Known issues with upgrades from Mageia 5 to Mageia 6

Since the release of Mageia 6 last week, there have been several reports about issues with upgrades from Mageia 5, particularly for users upgrading from KDE 4. While that is not surprising due to the complex nature of the upgrade from KDE 4 to Plasma 5, those issues had sadly not been noticed by our QA team during its extensive pre-release testing.

We want to both acknowledge that we are aware of the issues and working on needed fixes, and make sure that those wanting to upgrade from Mageia 5 are aware of the issues and read the errata beforehand. To avoid bad surprises for the least tech savvy users, we temporarily disabled the upgrade notification that prompts users to upgrade to Mageia 6 from their live session – it will be re-enabled as soon as we are confident that most users will have a smooth upgrade.

Also note that these issues are not present on new installs and the installation experience, particularly switching from KDE 4 to Plasma 5, will be easier with a fresh installation. As such all upgrade issues should be fixable via normal package updates, and no new ISOs are planned.

The section in the Mageia 6 errata relating to upgrades highlights the procedure to minimize some of the known issues. A big thing to note that has caused issues is the use of third party packages installed in Mageia 5, especially NVIDIA graphics drivers from the upstream website (as opposed to the ones packaged by Mageia).

Here is a small summary of things to look out for:

A note on upgrades in general – performing the upgrade offline with the Classical ISO works only if update repositories are enabled, as a full Mageia 5 upgrade requires more packages than are available on the ISO images. The recommended way to start an upgrade is to do it from a non-graphical terminal (e.g. tty2 accessed via Ctrl+Alt+F2) using urpmi, as outlined in the release notes.

If you have any upgrade issue, make sure to reach out with the community on the forums, mailing lists or IRC, where advanced users can help you debug and often fix an apparently broken system.

Apart from those upgrade issues affecting some Mageia 5 systems, most users seem to be pretty happy with Mageia 6 – we will continue showcasing some of the interesting developments made for this release in future blog posts. If you missed it, be sure to check out the last post outlining some of the goodies introduced thanks to the DNF support in Mageia 6.

This entry was posted in Mageia, release, users. Bookmark the permalink.

Curious about Mageia? Download it, give it a try and tell us how you feel about it.

Want to bring something to it? Learn how you can contribute and donate.

24 Responses to Known issues with upgrades from Mageia 5 to Mageia 6

  1. Pingback: Problemas conocidos al migrar de Mageia 5 a Mageia 6 | Mageia Blog (Español)

  2. Alberto Girlando says:

    I have upgraded on three different computers, a desktop and two notebooks (all 64), the first running gnome, one had gnome and cinnamon (but I use cinnamon) and the third only cinnamon. The second was upgraded on-line, the other two with usb sticks in classical installation. With computer 1 and 3 I essentially had no problems, immediately with a working system. With computer 2, the one with gnome and cinnamon, I experienced the problems already reported in the errata, i.e., no background (I added a note to the bug report). Installing lightdm gave me a background, but only the default (very nice, but I prefer to change backgrounds..). In additions, other problems surfaced, like the lack of battery control icon. So I disinstalled both gnome and cinnamon and cleaned the configuration files in my home directory. I also used urpme –autorphans , but that is something risky, some necessary packages were disinstalled also.. Anyway, then I reinstalled cinnamon (and the necessary missing packages), and everything is now OK. I use claws-mail in all three computers, and this gave the problems, as the upgrade is NOT compatible with the version in Mageia 5.1. I had to backup the configurations files, and start a new configuration in which I then copied the archive files (address book etc). I think it is a problem of claws, not of Mageia.
    On the whole, I am so far very happy with the new installation, from the new graphic to the new functionalities, some of which I still have to test.

  3. Pingback: Bekannte Probleme beim Upgrade von Mageia 5 nach Mageia 6 | Mageia Blog (Deutsch)

  4. zarqos says:

    You missed the issue of sound,
    I upgraded from mga5 and I faced a big problem where no login screen and all freezes.
    after many tries to resolve this problem with posting in the blog and the irc channal and google+ account and no replyes I decided to reinstall the system with mga6 gnome shell dvd 64 bit, and this time I faced a problem of sound, and I tried many times to get a help but no answer till now.
    I’m afraid about giving up and change my beloved mageia to another distribution.
    sorry for my words but I’m disappointed.

  5. transitoryhikikomori says:

    Successfully upgraded my M6500, but now I’m downloading 23GB of stuff I wanted, but apparently wasn’t on the install disk. This is low priority, but it’d be nice to have a “save my place” feature on something like this, so I could take the machine (which has no battery) to a place with faster wifi :).
    Running Enlightenment (Welcome Back!!) again is nice.

  6. Pingback: Problemas conhecidos na atualização da Mageia 5 para a Mageia 6 | Mageia Blog (Português)

  7. Pingback: Відомі проблеми із оновленням з Mageia 5 до Mageia 6 | Mageia Blog (Україна)

  8. egc says:

    Well well … I tried to do an upgrade from 5 to 6, but after the upgrade it didn’t start the X server anymore, no matter what i tried to do with or without proprietary driver (Nvidia) …
    Ok, so i made a new install, formatting / and leaving /home alone. Before installation i had the UID 1001. The installation program gave me the UID 500 and changed all the files and folders in my home directory to UID 500, even though userdrake says that the UID should not be lower than 1000 …
    I don’t know if this is important but could anyone tell me how to change the UID to all my files and folders back to 1001, because just changing my own UID in userdrake won’t let me log in to my own home directory anymore? Thanks!

    • katnatek says:

      Go to text terminal Ctrl+Alt+F2.
      Login as root

      chown -R 1001 /horme/user

      You must change user by your login name

      Would be good if you can report this in bugzilla.

  9. egc says:

    Wine doesn’t work either, freetype is missing. Bugreport is in Bugzilla.

    • egc says:

      Maybe nobody needs a help on this on Mageia, but it doesn’t work at all. Freetype is missing. Don’t know what qa team is testing if it did not notice this simple thing …

      • katnatek says:

        Check if you set right the repositories or change the mirror that you are using

        libfreetype-gir2.0-1.52.1-1.mga6
        libfreetype6-2.7.1-2.mga6.tainted

        • egc says:

          Thanks for reply!
          The installer installed
          lib64freetype-gir2.0-1.52.1-1.mga6
          lib64freetype6-2.7.1-2.mga6.tainted
          on my system.
          Do i need
          libfreetype-gir2.0-1.52.1-1.mga6
          libfreetype6-2.7.1-2.mga6.tainted?

          Here is the error message:
          “Wine cannot find the FreeType font library. To enable Wine to
          use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.”

  10. On my very busy main development machine server x86_64, Nvidia GTS250 driver 340-102, I got
    GLX problems with Salome-meca interface. glXCreateContext failed.
    I picked up an original Nvidia-340-102 package and recompile it in place of yours… bingo, all was
    working PERFECTLY … until yesterday … you released a standard update for MESA OpenGL-‘
    4.5 … :-(((
    Restarting the machine his morning : no x11 … recompil of nvidia340-102 crashes on glx …
    It seems an Immediate DOWNGRADE of the last MESA-GL package update is necessary !
    A lot of poor guys don’t know how to repair that in text mode …
    Thanks for rapid answer.

    Serge. (senior linux devel.)

    • obspsr says:

      I proceed on the repair
      The problem was hardly resolved. After the mesa-17.1.5 update, I was unable to compile Nvidia-340.102 (original).
      I did “rpm -e” all Mesa/GL packages from your update, followed by “urpme –downgrade lib64xxxxxxxx-17.1.4” for the 12 packages concerned.

      I did “urpme x11-driver-video-nvidia340” and had to remove also /usr/share/nvidia

      I reinstalled “urpmi x11-driver-video-nvidia340” smoothly ….

      … and reboot nicely to Plasma, tried Salome-meca 2016 and Salome-8.2.2 ==> CRASH with “missing swrast module” … known recurrent problem.
      I changed the link: /usr/lib64/libGL.so.1 –> /usr/lib64/libGL.so.340.102 (iso libGL.so.1.2) and reboot.

      Everything works blazing speed (cuda !) NOW BUT… all these important details must be reshaped and simplified by the gurus !

      The links stays the main problem in OpenGL drivers and Nvidia upgrades.
      Other nice refs: https://askubuntu.com/questions/541343/problems-with-libgl-fbconfigs-swrast-through-each-update

      We have some upgrade problems, for sure, but the rest of Mageia 6 is perfect.
      I did the move with ~3900 packages and 100 kde icons, no problem in Plasma !

      Thanks for coop, and all this work,
      Serge.

  11. egc says:

    On two machines (one with fresh installation an one with an upgrade from Mageia 5) on the boot screen i have only 3 question marks instead of the Mageia boot splash …
    And changing the video mode in in the second bootloader configuration screen of grub2 does not change anything (see also bug report https://bugs.mageia.org/show_bug.cgi?id=21246)

  12. egc says:

    VLC player does not show any DVD menu anymore (just black) …

    Boy, so many things that are broken in Mageia 6 … I also had to reinstall Windows because the boot loader of Windows was broken … Plasma 5 is quite quick but so many functions that are missing which were there in kde4 and kdm …

    • egc says:

      I recommend waiting at least half a year with upgrading to or installing Mageia 6 to see if most of the bugs are resolved … Right now Mageia 6 looks nice but it is only for nerds and not for everyday users who don’t want to struggle around days and days with problems.