From Mageia wiki
Jump to: navigation, search
Drakconf multiflag.png
Other languages

Deutsch ; English ; Español ; Français ; Portuguese


Mageia 6

Note that we're still adding issues from the list of bugs in our Bugzilla that still need an errata entry for Mageia 6

Live images


1) By default GNOME uses the Wayland display server. Wayland is still not fully mature, and may not work well on some hardware. Normally GNOME will automatically fall back to using the display server if Wayland fails to start, but in some cases this fails to happen. If the GNOME desktop fails to launch after completing the initial language and locale selection, or if you experience display problems, you can try forcing GNOME to use the display server by adding nowayland to the boot options in the initial boot menu (F6 if using legacy boot, 'e' if using UEFI boot).

2) By default the NetworkManager service is enabled in place of the old network management services. On the plus side, this means that the NetworkManager applet integrated into the GNOME desktop works; on the minus side it means that attempting to configure your network connection via the MCC does not work. Use the drop-down menu accessible from the top right corner of the GNOME desktop to perform any necessary network configuration. For wired connections, the network is usually configured automatically and you don't need to do anything. For wireless networks, you will usually need to select an access point and, if it is password-protected, enter the password.

Non-working graphics

Some graphics hardware does not work correctly when using the xorg.conf file that gets created by harddrake when booting the Live system. If you have no graphical display at the end of the boot cycle, try adding noxorgconf to the boot options in the initial boot menu (F6 if using legacy boot, 'e' if using UEFI boot).

Some NVIDIA graphics cards don't work at all with the free video driver (nouveau). In this case, try replacing xdriver=free with xdriver=modesetting in the boot options in the initial boot menu, or alternatively, try using the non-free (proprietary) drivers by selection directly in the boot menu.

Non-working wifi cards

Some wifi hardware from Broadcom is known not to work, because they only work with their proprietary driver which we because of licensing issues not can have pre-built on the isos, and it need be loaded at boot time. Once Mageia is installed you can configure the wifi and reboot.

Retaining a third party bootloader

If, during live install, you want to retain your existing third party bootloader, then, when you get the bootloader screen, proceed to the NEXT screen titled 'Mageia Live' where there is an 'Advanced' button below the 'Probe Foreign OS' option.

In this advanced section there is a checkbox labeled "Do not touch ESP or MBR". Checking this box will stop your current bootloader from being modified. You will then need to add Mageia to a bootloader yourself. See also our Mageia6 version of the Live install manual.

Classic installer images

Fighting buggy UEFI firmwares

There are some reports about that resetting to default BIOS settings may solve problems, while others such as Lenovo Yoga 720 needed some fiddling: Strangely after booting once in Legacy mode, back to bios and change back from legacy mode to UEFI and with security disabled, both Live and Classic installed iso worked. Very similar to this experience.

Boot menu: Boot from Harddisk fails from USB

If you're booting the iso from a USB-key instead of from a DVD, the "Boot from HD" menu entry will not work, see bug 18392

Boot menu: Hardware Detection Tool

In rare cases, selecting 'kernel modules' can make a mess of the GUI and cause HDT to stop working, see bug 13829

Retaining an existing third party bootloader

If during installation of Mageia 6 you wish to avoid overwriting the MBR (PC-BIOS) or changing the default option in the UEFI nvram then at the 'Summary' screen you MUST enter the Bootloader section and then proceed to the NEXT screen titled 'BOOTLOADER CONFIGURATION' where there is an 'Advanced' button.

In this advanced section there is a checkbox labeled "Do not touch ESP or MBR". Checking this box will stop your current bootloader from being modified. You will then need to add Mageia to a bootloader yourself. See also our draft Mageia6 version of the installer manual (Link to be updated when the final Mga6 version is available).
Note that if you choose this option, add Mageia entry in Windows bootloader by Easybcd does not work because Grub2 is not installed in one of your Linux partition.

Upgrade issues

General points

  • Ensure that your Mageia 5 system is fully up-to-date.
  • If you can, back it up e.g. using Partclone or Clonezilla so that you can restore it if necessary.
  • Use the Classic ISO appropriate to your architecture.
  • Do not upgrade from KDE4 but from a lightweight desktop or from a command line.
Please note!
Please also read the page "From Mageia 5 to 6" to avoid Upgrade issues.

ownCloud -> Nextcloud client

If you have upgraded your Mageia 5 owncloud client to version 2 from backports, you can copy that configuration manually to nextcloud client in Mageia 6, see OwnCloud#Client_upgrading

ownCloud -> Nextcloud server

Nextcloud replaces ownCloud. This is both migration and several steps of upgrade. This software has limited ability to skip intermediate versions, so some iterative installs from MGA5 backports must be done *BEFORE* upgrading Mageia, and measures to prevent installing Nextcloud 12 before 11 taken. See OwnCloud#Upgrading for details.

Advice for complex upgrades

Large or complex upgrades may fail "transactions failed" before finishing, notably citing package conflicts or missing dependencies. This is partly due to the upgrade proceeding as grouped transactions which depend on later ones; and also to the fact that most upgrade packages exist on the upgrade media, others in online media. The following notes should get you through. They are based on an upgrade from Mageia 5 with over 4600 packages. Heed 'general points' above.

  • Run the upgrade using the Mageia-6-[arch]-DVD.iso
  • Add supplemental media (ftp, http, other)
  • If|when Conflict is presented, when taken back to 'supplemental media'

DO NOT ADD any media, leave it set as None.

  • As long as the conflicting rpms ARE NOT included in the iso then the upgrade will now complete successfully.

After rebooting to Mga6 user will still need to install any rpms skipped during the upgrade.

  • add Mga6 Mirror (don't forget to add 32-bit mirrors if you also had them active in Mageia 5 64-bit installation)
  • run 'urpmi --auto-select' and at y/n select n
  • Make note of the number of rpms which needed to be installed
  • run urpmi --auto-select --split-length (noted # of rpms)
  • all rpms should install and system is fully updated

Upgrading a system that has received updates since the ISO was released

If you are upgrading from one Mageia version to the next, and:

  • the old Mageia version has received updates and
  • for the next version only the iso is used, without online media,

then there can be packages with a newer version in "your old Mageia" than in "the new Mageia from the iso".
This can lead to a crash, with a message about "detecting looping forever while trying to resolve dependencies."

The easiest solution when you hit that problem is to not use the DVD for the upgrade, but to make sure the 'Check for newer "default" releases' box is ticked in this MCC screen in your Mageia 5 install: . Wait till mgaapplet informs you in your Mageia 5 session that a newer Mageia version is available, and then use the mgaapplet tool to start the upgrade.

Cinnamon desktop

After a system upgrade, Cinnamon DE has no wallpaper displayed. (mga#20914)

MATE Desktop

If a user has Mageia default wallpaper as a background on Mageia 5, upgrading to Mageia 6 won't change the background to new Mageia 6 default wallpaper. This is due to MATE's caching background in ~/.cache/mate/backgrounds folder. Removing this folder and log out-log in should set new Mageia 6 wallpaper as default background. (See: Mageia bug 19286 for further info)

Upgrade from Mageia 5 breaks sftp/sshfs connections

Due to change of location of a file, after the upgrade from Mageia 5 maybe you can't make connections using sftp/sshfs. To fix this as root:

  • Edit the file /etc/ssh/sshd_config, be sure the line
Subsystem	sftp

have this

Subsystem	sftp	/usr/libexec/openssh/sftp-server
  • Save the change and restart sshd
service sshd restart

See mga#21884 and mga#22340 for more information.

Security issues

Boot of system with cyphered partitions - CVE-2016-4484

Failed tries to enter the password of a cyphered partition with LUKS end with a shell.

People who want to secure their system have to:

  • add a BIOS password
  • add a grub password
  • add “” to the kernel command line

Software issues

Plasma 5 / KDE Applications

No sound from Plasma notifications

If there is no sound or only chopped sound only for plasma notification sounds, but in general sound is working, then this problem may be worked around by installing phonon4qt5-gstreamer. The cause for this is being investigated via (mga#21284).

The volume of the sound changes suddenly to 100% during a Plasma session

This is because PulseAudio uses flat volumes by default, instead of relative volumes, relative to an absolute master volume (mga#19377). If this is found to be inconvenient, relative volumes can be enabled by disabling flat volumes in the PulseAudio daemon's configuration file:

  • edit /etc/pulse/daemon.conf
  • change
 ;flat-volumes = yes


 flat-volumes = no
  • then restart PulseAudio by executing
 pulseaudio -k
 pulseaudio --start

The breeze theme is not used by default for some KDE 4 and GTK applications

  • For KDE4 applications that do not yet rely on the Plasma framework, for example Clementine, the kde4-style-breeze package must be installed so that they can have the same theme proposed by default.
  • GTK-based applications (Firefox, Thunderbid, Gimp, etc.) may not by default fit perfectly with the breeze theme. Go to the "System Configuration" tool on the Plasma desktop, then under "Application Appearance" then "GNOME Application Style (GTK)", selected "Breeze" for each GTK2 and GTK3 themes. To force the application of the Breeze theme, the following workaround may be needed: select and apply another theme temporarily, then select and apply the Breeze theme. This will allow the regeneration and implementation of the desired GTK theme.

Skrooge / tip of the day

The 'tip of the day' window only shows on top of the main window under Plasma. Under all other desktops, it appears under the main window, and hence is likely to be invisible - though present. This is an upstream problem. (mga#20426)

Kjots / ambiguous keyboard shortcut

This complains on starting about an ambiguous keyboard shortcut. Dismissing the alert continues normally. (mga#20428)

Applications that could need manual package installation

Due to missing require these applications not work as most in installations that not include Plasma as desktop alternative.


See mga#20514 for more information.

To get soundKonverter work install this packages

  • phonon4qt5-vlc (maybe you can use phonon4qt5-gstreamer instead)
  • kinit
  • kio
  • kio-extras


See mga#20830 for more information.

To get subtitlecomposer work install this packages

  • kio
  • kio-extras


When you have only fonts-ttf-liberation installed by default by mageia installer, you can show only square character for character in Cyrillic or Japanese or Chinese characters in an error message on a website.(and the same problem for mathematical characters)

To fix that install the package

  • fonts-ttf-unifont

See mga#20837 for more information.

The Plasma tools can't install new elements

The Plasma tools that offer to install new desktop themes, widgets and similar don't work right in Mageia 6, see mga#20645 and mga#21105 for more information.

For desktop themes, it is recommended to download the theme from and unzip to the folder .local/share/plasma/desktoptheme in your user folder.

Also for the tools that have the option, after download choose 'install from local file'.

Is reported (comments 11 and 12 in mga#20645) that the installation of the packages:

  • kpackage
  • kemoticons
  • kiconthemes

Helps to install from the Plasma tools some themes and widgets

Firefox from

Firefox from fails to start

If you want to have the lastest version of Mozilla Firefox downloaded from, you may experience an error.

Location: chrome://browser/content/browser.xul Line Number 344, Column 5:

<key id="key_quitApplication" key="&quitApplicationCmd.key;"

This error comes from the installed language packs for Mozilla Firefox that comes with Mageia 6. Uninstalling these language packs will remove the error.

$ rpm -qa | grep firefox

If you don't plan on using the provided Mozilla Firefox at all, you can uninstall everything:

rpm -qa | grep firefox | sudo xargs urpme

Or if for some reason you want to keep the Firefox shipped by Mageia:

Please note!

for this example i suppose the tarball you get from Mozilla's site is extracted in your user home. So you have a firefox folder in your user folder.

Please use the full path before firefox/ if you extract the tarball in other folders.

  • Open a terminal emulator
  • Run Mozilla's Firefox
 firefox/firefox --ProfileManager --new-instance --safe-mode
  • Create a new profile, by example zilla
  • Don't check the option for use as default profile
  • Choose the option "Start in Safe Mode"
  • In the url bar type about:config
  • Click the button "Accept the risk"
  • Click the right mouse button and select "New" > "Integer"
  • Create new integer value extensions.enabledScopes

See , for more information about this value.

  • Give 1 as value
  • Close Mozilla's Firefox
  • Close the terminal emulator
  • For launch the Mozilla's Firefox you can create a launcher that must have in the command box
firefox/firefox -p zilla
Please note!
remember zilla is the name in the example if you give other names to profile you must use that instead

Flash plugin not work with Firefox from

Due to changes in mozilla's Firefox our current version of freshplayerplugin not works with it.

As workaround:

Please note!
The updated freshplayerplugin package solves this issue

GNOME calculator fail to start on i586

See mga#20678

This issue is fixed with an updated gnome-calculator package.

GNOME screenshots of the single window have red and blue values swapped

Upstream bug, see bgo#780744 / bgo#779234. Tracking bug for mageia: mga#21292

Changes in font hinting (fontconfig)

Bug 18488 - Fontconfig 2.11.95 introduced voluntary changes in font hinting

If you feel uncomfortable with the new fonts and wish to restore the former font hinting of mageia 5, you should manually force fontconfig to do so. In summary:

1) Edit your ~/.basrhc file and add this line (force the old interpreter)

  export FREETYPE_PROPERTIES="truetype:interpreter-version=35"

2) Create a new file /etc/fonts/local.conf with the following content:

  <match target="font">
    <edit mode="assign" name="hintstyle">

Log out and log in, the new font settings should be effective.

See bug18488, comment 23 for more details (Note that the directory should be /etc/fonts instead of the mentioned /etc/fontconfig/.)

NB: Please notice that the new font settings are an upstream choice. See for instance the discussion:

Cinnamon Desktop

If this is installed along with other desktops, its desktop background is black rather than the Mageia theme. Nor can it be changed by the usual configuration tool. The desktop is, however, otherwise fully functional. The problem is only evident using SDDM, GDM or LXDM display managers; under LightDM, the desktop background is correct. (mga#21216)

Fuse-exfat no longer installed by default

Fuse-exfat had to be moved to our tainted repositories, because of possible license issues.
It is no longer installed by default for the same reason bug 16859

GNOME Classic desktop

Installed from the Classic ISO, this has for some display managers just oversized Home & Wastebasket icons, both ineffective. The 'Places' menu provides instant access to what would normally be iconised on the desktop - and more. Under some display managers, an oversize JoinMageia icon is also present; this works. (mga#21217)

IceWM and IceWM-session

It seems a bug that, in your display manager, there's now icewm and icewm-session, and that icewm-session does what icewm used to do (but no longer does). However, it's a new feature from upstream, see the Mageia 6 release notes

Kalarm & Ktorrent under Xfce

Starting these two applications under Xfce (only) has the window tucked underneath the top desktop taskbar, making access to their window bars impossible to move them down. The application menu and toolbars are also partially obscured. Alt+mouse, if not otherwise assigned, enables the window to be dragged lower. (mga#20413)

LXDE canberra error

  • If the screensaver displays
GTK message: failed to load module "canberra-gtk-module" 

You can get rid of this message by installing the package lib64canberra-gtk0, for X86_64 arch, or libcanberra-gtk0, for i586 arch, see mga#15176.


Mariadb - In Mageia 6 mariadb-10.1.16 has strict_password_validation permanently set ON.(bug 19223)
For passwords to be accepted they need to pass the cracklib-check test.
The following code snippet will do this for any intended password.

 $ echo 'yourpassword' | /usr/sbin/cracklib-check
 yourpassword: OK

MATE Desktop

  • Pluma cannot use python based plugins because porting from pygtk to libpeas is not completed in this release. Thus pluma-plugins package which provides python based plugins for pluma is obsoleted and removed from repositories. (See MATE Issue Report for further info)
  • gnome-main-menu is dropped from repositories because it is not compatible with MATE Desktop 1.16.0 and above and it's development is ceased. Users who want to use another menu implementation other than default one should use mate-menu
  • mintmenu is dropped from repositories because it is not compatible with (gtk+3 enabled) MATE Desktop 1.16.0 and hard to maintain. Thus this package is obsoleted and replaced by mate-menu package which provides the same functionality and easier to maintain.

Mythtv install problems

See bug 19127 for workarounds

Pre-built proprietary graphics drivers no longer available

As with Mageia 5.1, proprietary drivers are now built using the dkms system during the first boot (and rebuilt whenever a new kernel is installed). See bug 20142, comment 8 for a good explanation about why the pre-built ones were dropped and the Mageia 5.1 Release Notes for how to use a proprietary driver on a Live iso.

Endless reboot loop after switching between free and proprietary NVIDIA graphics drivers

After using MCC (or drakx11) to change between using the free graphics driver and using the proprietary graphics driver, on the next reboot you will be presented with the message "The system has to be rebooted due to a display driver change." Allowing the system to reboot will bring you back to this same message (bug 21263). This occurs because the drakx tools have failed to add/remove the nokmsboot option to/from the kernel boot command line (the nokmsboot option is required when using the proprietary driver and not required when using the free driver). This can be fixed by manually adding/removing the nokmsboot option. This can be done temporarily by editing the boot command line in the initial boot menu and permanently by editing the "Append" options in the "Set up boot system" section of the MCC.


Following the KDE upgrade, SDDM has now become the default Display Manager instead of KDM.

  • In some cases, sddm-greeter crashes after an "QOpenGLShader: could not create shader" error in the logs mga#16544 This bug report contains a workaround.
  • For computers with EFI and Optimus (Intel + Nvidia) graphics card, any installed kernel won't boot into SDDM. The workaround is to edit the kernel command line and remove noiswmd and add $vt_handoff. (mga#20583).
  • SDDM will not update user counting as it fails to register logins in /run/utmp. If this ends up being of relevant importance for you, please consider switching to other Display Manager (mga#18032).
  • If you have all desktops installed, the last items in the desktop menu (notably Xfce) will not be visible. They are, however, there, and accessible by arrowing down and pressing <Enter>, when the chosen entry then displays. (mga#20406)

Installing additional software packages from a USB memory stick

If you copied one of the classic installer ISOs to a USB memory stick (either by using the 'isodumper' utility or by using the 'dd' command) and used that to perform your initial installation, the installer recognises that memory stick as a CD/DVD and automatically adds 'cdrom' to the list of media used by the Mageia software installation tools (the GUI, rpmdrake, or the command, urpmi).

If you subsequently use the urpmi command to install additional software packages when the USB stick isn't plugged in, it will prompt you to insert the media, then output an error message:

Use of uninitialized value in subroutine entry at /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Net/DBus/Binding/ line 257

This error message appears to be spurious and can be ignored. However, urpmi then waits for you to insert a CD/DVD, and does not recognize your USB stick as an acceptable substitute.

Three alternative workarounds for this are:

  • Insert the USB stick before running the urpmi command
  • Use urpme to remove the 'perl-Hal-Cdroms' package. This causes urpmi to ask you to press Enter when you have inserted the media, rather than trying to detect it automatically
  • Disable or remove the 'cdrom' entries in the list of media used by urpmi. This is only applicable if you have added online repositories to the list of media, and don't want to install packages from the USB stick

The GUI software installer, rpmdrake, is not affected by this issue.

Note that if you install via a UEFI boot, the USB stick is only recognized as a CD/DVD if you select the default 'Install from DVD' option.

Additional info at mga#16142.

Netflix and other sites that require widevine plugin are not working

Widevine, a browser plugin to allow playback of DRM-protected videos, will not install successfully in the Firefox version distributed by Mageia. Also you need to make manual installation of widevine for the chromium-browser distributed by Mageia. See mga#20617 and mga#17449 for more details.

Follow the required procedure to install widevine in the browser of your choice.

Also read the page Status of Streaming Sites to know if you need to take other actions like faking the user agent to get your favorite streaming site work in Mageia.


With firefox closed:

  • As root edit the file /usr/lib/firefox/distribution/distribution.ini (or /usr/lib64/firefox/distribution/distribution.ini for x86_64 systems)
  • Change the lines


  • Save the changes
  • Launch Firefox
  • Open Preferences -> Content and enable the DRM checkbox
  • Go to about:addons -> Plugins, wait until confirmation that widevine is installed
  • You can check at if widevine-protected videos (the DRM option) are working

All the sites that need widevine and allowing Firefox for linux (with or without faking user agent) must work.

Please note!
This also install the Cisco's OpenH264 plugin

Current mageia's update to firefox 60esr fix this issue, so the above procedure is only needed if you stay in mageia's 52esr version of firefox

Chromium Browser

For chromium-browser, download and unpack widevine library and copy to Chromium browser's library directory, see mga#17449 comment 12 for more information.

Also Blogdrake, the Spanish community has created a script that makes this for you.

Install the last Tuningdrake package from Blogdrake's repositories and run get-widevine from a terminal emulator

If the widevine version installed by the script don't works try install other version running Widevine_Version=SomeVersion get-widevine where SomeVersion could be any of supported versions


To get updates to the package (and the scripts) at less add the Blogdrake's noarch repository

urpmi.addmedia BDK-Free-noarch

Please note!
  • Some sites could require fake the useragent
  • To keep widevine update run get-widevine each time the chromium browser is updated

Due to packaging issues flash plugin does not work in Chromium Browser

See mga#20196 for more information.

To get the flash plugin in Chromium browser follow this steps:

  • Install the package flash-player-plugin
  • Open a terminal emulator and execute the next commands
su -
mkdir -p /opt/google/chrome/PepperFlash
cd /opt/google/chrome/PepperFlash
ln -s $(rpm -E %{_libdir})/chromium-browser/PepperFlash/
ln -s $(rpm -E %{_libdir})/chromium-browser/PepperFlash/manifest.json manifest.json
  • Close the terminal emulator

Some fonts are not present in libreoffice

Due to upstream decision libreoffice drop support for some type of fonts, see mga#20725 for more information.

Changing language leads to a double set of home directories

When installing Mageia 6 with several languages, at the first start your /home directories are OK, only one language. Then go in MCC > system > localization and select another language, you will have a double set of /home directories, one in each language. See mga#14358

dropbox fail to start in Plasma/KDE

Is reported that dropbox fail to start in Plasma.

To make dropbox works in Plasma, try to run dropbox once, go to the corresponding .dropbox-dist/dropbox-lnx.* folder and remove at least one of this files:


For more information see mga#21843 the comment #50 on mga#20182 and this comment in the forums.

blueman ask twice for root password

After a recent update blueman start to ask twice for the root password.

If you don't wan't to have this behavior as root create the file /etc/polkit-1/rules.d/81-blueman.rules with this

polkit.addRule(function(action, subject) {
 if ( == "org.blueman.rfkill.setstate" && subject.local && && subject.isInGroup("wheel")) {
     return polkit.Result.YES;
 if ( == "" && subject.local && && subject.isInGroup("wheel")) {
     return polkit.Result.YES;

Also you need to add to the users that need blueman to the wheel group.

For more information see mga#23770

Hardware issues

Install/boot on HP Envy 15-AH150SA

The SSDTs are only compatible with Windows, and might cause a kernel panic on most types of install media (other than a live stick) and on all completed installs. Add acpi_no_static_ssdt as a kernel parameter at boot to solve this issue. For adding kernel options see the instructions here (How to set up kernel options). See also

Caveat for Optimus laptops (hybrid Intel/NVIDIA GPU)

The support for the Optimus technology (laptops with both an Intel graphics processor and a discrete NVIDIA GPU) is incomplete in Mageia's configuration tool for the graphics drivers. It may propose you to configure either the Intel IGP, the NVIDIA GPU or both: only the first option (Intel IGP alone) is suitable, as the NVIDIA GPU is typically not connected to the monitor.

If you configure only the Intel IGP, or use the default configuration proposed by the installer, it should install properly.

See the Optimus section in the release notes to learn more about configuration options to use the NVIDIA GPU post-installation.

UEFI firmware is hardcoded to use Windows on some HP, Lenovo and Medion laptops

Some firmware does not comply with the UEFI standards, and will not allow you to boot Mageia by default. Bug 19112 contains several workarounds..

Black and/or flickering display on ACER E5-571 when using KDE/Plasma

When using Plasma/KDE on ACER E5-571 and possible other notebooks featuring Intel IGP (8086:0a16 - Haswell-ULT) or AMD GPU, display rapidly flickers or turns black (opening console via Alt+F2 or folder sometimes helps), which didn't happen on MGA5. The solution is to enable Composite X11 extension, eg. remove 'Disable Composite' option in DrakX11.

3 rectangle shapes with question mark during boot

After selecting to boot Mageia in the grub2 menu the booting presents a grey screen with three rectangle shapes with question marks in them. The system boots normally and proceeds to the normal Login screen, or automatic logon depending on configuration. This happens if you are using the nvidia340 driver (and quite likely, any other driver that doesn't support kernel mode setting). Bug [1] contains possible workarounds.