Wiki » Mageia 10 Errata

Other languages Deutsch ; English  ; Español ; Français ; Português (Portugal) ; português brasileiro

Notes

This page is a companion to the Release Notes.

Entries below prepended with "FIXED", have a released update. So if you experience a problem marked fixed, try to do a full update. Some issues may need logout/login or reboot. Some are installation or upgrade issues. Note it may take a day for a released update to reach your mirror.

Significant issues with packages contained in the ISOs are listed here, plus wider coverage related to upgrading. - We have a lot of additional software in repositories.

A non-listed issue you experience may be fixed if you do a full update.

Also see Release Notes Known issues and Bug reporting sections.

THIS PAGE IS A WORK IN PROGRESS

Note that we will be updating issues from the FOR_RELEASENOTES10, INCLUDE IN ERRATAS10?, INCLUDED IN ERRATAS10, as they are decided. We try to keep it rather relaxed, but notorious even so, and each issue must be short and effectively described to not make the whole page too big. So, to-the-point descriptions of symptom and possible remedy. Sometime a link directly to a bug comment where a good workaround is described, or other resource that may help.

This English version errata is the master, German version usually kept updated, other languages often lag and miss being kept updated.

Boot

Also see Graphics.

Live images

Non-working graphics

By default the Live images allow the X.org display server to automatically configure itself. If you have no graphical display at the end of the boot cycle, try removing noxconf from the boot options in the initial boot menu (press e to edit the boot options), which enables service_harddrake to perform the display configuration. This may also help to force the initial language and locale selection dialogue to be duplicated on each monitor when you have two or more monitors connected, instead of being spread across them.

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

If you don't get a graphical display on a laptop with hybrid graphics, as well as removing noxconf, try replacing xdriver=free with xdriver=intel. This will force the system to use the Intel GPU which often is the one electrically connected to the monitor.

If persistence is enabled with the Live image, your settings will be preserved.

Live installer

mga#33135 If using an updated Live system (using persistence or it is updated while running) and there is no internet connection during install but updates to grub2 or dependencies exists, installer will fail the last step of install as it fail retrieving the needed packages. WORKAROUND is to disable the online repositories - before starting the installer. Note that the internal default Live repositories need to be enabled. For more information see notes on Live installer.

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 the Live install manual.

Installer images

Intel Rapid Storage Technology, RST incompatibility

If your device is using RST (Intel Rapid Storage Technology) (default for many new devices), you must read Install on device using RST.

Crashes in install process

Crash before the end of install

mga#31628 At least one case has been reported where the installation process crashes on an old BIOS laptop before completion. It is possible that you will get a bootable Mageia 9 after restarting. Try a full update immediately.

Crash at end of install

mga#27838 Some computers have buggy firmwares, causing writes to EFI NVRAM to fail at end of Mageia installation. Workaround: When configuring the bootloader at end of the install: Select rEFInd instead of GRUB, check "Install in /EFI/BOOT", uncheck the option to store to NVRAM.

NetInstaller

mga#28225 On some UEFI machines, the NetInstaller ISO boots with a Grub error message: error: ../../grub-core/video/readers/png.c:595 invalid filter value And shows Grub2 menu using text mode instead of graphic. Functionality is not affected; it is just a cosmetic quirk.

USB memory formatted with Ventoy

Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)/EFI files to the USB drive and boot them directly.

After booting a network image, if the source of the Mageia installation (could be a DVD Classic installer or local copy of Mageia's tree of files) is in the Ventoy labelled partition (i.e. where the ISO images must be stored) you may have to unplug and replug the USB device to get access to the partition. Comment#23 in mga#28371

Other workaround is reserve some space at the moment of format the USB memory with Ventoy, format that partition with any of the filesystems supported by the installer and store the source of Mageia installation in that partition (Comment 33 in mga#28371).

Note: Of course if you have one of the DVD Classic installation images you can instead directly select it from the Ventoy's boot menu.

To use the 32-bit Classic installer on USB as a repository

After system install, the Classic Installer ISOs can be utilized as a repository, to install software from without using internet - if you have left enabled the CDROM entries in the urpmi media.
The 64 bit ISO works for this both when placed on DVD and on a USB stick.
The 32 bit ISO works for this directly for DVD, but not USB. To allow the USB install ISO to function as a repository, do the following:
As root, manually mount the ISO filesystem by
mount /dev/sdX /mnt
replacing sdX with the appropriate drive identifier, e.g sdb, and noting that is the raw disk device, not a partition (e.g. not sdb1).
urpmi will then be able to use the USB stick as an install source.

Graphics

For how to change driver and some other tips see here.

Desktops

Various

mga#34205 On systems which got upgraded from Mageia 9, with LXDE desktop + lxdm as desktop manager, some applications try to open a bus for root. When run from a terminal, messages like this appear:

Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied

Manual Fix In Desktop Session Settings lxsession-edit -> Automatically Started Applications, enable AT-SPDI-D-Bus, close and restart the session.

mga#34836 After installation, the default login is set to IceWM-session. This is due to the alphabetical order of the desktop sessions. WORKAROUND: Simply select the desired desktop session on the login manager screen where you enter your username and password.

Under Wayland

LXQt and Wayland

mga#34495 The Mageia Control Center and other GUI tools may not open after entering the password. WORKAROUND: Use kwin_wayland as window manager for the LXQt Wayland session.

Software

Chromium browser

Currently we do not have a permanent maintainer for Chromium and cannot provide updates in time. WORKAROUND: Install Chromium via Flatpak or use the Chrome rpm from Google.

Various software

mga#34293 Some KDE applications like plasmatube, may fail when installed on non Plasma Desktop systems. WORKAROUND: See mga#34812#c3

mga#34634 - CodeBlocks: For now, we had to disable the wxSmith plugin.

Upgrade issues

Be sure to follow one of the procedures in Release Notes. Avoid screen saver interfering! mga#25251

If upgrade failed

Possible reasons

• Interrupted internet, interrupted power...
• For online updates, if your system use dkms and you have forgotten to update and reboot to latest kernel, per instructions, dkms fail.
• Various other...

Remedies

Do a full update. I.e in a terminal use the command urpmi --auto-update. When everything is updated, reboot.

If problems downloading packages, see Downloading Software.

If your system fail to boot to desktop: In the boot menu select "Advanced options for Mageia", then the item with highest kernel version containing "(recovery mode)", give root password, issue telinit 3 (enables network), then log in as root and issue the urpmi command.

If you can not boot to a usable state, perform an upgrade using a traditional DVD or netinstall installer. It will try to resolve dependencies and missing packages. Remember to not format any partition. Alternatively use DNF to synchronize packages and fix dependencies per below.

Ask for help in our forum :)

If all upgrade attempts fail, the fallback is to do a fresh install, possibly keeping (not formatting) /home.

No upgrade offered by the applet

The applet in system tray that notifies when normal updates exist for your system, will also notify when you can upgrade to a new Mageia release.

We delay enabling this message for some time after release date in order to solve issues found by early installers and upgraders. So just wait, or upgrade per methods described in the Release Notes. Upgrading was enabled in September 2023.

Removed packages

Generally, see at end of Release Notes. See also mga#32127

VirtualBox 32 bit host is no longer since Mageia 8.