From Mageia wiki
(Redirected from Mageia 3 Errata)
Jump to: navigation, search

This page is also available in these languages:

Português (pt-BR): Mageia 3 Errata pt_BR
français (fr): Mageia 3 Errata FR
Español (es): Erratas de Mageia_3
Русский (ru): Ошибки Mageia 3

List of current bugs found by the QA and other people If there is no confirmation in the bug report, feel free to add one or invalidate it, thanks.


  • The “Boot from Hard Disk” menu entry reboots from the USB stick (when installing from a USB stick). Workaround is to remove usb stick :-).
  • The options accessible through keys F3-F6 (DVD, Kernel option,...) do not work.Workaround
  • Pressing F2-F6 keys to change kernel options also moves selection from boot to install. As this happens only the first time, you can work around it by pressing Escape and moving the cursor again.


  • After installing LXDE, a panel link to Midori is missing (bug 7378)
  • Due to limited space, task-pulseaudio was removed from the iso: if you want sound, you may want to install task-pulseaudio.
  • Due to limited space, the grub2 graphical theme was removed from the iso: if you use grub2 and want a graphical menu then you can install the package grub2-mageia-theme.


Trying to install in UEFI mode will fail at the bootloader step (bug 10069)

Resolution too high for some monitors (no video output). Some monitors do not return correct (or any) Extended display identification data (EDID). If you have such a monitor, and have a video card that works with resolutions higher than what the monitor can display, there will be no video output. Workaround is to edit the kernel parameters at startup, and add the option xdriver=vesa, which will limit the resolution to 1024x768. For details see

Adding online media during install

When adding online repositories at the beginning of a Mageia 3 installation, with the classical installer iso images (dual-cd, x86_64 dvd, i586 dvd), the following steps must be taken.

Ensure the version of the iso image is dated June 6th, 2013. If you have the May 18th version, it can be updated with the command

rsync -avHP rsync:// /path/

Replace the x86_64-DVD with i586_DVD or dual-CD, as appropriate, and the /path/ with the directory containing the May 18th version of the iso image. Don’t forget the trailing slash, on both names. The mirror,, can be replaced by any mageia mirror, that supports the rsync protocol.

Do not accept the default repository selection. Either unselect the Nonfree Release repository, or select the Nonfree Release2 and Nonfree Updates repositories. On a 64 bit install, also select Nonfree 32 bit Release, and Nonfree 32 bit Updates.

At the end of the installation, DO NOT let it check for updates, or it will add a second full set of online repositories.

Installer Issues

  • You can see a long list of "unable to read modalias from /sys/..." messages when loading the installer (bug 7291)
  • The release notes are not yet complete, feel free to contribute here (the output in the installer will be take from here)
  • warning: %post(...) scriptlet failed, exit status 1 (bug 7611)
  • network installer does not work with NFS in some cases, (bug 9051). Work around is to use http.

Upgrade Issues

  • If some third party packages, like Adobe-reader or the JRE for Fedora are installed, please remove them before, or they will break the upgrade. (bug 10043, bug 10123, bug 10581) This may happen if one of the third party packages is (partly) installed in /bin, /lib, /lib64 or /sbin because this may cause conflicts during "usrmove". Third party packages which do not affect any of the "usrmove" directories will not break the upgrade.
  • If you see a message which contain "rpmlib(X-CheckUnifiedSystemdir)", it means you didn't carefully follow the instructions, as the /usr move is not complete.
  • When upgrading using mgaapplet, right at the end of the upgrade, it may fail with a segfault with a backtrace about pango, when it's supposed to be displaying a message to reboot the system. If that happens, just go ahead and reboot. For details, see
  • After upgrading using mgaapplet, when the system is rebooted, there may be a message about plymouthd failing to start. Workaround is to run "dracut -f" as the root user. For details see
  • When using mgaapplet to upgrade, after installing the mageia-prepare-upgrade package, on systems where the bios boot menu is used to select booting from a drive other then sda, /boot/grub/, and menu.lst files need to be fixed to point to the correct drives and "dracut -f" must be run manually (as root). For details see

luks encrypted partitions

If you have luks encrypted partitions, be sure to have a rescue-medium at hand, just in case you need it.

After upgrade you may not be able to enter the password or unlocking the root device fails for other reasons. To prevent this, run dracut -f after upgrade, but prior to rebooting. If booting still fails, this forum thread may help recovering. Also see Mageia_2_Errata#Base_system and Mageia_2_Errata#luks_encrypted_partitions.

Software Issues

Base system


  • Drakboot
Grub2 is recognized by drakboot but its configuration is only partial. For example configuration of entries is not working. If you need more options, it is recommended to use one of the native grub2 methods described in /usr/share/doc/grub2/README.Mageia. (Bug 9627)
  • Kernel options
like 'nokmsboot' are still to be added manually in /etc/default/grub. (Bug 8540)
They may be added into this line:-
GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=792 nokmsboot resume....."
  • Graphic modes
Similarly vga=xxx graphic modes when needed may also be added in the same place as shown above.
Note: After making changes to /etc/default/grub run update-grub (or update-grub2 which does the same) and enter the root password if asked.
  • Advanced sub-menu bug
After a kernel update, the second entry in the Advanced options for Mageia will not boot. It is unlikely that this option will be needed since it boots the same kernel as the main top-level entry. Running update-grub in a terminal once will repair it. (Bug 10024)
  • Multi-booting
When installing GRUB 2 to a partition (for multi-booting) using drakboot or the installer, nothing is written to the partition boot sector as this is not recommended for reliability reasons related to the use of block lists. These are prone to overwriting by some file system utilities, and not even possible on some file systems. Instead a copy of the grub2 kernel is written as /boot/grub2/i386-pc/core.img and this may be booted from either grub or grub2 used in a dedicated master bootloader or in another system.

A suitable entry in a grub legacy menu.lst for booting Mageia using grub2 installed to sda7 would be:

title Mageia 3 on sda7
root (hd0,6)
kernel /boot/grub2/i386-PC/core.img

An entry in a manually created /boot/grub2/grub.cfg (for a dedicated master bootloader) or when adding to an automatically generated menu using /boot/grub2/custom.cfg the entry would be:

menuentry 'Mageia 3 on sda7' {
multiboot /boot/grub2/i386-pc/core.img

If /boot is on a separate partition (e.g. needed when btrfs is used for root) then a suitable entry (where /boot is on sda6) would be as below. Note also the changed multiboot path:

menuentry 'Mageia-3 (btrfs root)' {
multiboot /grub2/i386-pc/core.img

A major advantage of grub2 over grub legacy is the ability to use partition labels without knowledge of unreliable device assignments. If the Mageia root partition is labelled 'mageia-3' (assuming /boot is not on a separate partition) then this may be used:

menuentry 'Mageia 3' {
search --no-floppy --label --set=root mageia-3
multiboot /boot/grub2/i386-pc/core.img

Note that since the partition boot record is not used by grub2, it may be used by grub legacy while both are installed together, allowing for chainloading into grub legacy and multibooting into grub2 from two separate master menu entries. Useful backup bootloader!

  • Minimal installs

When a minimal install of grub2 is needed it may be installed with urpmi grub2 --no-suggests which will omit os-prober and the grub2-mageia-theme, giving a classical grub2 text only menu with no other systems listed. os-prober may be installed later as may the grub2-mageia-theme package - just install or un-install these at will and the effect will be seen at the next boot.

  • KDE Leave menu

To use the KDE options on the Leave > Reboot sub-menu (accessed by clicking on the yellow icon - not the text) with grub2, it is necessary to change /etc/default/grub to include:


Run update-grub after editing /etc/default/grub

Also systemsettings > System Administration > Login Screen > Shutdown tab > Boot Manager needs grub2 selected.

NetworkManager doesn't manage devices in default GNOME installation

As NetworkManager is not the default network connection manager for Mageia, it can be confusing in a default GNOME install. net_applet, the default Mageia tool is hardly visible (in legacy systray in lower right corner) and NetworkManager is directly present.

If you want to use NetworkManager, please close net_applet and disable autostart for it (via right-click menu) and hand over control over your interfaces to NetworkManager, as root in a terminal do:

 sed -i s/NM_CONTROLLED=no/NM_CONTROLLED=yes/ /etc/sysconfig/network-scripts/ifcfg-wlan0

NetworkManager and drakxnet fail to connect to wifi network with WPA

Sometimes, when both NetworkManager and the net_applet (or other Mageia tools) are present (for example in Gnome), they can compete and interfere to establish a wifi connection with WPA. This can result in multiple pop-up from NetworkManager repeatedly asking for the password. Check the output of

ps aux | grep wpa

If there are more than one instance of wpa_supplicant running (i.e. more than one line), please reboot. On reboot, make sure in the Mageia Control Center that the network interface is configured to be "controlled by Network Manager". Then try to connect using Network Manager.

net_applet - Monitor Network/network accounting does nothing

If clicking on "Monitor Network" does nothing, you may need to install vnstat and net_monitor packages. You can then see the traffic used if that interface has been enabled via drakconnect.

drakfirewall doesn't generate shorewall6 config

This means that IPv6 is currently unfirewalled and shorewall6 service is likely to be in a failed state. after manual configuration of zones|interfaces|rules files, it should work.

According to, reporter Thierry ANIEL 2013-05-19 15:56:00 CEST:

shorewall6 service launch at startup fails. As a consequence, management of firewall through Mageia Control Center is not efficient.

This can be fixed as follows :

  1. uninstall shorewall-ipv6
  2. try to edit your firewall configuration
  3. Mageia Control Center complains that you must install shorewall-ipv6
  4. accept to install it
  5. all works now

Hplip and printer over wifi

If you want to configure a printer which is connected via wifi, you will see a crash of the tools. As a workaround you can change the original copy a python file to a new upstream one. See comment 22 in their bugzilla for more details. (Reported as bug 10067)

cups doesn't find usb printers

The cups package misses a dependency, so permissions for the usb-device can not be setup correctly. Since then cups cannot read device information, the printer is not listed and cannot be added. Solution: Install the package acl manually, then unplug and replug the printer:

urpmi acl

(Reported as bug 10475)



  • Unlike Mageia 2 and previous versions, by default ibus will not add input methods to itself automatically. Please follow these steps to add input methods:
    • Right click on the ibus icon on desktop systray (lower right corner on KDE).
    • Select "Preferences".
    • Select "Input Method" tab which should be on the center of ibus preferences.
    • Click on the "Select an input method" to see a grayed out list of languages.
    • Click on the ">" symbol before each languages to see a list of selectable input methods.
    • Select the wanted input method and click on the "Add" button on the right side.
The list of languages are shown grayed out and might cause confusion. But you should be able to add the input methods without any problem.


  • KDE Activities shown as Delete with red X (bug 7260)
  • KDE starts on TTY2 (bug 8074)
  • ibus-daemon not started (bug 8459), workaround is to install ibus-ui-gtk3.

KDE and locale settings


After installation, your language is not activated. For example, in a French install, for "numbers", "money", "date & time", "others" US standards are activated. This produces "$" instead of "€", for numbers "." instead of "," for decimal, etc.

You need to go to KDE settings > Localization > Countries & Languages then add your language in "Language". You can also add "Anglais US", it is useful when you go to an English language web site to fill in a web form, or edit this wiki in English!

Spell checker

This is an example based on a French language installation, but it relates equally well to other languages, including en_GB.

In order to have a spell checker enabled for all KDE applications (kwrite, konqueror ...) we need :

  • French dictionary "Français(France)" selected (default installation selects "Francais" dictionary)
  • spell checker activated (it is not by default installation)

Then go to kde settings > localization > spell checker then

  • select "Français(France)" in "Langue par défaut"
  • check "Vérification orthographique automatique activée"



  • If you use the Adwaita theme, all partition types are grey in diskdrake (bug 7379)
  • The Oxygen-gtk theme reverses the default button order in Gtk+ dialogs. Workaround is to switch to Adwaita. (bug 9609)
  • If the network icon shows "Unmanaged" for some network interface, you need to start the Mageia Control Center and the network configuration and select "Allow interface to be controlled by Network Manager", but do not attempt to connect directly within the MCC. Connect using NetworkManager only.
  • If you connect to a network (for example, a home router) and you cannot get out to the Internet or even ping the router, the Shorewall firewall is probably blocking the network interface (bug 10160). You can check "dmesg" to see if there are many messages about packets being rejected. If so, you need to add your network interface (for example, wlan0) into shorewalls interfaces file: echo -e "net\twlan0\tdetect" >> /etc/shorewall/interfaces. Note: where the previous command included "wlan0" you need to substitute the name of your network interface. Then restart shorewall service with "service shorewall restart".
  • Items on desktop are shown in lock-screen. Default setup is not affected since desktop-icons have to be enabled manually (for example via gnome-tweak-tool), but when they are enabled they also show up in the lock-screen. See upstream gnome bug 686943.


  • The titlebar & border is invisible when using certain themes. A workaround is to resize images so that all images are equal or larger than 2 pixel in width and length.(bug 8705)
Affected themes are: Ergologic Fire95 Frosty GlamICE Infadel2 Icedesert Kubical1.2 Miggy4 QNX SilverXP TrueCurve Urbicande Yamost


Hardware Issues

NVidia hybrid chipset

black screen after install or during live

The issue is that the 2nd chipset is primary and thus you cannot see anything, you can either attach external monitor, or with live add a "xdriver=vesa" to kernel append parameters; with installer, just adjust the xorg.conf manually to use only one monitor (the correct one)

Broadcom Wireless

This release has switched to using free drivers for all known supported wireless devices instead of using the proprietary Broadcom wl driver. However for some users the free drivers does not work well (or at all), and in that case you can enable Nonfree medias, and install broadcom-wl-kernel-$flavour-latest matching your kernel. The install DVDs and the live CDs / DVDs has the needed drivers available.

Virtualisation Issues

installing mageia on older KVM host

if you have an older KVM host (like Mageia 2), you should select "vga" as graphic instead of "cirrus" (default).

ATI dropped support

AMD dropped support of Radeon HD 2000/3000/4000 in Catalyst

Laptop issues

brightness regression

Some laptops will not change the brightness when you press the dedicated keys or use KDE and Gnome tools. This is because Linux 3.8 presents itself as Windows 8 to the BIOS. As a workaround, adding acpi_osi="!Windows 2012" to the GRUB kernel line has helped. Another workaround instead : acpi_backlight=vendor which prevents the ACPI backlight interface to be used.

acer x3995

In order install Mageia on a new ACER X3995, you need to do a BIOS update. BIOS updates can be downloaded from the Acer website.

Working UPDATE P11.A3 (without L) dated 12/10/2012 is known to work. You need a DOS bootable USB/CD in order to apply or a Windows 64-bit OS (not 32-bit). After performing the update, enter the BIOS configuration tool and reset to default values, reboot and then modify to yours.


bug 1215, comment 22

There have been reports about windows not booting after resizing an SSD

Deprecated Functionality