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

Errata page for Mageia 2. Please have a look here before reporting bugs.

Une version en français est disponible.



  • The “Boot from Hard Disk” menu entry results in rebooting on the USB stick (when installing from an USB stick).
  • The options accessible through keys F3-F6 (DVD, Kernel option,...) are not working.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 workaround with escape and moving the cursor again.

Installer Issues

Bootloader step

The bootloader step fails if the /boot partition is too small ( less than 20Mb ). See bug 4912

Grub installation

The bootloader will be configured according to automatic detection of available installations on your hard disk.
If you want to check and/or change the configuration you can do so by hitting the "Configure" button in the summary.
Note that the bootloader will not be written to the hard disk before you leave the summary.

(ref. bug 484)

Installing Mageia next to a GRUB2 based distribution

Installing Mageia next to a GRUB2 based distro (like Debian or Ubuntu) is not supported. With the default GRUB settings you won't be able to boot into your GRUB2 based distro anymore. To manually add a GRUB2 based system to your Mageia boot menu you may wish to follow the steps here.

Mageia boot fails when dual booted from a GRUB2 system

There is a bug in os-prober used by most GRUB2 based distributions which causes GRUB2 to generate faulty boot menu entries for Mageia. The bug is fixed in os-prober-1.53 but this was only released on May 8th 2012 and therefore still affects most GRUB2 based systems. There is more information on correcting this issue in the Mageia forum here. It will work with the line "initrd /boot/initrd.img" in the grub2 boot-entry.

Stage 1

Strange ascii characters can be seen in the stage1 (before the graphical installation or in rescue mode) example: See bug 4894

luks encrypted partitions

cannot use luks encrypted partitions during the install or Mageia2 Beta3 Installer DVD 64bits : Can not unlock and set /home on my crypted home partition on logical volume (LVM) to use it. See bug 5661 (new) or bug 3749 (old). Workaround : for example use System Rescue CD to backup luks encrypted partitions with command line (no tutorial) (for advanced users only).

Dual iso and package selection

Since the dual iso contains only a minimal list of packages, only LXDE is available even though you can see other categories. If you want to install these packages with the dual iso you need to enable the online repositories.

Live Installer

When installing from a live CD, if you close an advanced window, the installer will quit without warning.

Removing unused drivers/locales

Be careful when the installer asks if it should remove unused drivers and unused locales. It may remove drivers which the system needs later on, be even more careful as by default both options are enabled. It was reported in forums that in some cases drivers that are still required could also be removed, so it is best to keep unused drivers and locales if you are unsure or are in doubt.

Upgrade Issues

See also bugs in our bugzilla tracker


KDE Platform Issues

  • Nepomuk

It is now enabled by default. You can either disable it or remove it from the installation by using :

urpme nepomuk

Please note that some applications now require Nepomuk to be enabled such as KMail2.

KDE Workspace Issues

  • Desktop effects

They are now enabled by default (following upstream configuration). You can disable them using ALT+SHIFT+F12 on session start.

  • Mageia Panel

The default Mageia panel now use the plasmoid icontasks (part of kdeplasma-addons) as the default task manager. The upgrade should be done automatically for users using the default panel in MGA1. Additional plasmoids should also be added on the panel but the order can be different. For classical user it is still possible to use the default task manager plasmoid by either :

    • removing the plasmoid and adding back the default task manager plasmoid
    • removing the entire panel and simply adding the classical mageia panel with a right click on the desktop
  • Upstream configuration

Starting KDE SC 4.7 we're providing an additional package name, vanilla, in order for an end user to simply use upstream configuration for desktop and applications. You simply need to install the vanilla-kde4-config package via rpmdrake or via urpmi like this:

urpmi vanilla-kde4-config

KDE Application Issues

  • KDEPim related issues

- KMail has been upgraded from Kmail (in Mageia 1) to KMail 4.8.x .

The major change is related to KMail which is now Akonadi based. You should be asked by an utility to either upgrade your installation or start from a fresh configuration.

- Bogofilter is broken with KMail 4.8.x .

Currently using the bogofilter to filter mail under kmail produces empty emails. This a know issue ( see mga 5838 and KDEPIM Devel mailing list. The only workaround currently is to disable bogofilter.

  • Google Calendar & Contacts integration

There are two packages allowing this integration in Kontact : akonadi-google & akonadi-googledata Akonadi-googledata has been available since MGA1 but seems to be less maintained, we recommend switching to akonadi-google

  • Kscreensaver

Effects are now disabled by default (see mga #5020 but also kde #283284 & kde #182104). To enable them you need to add in your ~/.kde4/share/config/kslideshow.kssrc :

  • Kshisen

Removing tiles could be very slow when the sound is enabled. It's an upstream issue fixed in KDE 4.9 ( see kde #28 9473 ) but as said in mga #4785 the backport of this fix is not easy. Current workaround is to disable sound. For some users using phonon-vlc instead of phonon-gstreamer seems to fix the issue.

GNOME issues

Totem and other GTK programs are missing all icons

You need to install gnome-icon-theme-symbolic to fix this issue.

Alacarte does not start

It will be provided as an update once a non-buggy version is available from GNOME.

pm-utils conflicts with laptop-mode-tools

The pm-utils package conflicts with laptop-mode-tools package; according to pm-utils upstream developers, pm-utils now provides functionalities similar to those provided by laptop-mode-tools, and that both package should conflict due to that reason. Also note that having both packages installed at the same time can cause some bugs, for example this bug in Mageia. For these reasons, on upgrading it's very likely laptop-mode-tools will be removed from your installation as pm-utils is required by most desktop environments' core packages.

Software Issues

Boot fails when webdav, sshfs etc. entries exist in fstab

If you have entries for WebDAV storage or other uncommon network filesystems (e.g. sshfs via fuse) in /etc/fstab, after an upgrade your system may fail to boot and display messages similar to the following where the boot stalls:

 Dependency failed. Aborted start of Relabel all filesystems, if necessary [ABORT]
 Dependency failed. Aborted start of Mark the need to relabel after reboot [ABORT]
 Dependency failed. Aborted start of Setup links in /boot for running kernel [ABORT]
 Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode.
 Give root password for maintenance (or type Control-D to continue):

To avoid this problem simply ensure that all network filesystems are clearly labelled with the "_netdev" option in fstab.

In addition, if any filesystem is non-critical for logins (i.e. not your $HOME), you should mark with the "nofail" option. This will ensure that the login screen starts quicker (i.e. before network and before the mount), otherwise it will be delayed until the network is up and the filesystem is mounted.

Base system

  • After upgrade (typically only urpmi based upgrades), dracut will generate a large, generic initrd. This is needed due to the fact that because the host system did not boot with a dracut-based initrd, the udev medadata may be incomplete and dracut is subsequently unable to probe device information correct to generate a "hostonly" (i.e. slimline and custom to your system) initrd. After initial boot you can recreate your initrd via "dracut -f" to get a more customised, smaller initrd.
  • If you are affected by the above issue and use encrypted partions and your keyboard is not a US qwerty model, you may have trouble entering your pass phrase until you regenerate your initrd as described above. If you are affected by this you should append the following to the kernel command line: vconsole.keymap=de-latin1-nodeadkeys.uni (substituting for your own keymap of course!). You only need to do this up until the point where you regenerate your initrd as described above. You can find your keymap name by looking in the file: /etc/sysconfig/keyboard for the KEYTABLE variable.

Drakconf issue

Drakconf needs only lib64gdk_pixbuf2.0_0-loaders-png15

GdkPixbuf-WARNING **: Bug! gdk-pixbuf loader 'png12' didn't set an error on failure. at /usr/lib/libDrakX/ line 316.
Failed to load image '/usr/lib/libDrakX/icons/drakbug-16.png': reason not known, probably a corrupt image file at /usr/lib/libDrakX/ line 316.

To resolve that:

rpm -e $(rpm -E %{_lib})gdk_pixbuf2.0_0-loaders-png12 --nodeps
urpmi $(rpm -E %{_lib})gdk_pixbuf2.0_0-loaders-png15 

Firefox and Adblock

If you have installed adblock plus from and firefox which segfault, check what lib(64)proxy you have.

If you have libproxy-mozjs, try to remove it and install the webkit one:

  • urpmi $(rpm -E %{_lib})proxy-webkit
  • urpme $(rpm -E %{_lib})proxy-mozjs

KDE and locale settings


After installation, your language is not activated. So as example in a French install, for "numbers", "money", "date & time", "others" US standards are activated. for example for money you have "$" 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 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"

LibreOffice Issues

libreoffice-kde Issues

The libreoffice-kde, the LibreOffice KDE integration plugin, is known to cause some issues:

  • Hovering a button in the toolbars doesn't give the expected visual feedback (the button does not glow and/or is not shown as popping out of the GUI, etc).
  • While using LibreOffice with the traditional Chinese language pack (libreoffice-langpack-zh_TW), the text appearing on the status bar is shown as squares (a workaround is available in Bug#815.)

As such, it is currently not recommended to install libreoffice-kde. This plugin offers two main features:

  • Makes LibreOffice use the KDE4 file chooser instead of the native file chooser.
  • Makes LibreOffice use KDE4 Oxygen style.
    If you want LibreOffice and other GTK+2.0 applications to use the KDE4 Oxygen style, install the oxygen-gtk package (you can set the GTK+2.0 icon theme in System Settings -> Applications Appearance -> GTK Styles and Fonts).

Without 'libreoffice-kde', you will only be missing the KDE4 file chooser but the LibreOffice one works well enough, even if it doesn't look very KDE.

Chinese font fallback substitution issue

As described in Bug#751, there are some Chinese font issues when typing Chinese characters or opening files containing Chinese characters:

  • When typing in Chinese with a font not containing Chinese characters, the typed characters will be displayed as unreadable squares
  • When opening a file with Chinese font characters, but the font specified in the document is not present in the system, the Chinese characters in these files will also be displayed as unreadable squares.

Ideally, the Chinese characters will use the default system CJK font for fallback/substitution in the above cases. But unfortunately this does not happen in LibreOffice in Mageia at the moment.

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. Then you can see the traffic used if you have enabled it for that interface via drakconnect.

lsusb, command not found

If you need lsusb you should install usbutils.

LXDE Issues

No shutdown possibility, when using xdm or slim

When using xdm or slim as desktop manager, you won't be able to shutdown from inside lxde. Use lxdm, gdm or kdm as an alternative.

LXDM and Xguest

Xguest seems not working with LXDM, as a workaround you may use GDM, or KDM.

X2go issues

x2goclient is segfaulting in some cases. The seemingly random nature of this problem is making it hard for the fault to be idetified. As a workaround use pyhoca-gui, once you have configured your sessions in x2goclient.

SSH daemon issues

With SSH daemon, we no longer support using sshd with the UsePAM=no option set. If you use this, option you will be warned in your syslog and restarting sshd service will likely kill any active sessions.

Hardware Issues

Proprietary graphics card drivers

The Free DVD is known to generate a non-working installation on many systems with Radeon or Nvidia graphics . If you are not an experienced Linux user, we recommend you use one of the Live CDs to install Mageia 2, and when asked, choose to use the proprietary graphics driver. But you can also get issue with the live. We list below easy workaround for each case


Live Cds

Depending on your card you may add in the grub (f6):

  • xdriver=radeon
  • xdriver=fglrx
  • xdriver=intel (if you have a system with both intel and amd/ati gpu)

DVDs & Dual

If you want to install through the free DVD or Dual we recommend you to use the vesa driver in the Xserver configuration
Then at the first reboot, enable the nonfree repository with drakrpm-edit-media and install the requested package with XFdrake. (radeon-firmware or fglrx)

If you have errors, i.e by not using the vesa driver:

  • boot in safe mode.
  • go in the emergency console
  • run XFdrake and chose Vesa
    • if you have a network connection, add the online media with urpmi.addmedia --distrib --mirrorlist
    • enable the Nonfree repositories: urpmi.update --no-ignore Nonfree\ Release Nonfree\ Updates
    • updates the repositories: urpmi.update -a
    • Run XFdrake and choose the correct driver.

Note that the 'vesa' driver doesn't support many common widescreen resolutions, so is only to get a very basic Xwindows session, but once there you can select the correct driver.


Live CDs

Depending on your card you may add in the grub (f6):

  • xdriver=nouveau
  • xdriver=nvidia
  • xdriver=intel (if you have a system with both intel and nvidia gpu)

DVDs & Dual

See above, the procedure will be the same.

ath5k wireless problems on a HP Compaq Presario CQ60-415so

Something blocks wlan0-interface from starting up and there's a possible workaround to that:

Install rfkill
Disable the eth0-interface
Now enable wlan0-interface

Then type:

 rmmod -f ath5k
 rfkill unblock all
 modprobe ath5k

Realtek USB wireless adapter does not work after live install

The firmware for the Realtek USB wireless adapter is incorrectly removed during live install, and the Mageia network configuration tools freeze when trying to configure it. You can install the rtlwifi-firmware package to fix the issue.

This is reported as

some hardware doesn't work because it needs firmware

If your hardware doesn't work, you can try to install the kernel-firmware-nonfree package that is in the nonfree repositories and then reboot your computer. After rebooting, check if your hardware is now working. Note : you need this package for the firmware needed by some wifi network card, etc...

some HP devices require a plugin which can't be installed automatically

Some HP printers / multi-function devices require plugins additionally to hplip to function correctly. Currently such plugins can't be installed automatically, and also not manually as normal user. Please install those plugins as root via starting


Reported as and at

IDE controllers and kernel module load order

As per the problem is that ide hard drives show up as /dev/hd? instead of as /dev/sd?, and cd/dvd drives show up as /dev/hd? instead of as /dev/sr?. It's been fixed for most cases, but not all apparently.

The workaround is to add a kernel option, with rdloaddriver=module, where module is replaces with one of pata_via, pata_amd, pata_jmicron, or ata_piix, depending on the hardware being used.

To determine which module is needed, the easiest way is to run lspcidrake|grep IDE under Mageia 1. If Mageia 1 is not available, all four modules can be loaded, and then use lspcidrake|grep IDE, to see which one is needed for the hardware in use, i.e. Add rdloaddriver=pata_via rdloaddriver=pata_amd rdloaddriver=pata_jmicron rdloaddriver=ata_piix to the kernel options. Once the correct module is known, add the kernel option to all entries in /boot/grub/menu.lst.

Powersaving features not enabled by default on AMD E2 (brazos) CPU's

The module that controls the CPU frequency is not loaded, forcing it to run at max speed all the time. Although it doesn't affect anyhow to the usage, the battery life is decreased a whole bunch.

The easiest way to solve this making changes permanent is to edit edit file /etc/modules and simply add the line powernow_k8

Still the governor of cpufreq would be performance, and to really make use of the powernow_k8 features it should be set to ondemand. To make this at startup you can install the cpupower software and add the following command to /etc/rc.local

 cpupower frequency-set -g ondemand

The bug is already reported:

partitioning of big hard disks

Diskdrake uses fdisk per default. In order to handle big disks (> 2TB) properly you have to install gdisk from the repositories.

Important: During the installation process you cannot create partitions bigger than 2 TB with diskdrake but you have two choices:

  • either you partition your disk with an other tool beforehand (e.g. gparted)
  • or you install gdisk from the repositories after the first reboot and resize your partitions.

Deprecated Functionality


  • initscripts provided in Mageia 1 used to run the executable /sbin/halt.pre after terminating all processes but before unmounting filesystems. Under systemd, no such hook point exists. Users are advised to write their own systemd unit (see "man systemd.unit" and "man systemd.service" to run their own custom functionality. Most scripts should be designed to be run at no specific point in time, with the exeption of the /sbin/halt.local script which is still run as before (after unmounting filesystems). Reference: #3744.

kernel modules

  • sound modules no longer support the sound-slot-n syntax. In order to be fully hotplug friendly (not relying on manual module loading) we have had to deprecate this syntax. It worked by cycling through the modules when loading manually, which is fundamentally incompatible with hotplug. See #4688 for alternative syntax.