- 1 Mageia 7
- 1.1 Boot
- 1.2 Live images
- 1.3 Classic installer images
- 1.4 Upgrade issues
- 1.5 Software issues
- 1.5.1 Plasma Applications
- 1.5.2 Cinnamon Applications
- 1.5.3 GNOME Applications
- 1.5.4 Xfce Applications
- 1.5.5 IceWM
- 1.5.6 Netflix and other sites that require widevine plugin are not working in Chromium
- 1.5.7 NFS server
- 1.5.8 Bind server
- 1.5.9 Steam installation
- 1.5.10 PMB
- 1.5.11 Obsoleted packages
Note that we're still adding issues from the list of bugs in our Bugzilla that still need an errata entry for Mageia 7
Some recent Intel systems
With some recent hardware, the boot stops after selecting the Grub entry, but before that the kernel comes in action. The identified culprit is the microcode from Intel and last Intel i7 generation processors. This is reported for Asus UX333, UX433 or UX533. A workaround is to add a kernel option dis_ucode_ldr. The solution seems to be a BIOS update. See mga#24979.
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 mga#19642 comment 36 contains possible workarounds.
Some machines fail booting 32 bit installer and live iso
See mga#23431. Remedy: use 64 bit versions.
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 X.org 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 X.org display server by adding nowayland to the boot options in the initial boot menu (press to edit the boot options).
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.
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 (pressto edit the boot options).
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.
With Intel 810 - UHD Graphics 620, KDE Plasma, GNOME, and several other desktop environments display a blank desktop/panel. The Xfce desktop environment does work fully. See mga#25022 for details.
If your laptop with hybrid graphics fail to boot, try to edit the boot command line similarly as described above but change xdriver=free to xdriver=intel. This will force the system to use the Intel GPU which often is the one electrically connected to the monitor. It may also work to keep free and add the word noxorgconf to the end of the line. Work in progress; mga#25181
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 Mageia 7 version of the Live install manual.
Classic installer images
Fighting buggy UEFI firmwares
There are some reports about that resetting to default UEFI settings may solve problems, while others such as Lenovo Yoga 720 needed some fiddling: Strangely after booting once in Legacy mode, back to UEFI settings and change back from legacy mode to UEFI and with secure boot disabled, both Live and Classic installed iso worked. Very similar to this experience.
Retaining an existing third party bootloader
If during installation of Mageia 7 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 Mageia 7 version of the installer manual.
- Ensure that your Mageia 6 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.
Upgrading a VirtualBox guest
Depending on when it was created, a Mageia 6 VirtualBox guest may or may not use nokmsboot as one of the kernel boot options. If there, an upgrade install from Mageia 6 to Mageia 7 will fail to reboot properly. For best results, the nokmsboot boot option should be removed before beginning the upgrade.
The easiest way to do this is to boot the guest before the upgrade, run the Mageia Control Center inside the guest, choose Boot, then Set up the boot system. The kernel boot options will be shown on the second screen. If nokmsboot is there, simply delete it, and click on "Finish." An alternative is to remove it during the "Post-install Configuration" phase of the upgrade. "Set up the boot system" is one of the things that can be configured. The process is the same as if done with MCC.
Finally, if you missed all this and your upgraded guest fails to boot, shut it down and then restart it. When the grub2 menu appears, press linux16. Use the arrow keys of your keyboard to go to that line and move along it and use the key to remove nokmsboot. Be careful not to delete or add anything else. When finished, press and the boot should be successful. Once in the guest, use MCC as described above to make the change permanent.on your keyboard. This will bring up a text screen that can be edited temporarily, for this boot. Look for the line that begins with
LVM and/or LUKS with old udisks
Before upgrading a system using LVM and/or LUKS from mga6, udisks need to be uninstalled manually. Because if udisks is installed when Mageia 7 boots, it will time out and drop you to debug shell. If that happens, there in the shell press - and it will boot up normally and you can make the uninstall. See mga#24949.
GRUB fail to boot with JFS file system
If you use legacy GRUB and the filesystem JFS, you need to upgrade to GRUB2 before upgrading to Mageia 7, See mga#25009; presumably fixed in grub-0.97-48.1.mga7, so if you enable online update media and internet connection during the upgrade (or use network installation), it should work.
Advice for complex upgrades
Large or complex upgrades may fail with message "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. First see 'general points' above.
- Run the upgrade using the Mageia-7-[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 Mga7 user will still need to install any rpms skipped during the upgrade:
- Add Mga7 Mirror (don't forget to add 32-bit mirrors if you also had them active in Mageia 6 64-bit installation)
- Run urpmi --auto-select and at y/n select
- Make note of the number of rpms which needed to be installed
- Run urpmi --auto-select --split-length (noted # of rpms, for example urpmi --auto-select --split-length 423 for 423 rpms)
- All rpms should install and system is fully updated
Device names changed for MMC devices
By default, Mageia uses UUIDs for block-devices. It is possible that you deviated from the default and manually changed /etc/fstab to use device names for MMC block-devices. If so, you will have to change this from /dev/mmcblk0 to /dev/mmcblk1. This has changed in Linux kernel 4.14.
Packages with mga6 suffix
Take care of this if you use to check if you still have some old packages after the upgrade. Due to some issues in the development cycle of mageia 7 some packages still have mga6 suffix, you can see here the list of packages.
Oxygen Look And Feel Workspace Theme
Be aware that the Plasma Oxygen theme may demonstrate a memory leak when used with some Intel hardware graphics cards/drivers. While the exact cause is still being tracked down, when the problem does show up, it consumes all available memory, resulting in slowing performance as the swap fills up, followed by out of memory killing of processes in random order. The random killing of processes may result in file corruption, depending on what being written when the process was killed. Until the exact cause has been tracked down and fixed, the issue may be avoided by keeping the default breeze theme selected, instead of changing it to oxygen.
Cinnamon requires cinnamon-screensaver to be installed. If you select Cinnamon in the installer, or if you manually install the task-cinnamon or task-cinnamon-minimal meta-packages, this will be done automatically, but if you choose to manually install the cinnamon package by itself, Cinnamon will not work until you also install the cinnamon-screensaver package. See mga#23899.
GNOME on Wayland and su -
Some drak commands previously invoked from a "su -" root terminal no longer presents a user GUI interface, rather a ncurses interface. If this occurs, exit the ncurses interface, exit the root terminal and re-invoke as normal user terminal the drak command. A password popup will occur requesting root password and after the correct password is entered, the expected GUI interface is presented.
Recover Evolution data after an upgrade
Evolution format changed from 2.32 to 3.x. In both cases, the data was stored in ~/.local/share/evolution/mail/local/ according to XDG Base Directory Specification. Inside that data directory, the format and the tree structure changed.
This article in linuxmint forums explain how recover your data.
Screen tearing at login
It has been found that on some older hardware that there is some screen tearing after entering your user name and password into the login greeter and before the full presentation of the desktop. See mga#24134.
If you are affected, choose a free video driver after logging in.
Windows survive to closing
With some specific hardware, the window of closing application doesn't disappear, although the application is really closed. This doesn't occur by an opening session with "IceWM session". See mga#23595
Netflix and other sites that require widevine plugin are not working in Chromium
Widevine, a browser plugin to allow playback of DRM-protected videos, will not install successfully in the chromium-browser distributed by Mageia. See mga#24835 for more details.
For the moment, if you use some site that need widevine plugin, try with firefox.
Latest nfs-utils 2.3.4 brings minor configuration handling changes.
First, parsing of /etc/export file seems to be stricter, and usage of wildcard, ie 192.168.0.*), instead of CIDR notation, ie 192.168.0.0/24, is no longer supported. You may want to consider creating a file in the directory /etc/exports.d and placing just your changes in a file name of your choice ending in .exports.
See man exports.
Second, usage of /etc/sysconfig/nfs to define command-line parameters for various NFS utilities is no longer supported, in favour of /etc/nfs.conf configuration file. A script (/usr/libexec/nfs-utils/nfsconvert.sh) is available for conversion, and the nfs-convert systemd service, which is a dependency of other nfs services, should automatically run it if needed.
Starting with bind 9.11.5P1-2mga7, the files needed to run bind in a chroot are now shipped in distinct subpackages:
- bind-chroot for the standard bind
- bind-sdb-chroot for bind with SDB support
The new systemd units follow the same logic:
- bind service runs bind
- bind-sdb service runs bind with SDB support
- bind-chroot service runs bind in a chroot
- bind-sdb-chroot service runs with SDB support in a chroot
Due to some utilities transfer between the bind and the bind-utils packages, an rpm transaction trying to update only one of those package will fail because of a file conflict.
The root zone public key, needed for DNSSEC validation, is missing from the package.
Both issues are fixed in a pending package update.
As Steam needs some 32 bit libraries, you have to manually enable 32bit repositories (Core Release and Updates) as they are no longer enabled by default. The indication that they are not enabled is that some libraries can't be found.
Phpmybibli is not yet compatible with php7, so you can not upgrade to Mageia 7 which as only php 7.3. The upgrade of PMB to php 7.3 is a work in progress upstream, so we will package it as soon as it will be available.
get-skype is now obsolete, as the classic Skype versions for Linux ceased to be supported by Skype on 1 July 2017. There is a new web-based Skype version which may be installed directly from the Skype web site by selecting the rpm version here. Note that only 64-bit systems are supported.
cvsps version 2, which was last updated over ten years ago, is now obsolete. It was used by git-cvsimport from the git-cvs package. If you are performing a one-shot import of a CVS repository, consider using cvs-fast-export.