From Mageia wiki
Jump to: navigation, search
(Miscellaneous: +#24362 Networking, download=wget)
(Intel: #29587)
 
(196 intermediate revisions by 12 users not shown)
Line 3: Line 3:
  
 
{{multi language banner|[[Mageia_8_Errata-de|Deutsch]] ; [[Mageia_8_Errata|English]]  ; [[Erratas de Mageia 8|Español]] ; [[Mageia_8_Errata-fr|Français]] ; [[Mageia_8_Erratas do Mageia|Português(Portugal)]] }}
 
{{multi language banner|[[Mageia_8_Errata-de|Deutsch]] ; [[Mageia_8_Errata|English]]  ; [[Erratas de Mageia 8|Español]] ; [[Mageia_8_Errata-fr|Français]] ; [[Mageia_8_Erratas do Mageia|Português(Portugal)]] }}
<!--'''This information is available in other languages''':<br />
 
 
* [https://wiki.mageia.org/de/Mageia_8_Errata Deutsch]
 
* [[Mageia_8_Errata|English]]
 
* [[Erratas_de_Mageia_8|Español]]
 
* [[Mageia_8_Errata-fr|Français]]-->
 
 
  
 
== Notes ==
 
== Notes ==
Line 17: Line 10:
 
''Old Errata version for Mageia 8 RC [https://wiki.mageia.org/mw-en/index.php?title=Mageia_8_Errata&oldid=50564 is here.]''
 
''Old Errata version for Mageia 8 RC [https://wiki.mageia.org/mw-en/index.php?title=Mageia_8_Errata&oldid=50564 is here.]''
  
''' '' 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.
+
''' '' 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 [http://mirrors.mageia.org/status reach your mirror].
  
 
Only 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.
 
Only 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.
Line 28: Line 21:
  
 
== Boot ==
 
== Boot ==
 +
 +
Also see [[#Graphics|Graphics]].
 +
 +
{{Bug|27117}} - If rootfs is btrfs, and /boot is on rootfs, GRUB complains about ../../grub-core/commands/loadenv.c:216:sparse file not allowed.  This is only cosmetic. '''Manual fix''' in [https://bugs.mageia.org/show_bug.cgi?id=27117#c3 Comment 3].
 +
 +
{{Bug|32165}} - Default boot selection: When you select in grub menu an option different to default (other OS or old kernel version by example), at next reboot that option has become the new default and will be booted if you don't select other. ''This behaviour is expected and has become a standard'' in Linux distributions, see the bug if you want to change it.
  
 
== Live images ==
 
== Live images ==
 +
 +
{{bug|28768}}  The '''draklive manual''' embedded on Live ISOs lacks one page, thus the menu entry "Updates" doesn't work. The full manual is available '''[https://doc.mageia.org/draklive/8/en/content/index.html online.]'''
 +
 +
=== 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 {{keypress|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 [[Persistent_live_systems|persistence]] is enabled with the Live image, your settings will be preserved.
 +
 +
=== Non-working WiFi cards ===
 +
 +
Some WiFi hardware from Broadcom is known not to work, because they only work with Broadcom's proprietary driver, which we cannot have pre-built on the ISOs (because of licensing issues), and which needs be loaded at boot time. Once Mageia is installed you can configure the WiFi and reboot. Similarly, if [[Persistent_live_systems|persistence]] is enabled with the Live, you can configure the WiFi, and in following boots it will work.
 +
 +
=== 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.<!--[https://bugs.mageia.org/show_bug.cgi?id=19949#c21 bug 19949 comment 21]-->
 +
See also [https://doc.mageia.org/draklive/8/en/content/setupBootloader.html our Mageia 8 version of the Live install manual].
  
 
== Installer images ==
 
== Installer images ==
Line 43: Line 65:
 
* 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. {{Bug|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. {{Bug|28225}}
  
* If the source of the Mageia installation is in a USB device formatted with '''exFAT''' filesystem you may have to unplug and replug the USB device to get access to the partition. [https://bugs.mageia.org/show_bug.cgi?id=28371#c23 Comment#23 in mga#28371]
+
==== USB memory formatted with Ventoy ====
 +
[https://www.ventoy.net/en/index.html {{prog|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. [https://bugs.mageia.org/show_bug.cgi?id=28371#c23 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 ([https://bugs.mageia.org/show_bug.cgi?id=28371#c33 Comment 33 in mga#28371]).
  
=== 32-bit installer must be on DVD to work as repository ===
+
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.
  
After system install, the Classic Installer ISOs can be utilized as a repository, to install software from without using internet.
+
=== To use the 32-bit Classic installer on USB as a repository ===
+
 
The 64 bit ISO works for this both when placed on DVD and on a USB stick. The 32 bit ISO does not work as a repository from USB.
+
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.
 +
<br>
 +
The 64 bit ISO works for this both when placed on DVD and on a USB stick.<br>
 +
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:<br>
 +
As root, manually mount the ISO filesystem by <br>
 +
<code>  mount /dev/sdX  /mnt </code> <br>
 +
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).<br>
 +
urpmi will then be able to use the USB stick as an install source.
  
 
== Graphics ==
 
== Graphics ==
 +
 +
''How to change driver: see [[Setup_the_graphical_server|here]].''
 +
 +
{{Bug|20835}} - '''Avoid the {{keypress|Test}} button in MCC graphic setup!''' 1.) it may give false negative.  2.) it may '''hang''' your system.  3.) it may cause you to be '''unable to log in to desktop''' beacuse user's .Xauthority file got set to owned by root - '''Fix:''' ''(for 3.)'' Set user and group on ~/.Xauthority to your normal user. ''(Ask in forum if you need help.)''
 +
 
=== AMD/ATI ===
 
=== AMD/ATI ===
  
FIXED(?) {{bug|28154}} - Live media not booting with some Radeon HD GPU or system installed with Classic ISO.
+
''Described problems are most visible on Live media or system installed with Classic ISO without update repos enabled.  Some updates have improved the situation, some resume fixes coming in kernel, and most importantly see the explanation and workaround below.''
 +
 
 +
* Boot problem with some Radeon HD GPU. ''Example: {{bug|28154}}''
 +
 
 +
* Resuming problem, despite booting OK. ''Example: {{bug|28863}}''
  
For AMD graphic cards based on Southern Islands family (Tahiti, Pitcairn, Oland, Verde, Hainan) and Sea Islands family (Kaveri, Bonaire, Hawaii, Kabini, Mullins) we are now defaulting to the newer amdgpu driver instead of the older radeon, and want feedback if it works properly or not on your hardware.
+
* Legacy VGA not working yet ''(upstream problem)'', so for instance if you have '''dual screen with one on VGA''', the VGA connected one don't work. ''Example: {{bug|28817}}''
  
If it does not work for you, you can fall back to the older driver by adding the following on [[How_to_set_up_kernel_options#With_Grub_2_bootloader_2| kernel command line]]:
+
''Explanation:'' For AMD graphic cards based on Southern Islands family (Tahiti, Pitcairn, Oland, Verde, Hainan) and Sea Islands family (Kaveri, Bonaire, Hawaii, Kabini, Mullins) we are now defaulting to the newer amdgpu driver instead of the older less developing radeon.  We appreciate feedback if it fails on your hardware, see mga# above.
  
For Southern Island cards:
+
'''Workaround''' for both cases above: '''use the older radeon''' driver (like Mageia 7 default) by adding the following on [[How_to_set_up_kernel_options#With_Grub_2_bootloader_2| kernel command line]]:
radeon.si_support=1 amdgpu.si_support=0
 
  
For Sea Islands cards:
+
For Southern Island cards: {{cmd|<nowiki>radeon.si_support=1 amdgpu.si_support=0</nowiki>}}
radeon.cik_support=1 amdgpu.cik_support=0
+
 
 +
For Sea Islands cards: {{cmd|<nowiki>radeon.cik_support=1 amdgpu.cik_support=0</nowiki>}}
 +
 
 +
First use {{cmd|drakx11}} ({{prog|Mageia Control Center}} Section {{menu|Hardware > Set up the graphical server}} item {{menu|Graphic Card}}) to set driver to ''"ATI radeon HD 4870 and earlier"'' (at least for Bonaire cards).
 +
 
 +
In case booting to graphic desktop fail, use {{keypress|Ctrl}}+{{keypress|Alt}}+{{keypress|F2}} (or reboot to maintenance mode) to open a console and launch {{cmd|drakx11}} to select another driver, and reboot (type {{cmd|reboot}}.
  
 
=== Nvidia ===
 
=== Nvidia ===
 +
 
Nvidia has neglected to fix security issues in their 340 series driver, so we had to drop it from official repos.  See [[Mageia_8_Release_Notes#Proprietary_NVIDIA_driver|Release Notes]].
 
Nvidia has neglected to fix security issues in their 340 series driver, so we had to drop it from official repos.  See [[Mageia_8_Release_Notes#Proprietary_NVIDIA_driver|Release Notes]].
 +
 +
{{Bug|31994}} - '''Virtual tty terminals are black''' (i.e Ctrl-Alt-F3), after booted to graphics mode (desktop). And shifting back and forth may hang the system. '''Workaround''' [[Setup_the_graphical_server#Known_Nvidia_issues|here.]]  Note: ''This did not happen in release version of Mageia 8 but have been introduced by updates. Similar in other distributions.''
 +
 +
=== Intel ===
 +
{{Bug|29587}} - Random display lines get shifted right. Intel Coffee|TigerLake .... GT2 graphics
 +
 +
{{Bug|30189}} '''More than one screen on late Intel X5XX chipsets.'''  Intel released new hardware but problems not yet fixed in their driver.  Workaround is implemented in Mageia kernels 5.15.32 and up in normal updates, and 5.16.14 and up in backports.  So if you are affected, boot with only one screen connected, and update your system.
 +
 +
=== LibreOffice window tiny ===
 +
{{Bug|30152}}. The extent of this problem is not known, but seem related to desktops using Qt, and using VGA port to monitor. LibreOffice windows may start tiny. See bug ''[https://bugs.mageia.org/show_bug.cgi?id=30152#c17 Comment 17]''. '''Workaround:''' drag the border of the window and resize to full size, at less twice for each LibreOffice affected application, one from the menu launcher and one opening a related file from the file manager.
 +
 +
=== Recording your desktop ===
 +
{{bug|29405}}. Strange results when '''recording your desktop'''. The extent of this problem is not known. The '''workaround''' in [https://bugs.mageia.org/show_bug.cgi?id=30152#c7 Bug 30152 comment 7] solves the issue.
  
 
== Desktops ==
 
== Desktops ==
Line 73: Line 137:
 
{{Bug|23929}} - The folder Desktop in $HOME is not translated with '''Plasma or MATE only''' DE installation
 
{{Bug|23929}} - The folder Desktop in $HOME is not translated with '''Plasma or MATE only''' DE installation
  
{{Bug|28378}} - '''SDDM greeter''' does not remember previous session. '''Manual fix:''' In {{file|/etc/sddm.conf}} in the line {{cmd|<nowiki>RememberLastSession=false</nowiki>}} change false to true. This will be in an update. That update also set {{cmd|<nowiki>RememberLastUser=false</nowiki>}}, you may set it true if you like to have last user preselected at login.
+
{{Bug|25877}} - '''Netapplet/Mgaapplet/nm_applet''' with '''Cinammon''' or '''Xfce''':  When the applet is in a panel at the bottom of the screen, it's pop-up appears only as a black bar at the bottom of the screen. '''Workaround [https://bugs.mageia.org/show_bug.cgi?id=25877#c1 here.]'''
 +
 
 +
{{Bug|27601}} - '''The boot hangs with a black screen''' and the mouse cursor still mobile. This is due to a change of hostname during '''SDDM''' start, set by avahi or networkmanager when the hostname is localhost. The workaround is to set the hostname to a personal value, for example with the command ''hostnamectl set-hostname myhost.local''.
 +
 +
'''FIXED''' {{Bug|28378}} - '''SDDM greeter''' does not remember previous session. '''Manual fix''' if upgrade have been made before the fix: In {{file|/etc/sddm.conf}} in the line {{cmd|<nowiki>RememberLastSession=false</nowiki>}} change false to true.
  
 
=== Plasma ===
 
=== Plasma ===
  
'''Wayland''' session with Nvidia's 455 (current) nonfree-drivers is available by making sure that "nokmsboot" is removed and "nouveau.modeset=0" is passed to Kernel command line. Note {{bug|27296}} - Plasma Wayland session broken, and {{Bug|28365}} - Control Center does not start in Plasma Wayland ( temporary fix: as normal user, first issue {{cmd|xhost +si:localuser:root}} )
+
'''Wayland''' session with Nvidia's {{prog|nvidia-current}} proprietary drivers is available by making sure that "nokmsboot" is removed and "nouveau.modeset=0" is passed to Kernel command line. Note {{bug|27296}} - Plasma Wayland session broken, and {{Bug|28365}} - Control Center does not start in Plasma Wayland - '''Temporary fix:''' as normal user, first issue {{cmd|xhost +si:localuser:root}}
  
'''Compiz''' desktop effects is no longer compatible with Plasma. If you use it in Plasma on Mageia 7 then disable it in {{prog|Mageia Control Center}} {{menu|Hardware -> Configure 3D Desktop effects}} - '''before''' upgrade, and if you don't want Compiz for another desktop environment, uninstall it.  After install/upgrade of Mageia, you find desktop effects at {{menu|System Settings}} (icon in panel) {{menu|-> Workspace -> Workspace Behavior -> Desktop Effects}}.
+
'''Wayland:''' Plasma panels: {{Bug|30654}}: launchers at the top left corner of the screen don't work. '''Workaround:''' Add a spacer in the panel at left/top.
  
'''Dolphin''' right click extension ''kde-rootactions-servicemenu'' is removed as it is unmaintained upstream and have issues.
+
'''Compiz''' desktop effects is no longer compatible with Plasma. If you use it in Plasma on Mageia 7 then disable it in {{prog|Mageia Control Center}} : {{menu|Hardware -> Configure 3D Desktop effects}} - '' '''before''' '' upgrade, and if you don't want Compiz for another desktop environment, uninstall it.  After install/upgrade of Mageia, you find desktop effects at {{prog|System Settings}} (slider icon in main launch menu) {{menu|Workspace -> Workspace Behavior -> Desktop Effects}}.
  
{{bug|27147}} - Multi-users '''successive logins''', plasmashell no longer runs log on to whatever user after going into sleep
+
'''Dolphin''' right click extension ''{{prog|kde-rootactions-servicemenu}}'' is removed as it is unmaintained upstream and have issues.
  
{{Bug|27183}} - Default Mageia '''spectacle integration''' settings missing in plasma5 systemsettings - ''On some occasions after upgrade.'' '''FIX:''' Launch Spectacle, press {{menu|Configure -> Shortcuts -> Launch Spectacle}}. Change the setting from "Custom" to "Default" (Print screen), and confirm in the popup asking to reassign.
+
{{bug|27147}} - Multi-users '''successive logins''', plasmashell no longer runs log on to whatever user after going into sleep.
  
{{bug|27362}} - startplasma-x11 spawns '''zombie''' process ''(may make it sluggish)''
+
{{Bug|27183}} - '''Screenshot not launched by PrintScr key''' - Default Mageia spectacle integration settings missing in plasma5 systemsettings - ''On some occasions after upgrade.'' '''Manual fix:''' Launch Spectacle, press {{menu|Configure -> Shortcuts}}. Select each entry under "Spectacle" and change the setting to "Default", and confirm in the popup asking to reassign. OK the main dialogue. If PrtScn key still does not make Spectacle show, then rename {{file|~/.local/share/kglobalaccel/org.kde.spectacle.desktop}} ''(Maybe add "X" to the end)''. It may contain custom settings, you can delete it, see [https://bugs.kde.org/show_bug.cgi?id=429634#c5 upstream bug].
  
{{bug|28095}} - '''Avatar''' Change not working on Classic Install Mageia 8 but does work on Live
+
'''FIXED''' by Mageia 8 updates: startplasma-x11 spawns '''zombie processes''' - {{bug|27362}} (many packages), {{bug|28824}} (qtbase), {{bug|28859}} (systemd)
 +
 
 +
{{bug|28095}} - '''Avatar''' Change not working on Classic Install Mageia 8 but does work on Live. '''[https://bugs.mageia.org/show_bug.cgi?id=28095#c5 Manual fix here.]'''
  
 
{{bug|28287}} - new plasma workspace does not allow '''unlocking of widgets when upgrading''' from older version.
 
{{bug|28287}} - new plasma workspace does not allow '''unlocking of widgets when upgrading''' from older version.
Plasma5 desktop and panel widgets cannot be locked/unlocked in Plasma version 5.18 onwards. This means that any such widgets locked before the upgrade cannot be unlocked after. '''So before upgrading''', be sure to UNlock all such widgets.
+
Plasma5 desktop and panel widgets cannot be locked/unlocked in Plasma version 5.18 onwards. This means that any such widgets locked before the upgrade cannot be unlocked after. '''So ''before'' upgrading''', be sure to UNlock all such widgets.
 
If you do find locked widgets after upgrading, this will unlock them:
 
If you do find locked widgets after upgrading, this will unlock them:
 
{{cmd|$ qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)"}}
 
{{cmd|$ qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)"}}
  
{{bug|28299}} - '''GTK apps complain''' (in log) about missing window_decorations.css. - '''[https://bugs.mageia.org/show_bug.cgi?id=28299#c1 Manual fix here]'''
+
{{bug|28299}} - '''GTK apps complain''' (in log) about missing window_decorations.css. - '''[https://bugs.mageia.org/show_bug.cgi?id=28299#c1 Manual fix here.]'''
  
{{bug|28342}} - '''No shadows on GTK menus''' in GTK apps under Plasma. - When the theme "Breeze" is set in {{menu|System Settings -> Application Style -> Configure GNOME/GTK Application Style}}, there is no shadow in GTK right-click and GTK menus. Workaround: Set it to "Adwaita" (which is default).
+
{{bug|28342}} - '''No shadows on GTK menus''' in GTK apps under Plasma. - When the theme "Breeze" is set in {{prog|System Settings}} : {{menu|Application Style -> Configure GNOME/GTK Application Style}}, there is no shadow in GTK right-click and GTK menus. '''Workaround:''' Set it to "Adwaita" (which is default).
 +
 
 +
{{bug|28623}} - '''Alt+F2 fail to launch the Run command dialogue. - Manual fix:''' In {{prog|System Settings}} : {{menu|Shortcuts -> System Services -> KRunner *)}} , unfold section KRunner *), and under "Default Shortcuts" checkmark "Alt+F2".  If it asks for confirmation, say yes.  Apply, close System Settings and try if it works. If it does not, repeat the procedure.  If still not, see bug. ''*) KRunner may be translated to something corresponding to "Run program".''
 +
 
 +
{{bug|28827}} - '''KDE Connect''' can not browse into devices. ''Explanation:'' If Mageia was installed using Classic Installer ISO without online repositories enabled, the suggested package {{prog|sshfs-fuse}} will not be installed. '''Manual fix:''' Install {{prog|sshfs-fuse}}.
  
 
=== GNOME ===
 
=== GNOME ===
  
'''Wayland:''' 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 {{cmd|nowayland}} to the boot options in the initial boot menu (press {{keypress|e}} to edit the boot options).
+
'''Network:''' By default, the NetworkManager service is enabled in place of the old network management services. You can 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. Network configuration via the MCC/drakconnect should also work in most cases.
 +
 
 +
'''Internationalisation:''' A default input method is not set in desktop session. You need to set it manually in Setting. {{bug|15793}}
 +
 
 +
==== GNOME and Wayland ====
  
'''Network:''' By default, the NetworkManager service is enabled in place of the old network management services. You can 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. Network configuration via the MCC/drakconnect should also work in most cases.
+
By default, GNOME uses the Wayland display server. ''If'' Wayland fails to start, GNOME will automatically fall back to using the X.org display server - but in rare cases, this fails. If the GNOME desktop fails to launch, or if you experience display problems, you can try forcing GNOME to use the X.org display server by editing  {{file|/etc/X11/gdm/custom.conf}} and set ''WaylandEnable=false''.   <!-- per https://bugs.mageia.org/show_bug.cgi?id=31624#c23 -->
 +
 
 +
For GNOME Live ISO there is a shortcut: add ''nowayland'' to the boot options in the initial boot menu (press {{keypress|e}} to edit the boot options). ''(But if you use persistence, use the method above.)''
  
 
=== Xfce ===
 
=== Xfce ===
Line 114: Line 194:
 
=== LXQt ===
 
=== LXQt ===
  
{{Bug|28360}} '''The compositor''' for transparency, generally used with Openbox, used to be {{pkg|compton}}. This one is deprecated and replaced by '''{{pkg|picom}}. If you upgrade from Mageia 7''', the configuration file {{file|~/.config/compton.conf}} can have some incompatible parameters which need to be edited. - Or simply delete that file.  Unfortunately we have no Picom configuration tool yet.
+
{{Bug|28360}} '''The compositor''' for transparency, generally used with Openbox, used to be {{prog|compton}}. This one is deprecated and replaced by '''{{prog|picom}}. If you upgrade from Mageia 7''', the configuration file {{file|~/.config/compton.conf}} can have some incompatible parameters which need to be edited. - Or simply delete that file.  Unfortunately we have no Picom configuration tool yet.
  
 
Picom looks for configuration in the following order: {{file|~/.config/picom.conf}}, {{file|~/.config/compton.conf}}, {{file|/etc/xdg/picom.conf}}. That means a customized picom.conf can reside in {{folder|~/.config/}} for a personal configuration or in {{folder|/etc/xdg/}} for a system wide configuration. So for customisation per user copy {{file|/etc/xdg/picom.conf}} to {{folder|~/.config/}} and edit it there.
 
Picom looks for configuration in the following order: {{file|~/.config/picom.conf}}, {{file|~/.config/compton.conf}}, {{file|/etc/xdg/picom.conf}}. That means a customized picom.conf can reside in {{folder|~/.config/}} for a personal configuration or in {{folder|/etc/xdg/}} for a system wide configuration. So for customisation per user copy {{file|/etc/xdg/picom.conf}} to {{folder|~/.config/}} and edit it there.
Line 125: Line 205:
  
 
Some help, if needed: 1) Launch {{cmd|picom}} from a terminal and see the output, exit with Ctrl-C.  2) {{file|/etc/xdg/picom.conf}} have comments.
 
Some help, if needed: 1) Launch {{cmd|picom}} from a terminal and see the output, exit with Ctrl-C.  2) {{file|/etc/xdg/picom.conf}} have comments.
 +
 +
---
 +
 +
'''FIXED''' for new users: {{Bug|28407}} '''Default terminal in pcmanfm''' shall be qterminal, not xterm. '''Manual fix''' for existing users in already made upgrade or install: Use pcmanfm-qt preferences GUI. ''(Our general policy is to not force user preferences.)''
  
 
== Software ==
 
== Software ==
 +
 +
=== Firefox ESR ===
 +
 +
'''FIXED''' by an update {{Bug|29064}} - A packaging issue caused various problems with a few sites, solving i.e. {{Bug|27374}}, {{Bug|28359}}.
 +
 +
Note that still a few sites choose to not accept Firefox ESR (even upstream version), and demand non ESR version.  You can help informing the problematic sites that [https://support.mozilla.org/en-US/kb/switch-to-firefox-extended-support-release-esr Firefox ESR does not come with the latest features but it has the latest security and stability fixes].
 +
 +
As workaround you can try using an user agent switcher to spoof a non-ESR Firefox. Alternatively you can install the Firefox non-ESR version for example by using [[Flatpak]] or other [[Ways_to_install_programs|Ways to install programs]].
 +
 +
=== Flatpak ===
 +
 +
Plasma Discover and Gnome-software prefer [[Flatpak]] [https://bugs.mageia.org/show_bug.cgi?id=27620#c5 over Mageia RPM packages].
 +
 +
=== Backports problems ===
 +
 +
{{Bug|29830}} - drakrpm autoselects dependencies from a disabled repo.  - This may install incompatible versions.
 +
 +
When you have backports repository configured (which is normal), Mageia graphical tools choose dependencies from it, even when it, as normal, is not enabled.  A typical example is that PHP8.1 get installed as dependency for something needing PHP, but some such applications need PHP8.0.x, which should be installed from core updates repository.  '''Workaround:''' use command line urpmi, or ''' ''remove'' ''' the backports repositories:  Use command line {{cmd|urpmi.removemedia -y Backports}} or graphical tools: Start {{cmd|drakrpm-edit-media}} which is {{prog|Mageia Control Center}} section {{menu|Software Management -> Configure media sources for install and update}}, shift-click all backport media and click the button "Remove".  '''FIX:''' If you already have gotten the too high versions, you can downgrade by disabling (or removing) backports repos, and issue {{cmd|urpmi --downgrade affected packages}}. For checking you can issue {{cmd|urpmq --not-available}} to list packages and versions that are not in enabled repos. ''(Possibly not all of them need be downgraded to fix your specific problem, and some may have been installed from other repos currently not configured or enabled, or other means.)''
 +
 +
{{Bug|30084}} - mgaapplet does not list all updates available in Core Updates if Core Backports is enabled
 +
 +
=== Mageia Control Center ===
 +
 +
(Rare) Icons are invisible, but clickable in blind, after selecting a pane in left field:
 +
 +
{{Bug|30332}} - With updated webkit2 >=2.36, drakconf comes up with a blank window on both arches on real hardware and in VirtualBox guests for some graphics driver/settings.
 +
 +
'''Workaround:''' For 32-bit systems:, as root {{cmd|urpmi --downgrade libjavascriptcore-gir4.0-2.34.6-1.mga8 libjavascriptcoregtk4.0_18-2.34.6-1.mga8 libwebkit2gtk4.0_37-2.34.6-1.mga8 libwebkit2gtk-gir4.0-2.34.6-1.mga8 webkit2-2.34.6-1.mga8 webkit2-jsc-2.34.6-1.mga8}} - ''Note: For 64 bit systems use "lib64" instead of "lib".''
 +
Also as root, add two lines to {{file|/etc/urpmi/'''skip.list'''}} to avoid the packages getting updated:
 +
: /javascriptcore/
 +
: /webkit2/
  
 
=== Mageia Welcome ===
 
=== Mageia Welcome ===
  
{{bug|28328}} - '''Steam''' cannot be installed with the one-click button proposed with Mageia Welcome if 32bits repositories are not enabled, as it is the case by default. - [[Mageia_8_Release_Notes#32_bit_repos_on_64_bit_systems| 32 bit repositories should be enabled]] to complete the installation.
+
'''FIXED''' by Mageia 8 update (gives information) {{bug|28328}} - '''Steam''' cannot be installed with the one-click button proposed with Mageia Welcome if 32bits repositories are not enabled, as it is the case by default. - [[Mageia_8_Release_Notes#32_bit_repos_on_64_bit_systems| 32 bit repositories should be enabled]] to complete the installation.
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28806}} - '''MageiaWelcome''' MCC tab display incorrectly for Chinese and Japanese.
 +
 
 +
=== Phone USB connection ===
 +
 
 +
'''Android, MTP:''' {{bug|28216}}. The {{prog|libusb}} packages have been updated to include backported upstream fixes to improve Android phones USB connectivity. As you know there is a vast variety of Android devices. - Where there are still problems, try another method to connect, i.e over wifi using {{prog|kdeconnect-kde}} (works for more than Plasma, and provide more than file transfer) or filesyncing serverless using i.e {{prog|Syncthing}} or a cloud service. For more information visit our wiki page [[File_transfer_with_Android_devices|File transfer with Android devices]].
 +
 
 +
'''iPhone:''' {{bug|28669}} The packages {{prog|ifuse}} and {{prog|usbmuxd}} are missing by default. '''Manual fix:''' install them.
 +
 
 +
=== Virtualization software ===
  
=== Flatpak ===
+
To make virtualization software works, you need the machine virtualization support is enabled, but are usually disabled by default, we recommend read [https://support.microsoft.com/en-us/windows/enable-virtualization-on-windows-11-pcs-c5578302-6e43-4b4b-a449-8ced115f58e1 this link], could help you find how enable virtualization support on your machine.
 +
<br>
  
Plasma Discover and Gnome-software prefer [[Ways_to_install_programs#Flatpak|Flatpak]] [https://bugs.mageia.org/show_bug.cgi?id=27620#c5 over Mageia RPM packages].
 
  
 
=== Various software ===
 
=== Various software ===
 +
 +
{{Bug|9683}} - '''LibreOffice''' langpacks are not installed for Chinese and Portugese-Brazil. '''Manual fix:''' install them.
 +
 +
{{Bug|28963}} - '''LibreOffice''' package {{prog|libreoffice-'''emailmerge'''}} and the task package {{prog|libreoffice}} are not installed when installing from the classical ISO images. '''Manual fix:''' install {{prog|libreoffice}}.
 +
 +
{{Bug|22425}} - '''Draksnapshot''' fail to launch.
 +
 +
{{Bug|27340}} - '''FreeCAD''' GUI fails to display. '''Manual fix:''' delete {{file|~/.mozila/plugins/mozplugger0.so}} left over from a Mageia 7 to 8 upgrade.
  
 
{{Bug|28097}} - '''xviewer''' seg fault; also, not in application menus
 
{{Bug|28097}} - '''xviewer''' seg fault; also, not in application menus
  
FIXED by an update {{Bug|28363}} - VLC crashes when opening an MKV file when the video codec is AV1
+
'''FIXED''' by an update {{Bug|28363}} - '''VLC''' crashes when opening an MKV file when the video codec is AV1
 +
 
 +
{{Bug|28683}} - '''OGMRip''' fail to launch.  Problem is also seen in other distros, and upstream seem stale.
 +
 
 +
{{Bug|28791}} // {{Bug|31071}} - '''qt-fsarchiver''' Even after the update 2023-06-15 it have quirks: need sudo, and asks an extra time for user password.  '''fsarchiver''' do not handle [[Mageia_9_Errata#ext4_format_uses_feature_C12_which_are_not_recognized_by_older_fsck|the new ext4 version]] such as Mageia 9 and some other distros now use. ''Details, see bugs.'' Also see note on bug 31641 below.
 +
 
 +
{{Bug|28814}}, {{Bug|28840}}, {{Bug|30462}} '''Wine''' miss a few dependencies, especially for 32 bit libs. (Thus also '''PlayOnLinux'''.) '''Manual fix''' and also other tips [[Ways_to_install_programs#Running_MSWindows_programs|'''here''']]. Also see {{Bug|16273}}
 +
 
 +
{{Bug|30937}} - '''Thunderbird''' leave temporary files behind if set to open pdf in external program. [https://bugzilla.mozilla.org/show_bug.cgi?id=1793932 Upstream.] Manual workaround is to change the setting, see linked bugs.
 +
 
 +
Mageia 8 cannot mount nor fsck an ext4 partition made with some recent distributions, including Mageia 9 up to including beta 2, after which this was reverted back for compatibility, see {{Bug|31641}} and [[Mageia_9_Errata#ext4_feature_C12_is_not_recognized_by_older_fsck|the new ext4 feature C12]].
 +
 
 +
=== External software ===
 +
''Not packaged by Mageia, only prominent external software is to be listed here.''
 +
 
 +
{{Bug|30103}} - Video problems with '''Remote Desktop Tools''' ''(VNC, TeamViewer, AnyDesk, etc)'' ''' Workaround:''' Firstly, at least TeamViewer and Anydesk are not Wayland compatible, so use Xorg.  Problems can often be mitigated by on host computer selecting a lower resolution and/or switching off desktops effects (in for example Plasma: press Shift-Alt-F12), but better: in {{file|/etc/X11/xorg.conf}}, under devices, add Option "LinearFramebuffer".
 +
 
 +
=== Mageia tools ===
 +
 
 +
{{Bug|15829}} - '''Install and Remove Software (rpmdrake)''': starts in groups mode but {{menu|view}} menu says '''"All packages, alphabetical"''' instead, if you need view packages in alphabetical order select other option and select again '''"All packages, alphabetical"'''
 +
 
 +
{{Bug|24828}}, {{Bug|29406}} - '''Install and Remove Software (rpmdrake)''': search for applications with GUI+desktop file to install or remove produce an empty list if the package is provided by third party repositories. '''Workaround''': change the filter '''"Packages with GUI"''' to '''"All"'''
 +
 
 +
<br>
 +
 
 +
== Security ==
 +
 
 +
=== Boot of system with cyphered partitions ===
 +
{{bug|19800}} - [http://hmarco.org/bugs/CVE-2016-4484/CVE-2016-4484_cryptsetup_initrd_shell.html 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 “rd.shell=0” to the kernel command line
 +
 
 +
=== Change in defaults of system-wide crypto-policies  ===
 +
 
 +
During the development of Mageia 8, the upstream defaults of the system-wide cryptographic policies (which come with the package {{prog|crypto-policies}}) have changed.
 +
Previously the default was LEGACY, which allowed TLS 1.0 and 1.1 protocols. The algorithms DSA, 3DES, and RC4 were allowed, while RSA keys and Diffie-Hellman parameters are accepted if they are at least 1023 bits long.
 +
The new setting of DEFAULT allow the TLS 1.2 and 1.3 protocols, as well as the IKEv2 and SSH2 protocols. RSA keys and Diffie-Hellman parameters are accepted if they are at least 2048 bits long.
 +
 
 +
The current setting can be seen in {{file|/etc/crypto-policies/config}}
 +
 
 +
It is not advised to change the default system-wide crypto-policies back to LEGACY, please instead report bugs for applications which are not working due to those new defaults.
 +
 
 +
For more details, please have a look at [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening Red Hat Enterprise Linux 8 Security hardening - Using system-wide cryptographic policies]
  
 
== Miscellaneous ==
 
== Miscellaneous ==
 +
 +
{{Bug|31699#c28}} '''urpmi --auto-orphans''' tries to remove too much. For now, simply don't use it, or see bug for tips if you really need.
 +
 +
=== Hibernation ===
 +
 +
{{bug|28528}} - '''Resuming''' from hibernation instead start fresh. [https://github.com/dracutdevs/dracut/issues/924 Upstream bug]. '''Manual fix:''' 1) Verify that there is no line containing "add_dracutmodules" in output of {{cmd|cat /etc/dracut.conf.d/51-mageia-resume.conf}} .  2) Add the missing line by as root executing {{cmd|<nowiki>echo 'add_dracutmodules+=" resume "' >> /etc/dracut.conf.d/51-mageia-resume.conf</nowiki>}} and then generate new initrd: {{cmd|dracut -fv}} .  After dracut finish, resume shall work.  If not, you have other problem - please consult our forum.
  
 
=== Networking ===
 
=== Networking ===
Line 149: Line 334:
  
 
For a few users, the default download method intermittently fails. '''Workaround:''' Start {{cmd|drakrpm-edit-media}} which is {{prog|Mageia Control Center}} section {{menu|Software Management -> Configure media sources for install and update}}. In {{menu|Options -> Global options}} set "Download program to use" to "wget". {{bug|24362}}
 
For a few users, the default download method intermittently fails. '''Workaround:''' Start {{cmd|drakrpm-edit-media}} which is {{prog|Mageia Control Center}} section {{menu|Software Management -> Configure media sources for install and update}}. In {{menu|Options -> Global options}} set "Download program to use" to "wget". {{bug|24362}}
 +
 +
''Note: prior to wget 1.23 update in June ({{Bug|30509}}), make sure to select mirrors using https, as our release version 1.21 of wget have problems with ftp.''
 +
 +
If you already hit this (as described in {{bug|26827}}), failed downloads may result in messages like
 +
 +
{{pre|<nowiki>There was a problem during the installation:
 +
package firefox-0:91.3.0-1.mga8.x86_64 does not verify: Payload SHA256 ALT digest: BAD (Expected
 +
6ba98a0b474689bd5bbf15f361faf4116279e7c52d921ef5283db0e6f08d11c3 != 49b9a8f7b34a063e966a0133f5f84701d61ffd41ee3c595df575696a43c221bc)</nowiki>}}
 +
 +
If that happens, issue {{cmd|urpmi --clean}}, and try again (after changing to wget).
 +
 +
If that did not help, maybe the package on your mirror is broken, so remove your mirror set and add a new set, clean again, and try again:
 +
 +
To remove all repositories, either use command line {{cmd|urpmi.removemedia -a}} or graphical tools: Start {{cmd|drakrpm-edit-media}} which is {{prog|Mageia Control Center}} section {{menu|Software Management -> Configure media sources for install and update}}, shift-click all media, and click the button "Remove".
 +
 +
To add all Mageia repositories from a specific mirror, either use command line - ''example for 64 bit Mageia 8 Swedish mirror'': {{cmd|urpmi.addmedia --distrib https://ftp.acc.umu.se/mirror/mageia/distrib/8/x86_64}}, or graphical tools: in the {{prog|Configure media sources for install and update}}, Menu {{menu|File -> Add a specific mirror}}.
  
 
=== Printing ===
 
=== Printing ===
 +
 +
{{Bug|28746}} - '''Printer is not discovered.'''  For security reasons this functionality is by default not opened through the Firewall.  To enable: Checkmark "CUPS server" and "Network printer/scanner autodiscovery" in {{prog|Mageia Control Center}} Section {{menu|Security > Set up your personal firewall}}.
 +
 +
==== Printing in gtk webkit applications ====
 +
 +
{{bug|28758}} - Upstream bug in sandboxing may make printing from gtp applications such as Evolution not work. '''Workaround''', upstream links and more info see bug first post.
  
 
==== Printer duplicate - not a bug ====
 
==== Printer duplicate - not a bug ====
Line 173: Line 380:
  
 
Be sure to follow one of [[Mageia_8_Release_Notes#Upgrading_from_Mageia_7|the procedures in Release Notes]]. Avoid screen saver interfering! {{Bug|25251}}
 
Be sure to follow one of [[Mageia_8_Release_Notes#Upgrading_from_Mageia_7|the procedures in Release Notes]]. Avoid screen saver interfering! {{Bug|25251}}
 +
 +
Upgrade issues [https://bugs.mageia.org/showdependencytree.cgi?id=28393 Tracker bug].
  
 
=== If upgrade failed ===
 
=== If upgrade failed ===
Line 179: Line 388:
  
 
If all upgrade attempts fail, the fallback is to do a fresh install, possibly keeping (not formatting) {{folder|/home}}.
 
If all upgrade attempts fail, the fallback is to do a fresh install, possibly keeping (not formatting) {{folder|/home}}.
 +
 +
=== No upgrade offered by the applet ===
 +
 +
''' '' News: enabled 2021-04-04 '' '''
 +
 +
The applet in system tray that tells when normal updates exist for your system, will also tell when you can upgrade to a new Mageia release.
 +
 +
As usual, we delay enabling this message in order to solve issues found by early installers and upgraders.  So '''just wait''', or [[Mageia_8_Release_Notes#Upgrading_from_Mageia_7|upgrade per methods described in the Release Notes]].
  
 
=== Upgrade using DNF ===
 
=== Upgrade using DNF ===
  
'''Extra kernel flavour installed''' - DNF uses a different method to select kernel flavour than Mageia installer. This may result in that a system that was using the desktop kernel, after upgrade have both desktop and server installed, and server used.  Easy fix: select at boot the desktop kernel, then uninstall server kernel. {{bug|28272}}
+
'''Extra kernel flavour installed''' - DNF uses a different method to select kernel flavour than Mageia installer. This may result in that a system that was using the desktop kernel, after upgrade have both desktop and server installed, and server used.  '''Manual fix:''' select at boot the desktop kernel, then uninstall server kernel. {{bug|28272}}
 +
 
 +
=== PHP7 dropped ===
 +
 
 +
Mageia 8 have no PHP7.  This may cause problem if you have software that is not compatible with PHP8.
 +
 
 +
Examples:
 +
* [[Mageia_8_Release_Notes#Nextcloud|'''Nextcloud''' is coming in backport]]
 +
* '''FIXED''' by Mageia 8 update: '''Roundcube mail''' {{bug|28533}} '''is now ported to PHP8'''
 +
 
 +
'''Workaround:''' You may be able to compile PHP7 yourself, see [https://forums.mageia.org/en/viewtopic.php?f=7&t=14038#p82334 our forum].
  
 
=== Removed packages ===
 
=== Removed packages ===
Line 191: Line 418:
  
 
[[Mageia_8_Release_Notes#VirtualBox|There is no longer]] a VirtualBox 32 bit host.
 
[[Mageia_8_Release_Notes#VirtualBox|There is no longer]] a VirtualBox 32 bit host.
 +
 +
=== Unused packages ===
 +
 +
After upgrade, you may find that there are a lot of unused packages installed. ''(Reported as orphans, or you can not directly see what they are installed for.)''
 +
 +
Be careful - '''they may actually be needed:'''
 +
 +
The user may have third party software that requires the modules in those lib packages or requires old packages that are not lib packages. The third party software may be compiled from source, or manually
 +
copied binary files - not installed using rpm, so the package manager do not know. Also, if you alter between using DNF and urpmi, the [[Using_DNF#Warning_about_orphans_mechanisms|orphan tracking does not work]] for either of them.
 +
 +
As long as the old packages do not interfere with new packages, we have chosen to let users choose which old packages they do not need and uninstall them manually if they wish to.  (If you do, please keep a log of what you uninstall.)
 +
 +
You will also see that the updater have not only let old packages remain, but also installed corresponding upgrade Mageia versions of them - see it as a service.
 +
 +
''Even on a new install, there will be multiple versions or alternatives of some packages installed as being suggested by different packages. These packages are not required, just suggested or recommended, so are orphans from the moment they are installed.''
 +
 +
For more info see [[Removing_packages|Removing packages]].
  
 
=== Various upgrade issues ===
 
=== Various upgrade issues ===
  
''''' We are working to issue updates for solving the issues. See the bugs for the most recent news. '''''
+
If you manually upgrade by graphical tools (i.e drakrpm, not urpmi or dnf) while having Mageia 8 backport repos enabled - ''even if not configured'' - you may get too high versions of packages, not compatible with some application.  Fix and workaround see [[#Backports_problems|Backports problems]] above.
 +
 
 +
{{bug|29182}} '''Upgrading under Wayland using the mgaonline applet''' / mgaapplet-upgrade-helper does not work.  '''Workaround:''' Log out and log in using Xorg. Or use another [[Mageia_8_Release_Notes#Upgrading_from_Mageia_7|upgrading]] method.
 +
 
 +
'''Optimus / Mageia Prime''' may need you to run mageia-prime-uninstall followed by mageia-prime-install.  See [https://bugs.mageia.org/show_bug.cgi?id=24967#c45 this bug comment] and our [[Mageia-prime_for_Optimus|Mageia Prime]] wiki page.
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|27880}} - '''x2go server'''
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28007}} - '''llvm'''-11.0 mga8 packages conflicts with mga7 llvm-devel packages when updating MGA7 to MGA8
 +
 
 +
{{bug|28018}} - '''Google Earth Pro''' - See our wiki page [[Google_Earth|Google Earth]] on how to install it for Mageia 8 (and Cauldron).
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28352}} - '''KiCAD''' fails to enable HW acceleration. ''And if you need 6.x branch, try [[flatpak|Flatpak]].''
 +
 
 +
{{Bug|28419}} ''(Fixed if using online media and if CUPS is running = online upgrade)'' - '''Boomaga''' virtual printer: The mga7 version remains installed after upgrading - along with the new mga8 package. '''Manual Fix:''' Uninstall the mga7 package. If it refuse to uninstall: as root {{cmd|rpm -e --noscripts boomaga-3.0.0-1.mga7}} '' '''If''' you find Boomaga printer have '''disappeared''' from your printer choices, again configure it in'' {{prog|Mageia Control Center}} {{menu|Hardware -> Set up the Printer...}}. ''Be aware that leaving both the mga7 and mga8 versions of the Boomaga packages installed will cause the same problem with any future Boomaga updates and Mageia upgrades.''
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28479}} - '''batik''' package conflicts from upgrading Mageia 7 to 8
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28481}} - '''npm''' has higher release on Mageia 7 than on Mageia 8 causing upgrade problems.
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28485}} - '''mythtv''' upgrade MGA7->MGA8 fails on file conflicts
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28503}} - '''php-json''' belongs to Mageia 7 and breaks PHP in Mageia 8 - php-json is now bundled = there is no extension anymore. '''Manual fix''' for them who already updated: Remove the lingering php-json package.
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28522}} - File conflicts with '''opencv-devel''' cause cascading errors during upgrade from Mageia 7 to 8
 +
 
 +
{{bug|28550}} - If UID is 500, the $PATH variable doesn't contain {{folder|/usr/games}}, thus '''games can't be launched'''. ''This affect systems originally installed with Mageia version 6 or earlier and upgraded since, or a manually set '''UID < 1000'''.'' This can not easily be fixed in a safe way for every case. See bug for ideas '''how to fix''' and ask on our forum if you need further help.
 +
 
 +
'''FIXED''' by Mageia 8 update {{bug|28636}} - '''python3-gdal'''-3.1.3-7.mga8 conflicts with file from package lib(64)gdal-devel-2.4.3-1.1.mga7
  
{{bug|28007}} - '''llvm'''-11.0 mga8 packages conflicts with mga7 llvm-devel packages when updating MGA7 to MGA8
+
'''FIXED''' by Mageia 8 update {{bug|28679}} - Upgrade from 7 to 8 (DNF/CLI) fails on package M8 '''CairoSVG''' conflict with M7 cairosvg
  
{{bug|28479}} - '''batik''' package conflicts from upgrading Mageia 7 to 8
+
{{bug|28724}} - '''mgaapplet upgrade''': asks where to first download all packages but dont respect neither '''download location''' nor "all first".
  
FIXED by Mageia 8 update {{bug|28481}} - '''npm''' has higher release on Mageia 7 than on Mageia 8 causing upgrade problems.
+
'''FIXED''' by Mageia 8 update {{bug|28743}} - '''LibreOffice''' help does not work.
  
{{bug|28485}} - '''mythtv:''' upgrade MGA7->MGA8 fails on file conflicts
+
'''FIXED''' by Mageia 8 update {{bug|28914}} - Some '''Gimp plugins''' are missing, which were in Mageia 7.
  
{{bug|28503}} - '''php-json''' belongs to Mageia 7 and breaks PHP in Mageia 8 - php-json is now bundled = there is no extension anymore. '''Fix:''' Remove the lingering php-json. ''Update is coming to do this automatically.''
 
  
 
==== Samba ====
 
==== Samba ====
  
{{bug|28042}} - While upgrading to MGA8: ERROR:'script' failed for samba-client-4.10.18-1.1mga7.x86_64
+
'''FIXED''' by Mageia '''7''' update {{bug|28042}} - While upgrading to MGA8: ERROR:'script' failed for '''samba-client'''-4.10.18-1.1mga7.x86_64. In most cases you can '''neglect''' that error message.

Latest revision as of 13:36, 16 December 2023


Drakconf multiflag.png
Other languages
Deutsch ; English  ; Español ; Français ; Português(Portugal)

Notes

This page is a companion to the Release Notes.

Old Errata version for Mageia 8 RC is here.

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.

Only 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 see may be fixed if you do a full update.

Also see Release Notes Known issues and Bug reporting sections.

Note that we will be updating issues from the bugtracker, i.e FOR_ERRATA8, IN_ERRATA8, FOR_RELEASENOTES8 as they are decided.

Boot

Also see Graphics.

mga#27117 - If rootfs is btrfs, and /boot is on rootfs, GRUB complains about ../../grub-core/commands/loadenv.c:216:sparse file not allowed. This is only cosmetic. Manual fix in Comment 3.

mga#32165 - Default boot selection: When you select in grub menu an option different to default (other OS or old kernel version by example), at next reboot that option has become the new default and will be booted if you don't select other. This behaviour is expected and has become a standard in Linux distributions, see the bug if you want to change it.

Live images

mga#28768 The draklive manual embedded on Live ISOs lacks one page, thus the menu entry "Updates" doesn't work. The full manual is available online.

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.

Non-working WiFi cards

Some WiFi hardware from Broadcom is known not to work, because they only work with Broadcom's proprietary driver, which we cannot have pre-built on the ISOs (because of licensing issues), and which needs be loaded at boot time. Once Mageia is installed you can configure the WiFi and reboot. Similarly, if persistence is enabled with the Live, you can configure the WiFi, and in following boots it will work.

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

Installer images

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 (New for Mageia 8)

NetInstaller

  • 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. mga#28225

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

How to change driver: see here.

mga#20835 - Avoid the Test button in MCC graphic setup! 1.) it may give false negative. 2.) it may hang your system. 3.) it may cause you to be unable to log in to desktop beacuse user's .Xauthority file got set to owned by root - Fix: (for 3.) Set user and group on ~/.Xauthority to your normal user. (Ask in forum if you need help.)

AMD/ATI

Described problems are most visible on Live media or system installed with Classic ISO without update repos enabled. Some updates have improved the situation, some resume fixes coming in kernel, and most importantly see the explanation and workaround below.

  • Boot problem with some Radeon HD GPU. Example: mga#28154
  • Resuming problem, despite booting OK. Example: mga#28863
  • Legacy VGA not working yet (upstream problem), so for instance if you have dual screen with one on VGA, the VGA connected one don't work. Example: mga#28817

Explanation: For AMD graphic cards based on Southern Islands family (Tahiti, Pitcairn, Oland, Verde, Hainan) and Sea Islands family (Kaveri, Bonaire, Hawaii, Kabini, Mullins) we are now defaulting to the newer amdgpu driver instead of the older less developing radeon. We appreciate feedback if it fails on your hardware, see mga# above.

Workaround for both cases above: use the older radeon driver (like Mageia 7 default) by adding the following on kernel command line:

For Southern Island cards: radeon.si_support=1 amdgpu.si_support=0

For Sea Islands cards: radeon.cik_support=1 amdgpu.cik_support=0

First use drakx11 (Mageia Control Center Section Hardware > Set up the graphical server item Graphic Card) to set driver to "ATI radeon HD 4870 and earlier" (at least for Bonaire cards).

In case booting to graphic desktop fail, use Ctrl+Alt+F2 (or reboot to maintenance mode) to open a console and launch drakx11 to select another driver, and reboot (type reboot.

Nvidia

Nvidia has neglected to fix security issues in their 340 series driver, so we had to drop it from official repos. See Release Notes.

mga#31994 - Virtual tty terminals are black (i.e Ctrl-Alt-F3), after booted to graphics mode (desktop). And shifting back and forth may hang the system. Workaround here. Note: This did not happen in release version of Mageia 8 but have been introduced by updates. Similar in other distributions.

Intel

mga#29587 - Random display lines get shifted right. Intel Coffee|TigerLake .... GT2 graphics

mga#30189 More than one screen on late Intel X5XX chipsets. Intel released new hardware but problems not yet fixed in their driver. Workaround is implemented in Mageia kernels 5.15.32 and up in normal updates, and 5.16.14 and up in backports. So if you are affected, boot with only one screen connected, and update your system.

LibreOffice window tiny

mga#30152. The extent of this problem is not known, but seem related to desktops using Qt, and using VGA port to monitor. LibreOffice windows may start tiny. See bug Comment 17. Workaround: drag the border of the window and resize to full size, at less twice for each LibreOffice affected application, one from the menu launcher and one opening a related file from the file manager.

Recording your desktop

mga#29405. Strange results when recording your desktop. The extent of this problem is not known. The workaround in Bug 30152 comment 7 solves the issue.

Desktops

mga#23929 - The folder Desktop in $HOME is not translated with Plasma or MATE only DE installation

mga#25877 - Netapplet/Mgaapplet/nm_applet with Cinammon or Xfce: When the applet is in a panel at the bottom of the screen, it's pop-up appears only as a black bar at the bottom of the screen. Workaround here.

mga#27601 - The boot hangs with a black screen and the mouse cursor still mobile. This is due to a change of hostname during SDDM start, set by avahi or networkmanager when the hostname is localhost. The workaround is to set the hostname to a personal value, for example with the command hostnamectl set-hostname myhost.local.

FIXED mga#28378 - SDDM greeter does not remember previous session. Manual fix if upgrade have been made before the fix: In /etc/sddm.conf in the line RememberLastSession=false change false to true.

Plasma

Wayland session with Nvidia's nvidia-current proprietary drivers is available by making sure that "nokmsboot" is removed and "nouveau.modeset=0" is passed to Kernel command line. Note mga#27296 - Plasma Wayland session broken, and mga#28365 - Control Center does not start in Plasma Wayland - Temporary fix: as normal user, first issue xhost +si:localuser:root

Wayland: Plasma panels: mga#30654: launchers at the top left corner of the screen don't work. Workaround: Add a spacer in the panel at left/top.

Compiz desktop effects is no longer compatible with Plasma. If you use it in Plasma on Mageia 7 then disable it in Mageia Control Center : Hardware -> Configure 3D Desktop effects - before upgrade, and if you don't want Compiz for another desktop environment, uninstall it. After install/upgrade of Mageia, you find desktop effects at System Settings (slider icon in main launch menu) Workspace -> Workspace Behavior -> Desktop Effects.

Dolphin right click extension kde-rootactions-servicemenu is removed as it is unmaintained upstream and have issues.

mga#27147 - Multi-users successive logins, plasmashell no longer runs log on to whatever user after going into sleep.

mga#27183 - Screenshot not launched by PrintScr key - Default Mageia spectacle integration settings missing in plasma5 systemsettings - On some occasions after upgrade. Manual fix: Launch Spectacle, press Configure -> Shortcuts. Select each entry under "Spectacle" and change the setting to "Default", and confirm in the popup asking to reassign. OK the main dialogue. If PrtScn key still does not make Spectacle show, then rename ~/.local/share/kglobalaccel/org.kde.spectacle.desktop (Maybe add "X" to the end). It may contain custom settings, you can delete it, see upstream bug.

FIXED by Mageia 8 updates: startplasma-x11 spawns zombie processes - mga#27362 (many packages), mga#28824 (qtbase), mga#28859 (systemd)

mga#28095 - Avatar Change not working on Classic Install Mageia 8 but does work on Live. Manual fix here.

mga#28287 - new plasma workspace does not allow unlocking of widgets when upgrading from older version. Plasma5 desktop and panel widgets cannot be locked/unlocked in Plasma version 5.18 onwards. This means that any such widgets locked before the upgrade cannot be unlocked after. So before upgrading, be sure to UNlock all such widgets. If you do find locked widgets after upgrading, this will unlock them: $ qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)"

mga#28299 - GTK apps complain (in log) about missing window_decorations.css. - Manual fix here.

mga#28342 - No shadows on GTK menus in GTK apps under Plasma. - When the theme "Breeze" is set in System Settings : Application Style -> Configure GNOME/GTK Application Style, there is no shadow in GTK right-click and GTK menus. Workaround: Set it to "Adwaita" (which is default).

mga#28623 - Alt+F2 fail to launch the Run command dialogue. - Manual fix: In System Settings : Shortcuts -> System Services -> KRunner *) , unfold section KRunner *), and under "Default Shortcuts" checkmark "Alt+F2". If it asks for confirmation, say yes. Apply, close System Settings and try if it works. If it does not, repeat the procedure. If still not, see bug. *) KRunner may be translated to something corresponding to "Run program".

mga#28827 - KDE Connect can not browse into devices. Explanation: If Mageia was installed using Classic Installer ISO without online repositories enabled, the suggested package sshfs-fuse will not be installed. Manual fix: Install sshfs-fuse.

GNOME

Network: By default, the NetworkManager service is enabled in place of the old network management services. You can 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. Network configuration via the MCC/drakconnect should also work in most cases.

Internationalisation: A default input method is not set in desktop session. You need to set it manually in Setting. mga#15793

GNOME and Wayland

By default, GNOME uses the Wayland display server. If Wayland fails to start, GNOME will automatically fall back to using the X.org display server - but in rare cases, this fails. If the GNOME desktop fails to launch, or if you experience display problems, you can try forcing GNOME to use the X.org display server by editing /etc/X11/gdm/custom.conf and set WaylandEnable=false.

For GNOME Live ISO there is a shortcut: add nowayland to the boot options in the initial boot menu (press e to edit the boot options). (But if you use persistence, use the method above.)

Xfce

mga#24134 - After login the display may show black and white bands or interesting effects for a couple of seconds.

mga#27795 - In Xfce, net_applet (internet connection icon) does not react to changes in connection status properly

LXQt

mga#28360 The compositor for transparency, generally used with Openbox, used to be compton. This one is deprecated and replaced by picom. If you upgrade from Mageia 7, the configuration file ~/.config/compton.conf can have some incompatible parameters which need to be edited. - Or simply delete that file. Unfortunately we have no Picom configuration tool yet.

Picom looks for configuration in the following order: ~/.config/picom.conf, ~/.config/compton.conf, /etc/xdg/picom.conf. That means a customized picom.conf can reside in ~/.config/ for a personal configuration or in /etc/xdg/ for a system wide configuration. So for customisation per user copy /etc/xdg/picom.conf to ~/.config/ and edit it there.

If you instead want to use compton-conf configuration similar to Mageia 7, install the compton-conf rpm and then copy /usr/share/compton-conf/compton.conf.example and edit it like below.

How to edit compton settings to picom compatible: Rename ~/.config/compton.conf to picom.conf, and in it disable the lines starting with: no_dnd_shadow, no_dock_shadow, clear shadow, menu_opacity, alpha_step, paint-on-overlay by prepending them with a #. Make the line starting with vsync read vsync = false; , and replace the whole line starting with glx-swap-method with use-damage = true; .

To start Picom: Mageia -> Accessories -> picom. To have Picom automatically start at login: LXQt configuration center -> LXQt settings -> Session Settings -> Autostart -> Add Name: Picom, Command: picom.

Some help, if needed: 1) Launch picom from a terminal and see the output, exit with Ctrl-C. 2) /etc/xdg/picom.conf have comments.

---

FIXED for new users: mga#28407 Default terminal in pcmanfm shall be qterminal, not xterm. Manual fix for existing users in already made upgrade or install: Use pcmanfm-qt preferences GUI. (Our general policy is to not force user preferences.)

Software

Firefox ESR

FIXED by an update mga#29064 - A packaging issue caused various problems with a few sites, solving i.e. mga#27374, mga#28359.

Note that still a few sites choose to not accept Firefox ESR (even upstream version), and demand non ESR version. You can help informing the problematic sites that Firefox ESR does not come with the latest features but it has the latest security and stability fixes.

As workaround you can try using an user agent switcher to spoof a non-ESR Firefox. Alternatively you can install the Firefox non-ESR version for example by using Flatpak or other Ways to install programs.

Flatpak

Plasma Discover and Gnome-software prefer Flatpak over Mageia RPM packages.

Backports problems

mga#29830 - drakrpm autoselects dependencies from a disabled repo. - This may install incompatible versions.

When you have backports repository configured (which is normal), Mageia graphical tools choose dependencies from it, even when it, as normal, is not enabled. A typical example is that PHP8.1 get installed as dependency for something needing PHP, but some such applications need PHP8.0.x, which should be installed from core updates repository. Workaround: use command line urpmi, or remove the backports repositories: Use command line urpmi.removemedia -y Backports or graphical tools: Start drakrpm-edit-media which is Mageia Control Center section Software Management -> Configure media sources for install and update, shift-click all backport media and click the button "Remove". FIX: If you already have gotten the too high versions, you can downgrade by disabling (or removing) backports repos, and issue urpmi --downgrade affected packages. For checking you can issue urpmq --not-available to list packages and versions that are not in enabled repos. (Possibly not all of them need be downgraded to fix your specific problem, and some may have been installed from other repos currently not configured or enabled, or other means.)

mga#30084 - mgaapplet does not list all updates available in Core Updates if Core Backports is enabled

Mageia Control Center

(Rare) Icons are invisible, but clickable in blind, after selecting a pane in left field:

mga#30332 - With updated webkit2 >=2.36, drakconf comes up with a blank window on both arches on real hardware and in VirtualBox guests for some graphics driver/settings.

Workaround: For 32-bit systems:, as root urpmi --downgrade libjavascriptcore-gir4.0-2.34.6-1.mga8 libjavascriptcoregtk4.0_18-2.34.6-1.mga8 libwebkit2gtk4.0_37-2.34.6-1.mga8 libwebkit2gtk-gir4.0-2.34.6-1.mga8 webkit2-2.34.6-1.mga8 webkit2-jsc-2.34.6-1.mga8 - Note: For 64 bit systems use "lib64" instead of "lib". Also as root, add two lines to /etc/urpmi/skip.list to avoid the packages getting updated:

/javascriptcore/
/webkit2/

Mageia Welcome

FIXED by Mageia 8 update (gives information) mga#28328 - Steam cannot be installed with the one-click button proposed with Mageia Welcome if 32bits repositories are not enabled, as it is the case by default. - 32 bit repositories should be enabled to complete the installation.

FIXED by Mageia 8 update mga#28806 - MageiaWelcome MCC tab display incorrectly for Chinese and Japanese.

Phone USB connection

Android, MTP: mga#28216. The libusb packages have been updated to include backported upstream fixes to improve Android phones USB connectivity. As you know there is a vast variety of Android devices. - Where there are still problems, try another method to connect, i.e over wifi using kdeconnect-kde (works for more than Plasma, and provide more than file transfer) or filesyncing serverless using i.e Syncthing or a cloud service. For more information visit our wiki page File transfer with Android devices.

iPhone: mga#28669 The packages ifuse and usbmuxd are missing by default. Manual fix: install them.

Virtualization software

To make virtualization software works, you need the machine virtualization support is enabled, but are usually disabled by default, we recommend read this link, could help you find how enable virtualization support on your machine.


Various software

mga#9683 - LibreOffice langpacks are not installed for Chinese and Portugese-Brazil. Manual fix: install them.

mga#28963 - LibreOffice package libreoffice-emailmerge and the task package libreoffice are not installed when installing from the classical ISO images. Manual fix: install libreoffice.

mga#22425 - Draksnapshot fail to launch.

mga#27340 - FreeCAD GUI fails to display. Manual fix: delete ~/.mozila/plugins/mozplugger0.so left over from a Mageia 7 to 8 upgrade.

mga#28097 - xviewer seg fault; also, not in application menus

FIXED by an update mga#28363 - VLC crashes when opening an MKV file when the video codec is AV1

mga#28683 - OGMRip fail to launch. Problem is also seen in other distros, and upstream seem stale.

mga#28791 // mga#31071 - qt-fsarchiver Even after the update 2023-06-15 it have quirks: need sudo, and asks an extra time for user password. fsarchiver do not handle the new ext4 version such as Mageia 9 and some other distros now use. Details, see bugs. Also see note on bug 31641 below.

mga#28814, mga#28840, mga#30462 Wine miss a few dependencies, especially for 32 bit libs. (Thus also PlayOnLinux.) Manual fix and also other tips here. Also see mga#16273

mga#30937 - Thunderbird leave temporary files behind if set to open pdf in external program. Upstream. Manual workaround is to change the setting, see linked bugs.

Mageia 8 cannot mount nor fsck an ext4 partition made with some recent distributions, including Mageia 9 up to including beta 2, after which this was reverted back for compatibility, see mga#31641 and the new ext4 feature C12.

External software

Not packaged by Mageia, only prominent external software is to be listed here.

mga#30103 - Video problems with Remote Desktop Tools (VNC, TeamViewer, AnyDesk, etc) Workaround: Firstly, at least TeamViewer and Anydesk are not Wayland compatible, so use Xorg. Problems can often be mitigated by on host computer selecting a lower resolution and/or switching off desktops effects (in for example Plasma: press Shift-Alt-F12), but better: in /etc/X11/xorg.conf, under devices, add Option "LinearFramebuffer".

Mageia tools

mga#15829 - Install and Remove Software (rpmdrake): starts in groups mode but view menu says "All packages, alphabetical" instead, if you need view packages in alphabetical order select other option and select again "All packages, alphabetical"

mga#24828, mga#29406 - Install and Remove Software (rpmdrake): search for applications with GUI+desktop file to install or remove produce an empty list if the package is provided by third party repositories. Workaround: change the filter "Packages with GUI" to "All"


Security

Boot of system with cyphered partitions

mga#19800 - 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 “rd.shell=0” to the kernel command line

Change in defaults of system-wide crypto-policies

During the development of Mageia 8, the upstream defaults of the system-wide cryptographic policies (which come with the package crypto-policies) have changed. Previously the default was LEGACY, which allowed TLS 1.0 and 1.1 protocols. The algorithms DSA, 3DES, and RC4 were allowed, while RSA keys and Diffie-Hellman parameters are accepted if they are at least 1023 bits long. The new setting of DEFAULT allow the TLS 1.2 and 1.3 protocols, as well as the IKEv2 and SSH2 protocols. RSA keys and Diffie-Hellman parameters are accepted if they are at least 2048 bits long.

The current setting can be seen in /etc/crypto-policies/config

It is not advised to change the default system-wide crypto-policies back to LEGACY, please instead report bugs for applications which are not working due to those new defaults.

For more details, please have a look at Red Hat Enterprise Linux 8 Security hardening - Using system-wide cryptographic policies

Miscellaneous

mga#31699#c28 urpmi --auto-orphans tries to remove too much. For now, simply don't use it, or see bug for tips if you really need.

Hibernation

mga#28528 - Resuming from hibernation instead start fresh. Upstream bug. Manual fix: 1) Verify that there is no line containing "add_dracutmodules" in output of cat /etc/dracut.conf.d/51-mageia-resume.conf . 2) Add the missing line by as root executing echo 'add_dracutmodules+=" resume "' >> /etc/dracut.conf.d/51-mageia-resume.conf and then generate new initrd: dracut -fv . After dracut finish, resume shall work. If not, you have other problem - please consult our forum.

Networking

Downloading software

For a few users, the default download method intermittently fails. Workaround: Start drakrpm-edit-media which is Mageia Control Center section Software Management -> Configure media sources for install and update. In Options -> Global options set "Download program to use" to "wget". mga#24362

Note: prior to wget 1.23 update in June (mga#30509), make sure to select mirrors using https, as our release version 1.21 of wget have problems with ftp.

If you already hit this (as described in mga#26827), failed downloads may result in messages like

There was a problem during the installation: package firefox-0:91.3.0-1.mga8.x86_64 does not verify: Payload SHA256 ALT digest: BAD (Expected 6ba98a0b474689bd5bbf15f361faf4116279e7c52d921ef5283db0e6f08d11c3 != 49b9a8f7b34a063e966a0133f5f84701d61ffd41ee3c595df575696a43c221bc)

If that happens, issue urpmi --clean, and try again (after changing to wget).

If that did not help, maybe the package on your mirror is broken, so remove your mirror set and add a new set, clean again, and try again:

To remove all repositories, either use command line urpmi.removemedia -a or graphical tools: Start drakrpm-edit-media which is Mageia Control Center section Software Management -> Configure media sources for install and update, shift-click all media, and click the button "Remove".

To add all Mageia repositories from a specific mirror, either use command line - example for 64 bit Mageia 8 Swedish mirror: urpmi.addmedia --distrib https://ftp.acc.umu.se/mirror/mageia/distrib/8/x86_64, or graphical tools: in the Configure media sources for install and update, Menu File -> Add a specific mirror.

Printing

mga#28746 - Printer is not discovered. For security reasons this functionality is by default not opened through the Firewall. To enable: Checkmark "CUPS server" and "Network printer/scanner autodiscovery" in Mageia Control Center Section Security > Set up your personal firewall.

Printing in gtk webkit applications

mga#28758 - Upstream bug in sandboxing may make printing from gtp applications such as Evolution not work. Workaround, upstream links and more info see bug first post.

Printer duplicate - not a bug

You may see your printer shown twice. That is because you are shown all available printers on both the local CUPS server (localhost) and all connected CUPS servers. So if you share a printer to the network, which is the default, it will be shown as two on the sharing computer. This behaviour is not specific to Mageia.

Workaround: Tell CUPS to not share the printer queue job on local network if you do not need to use it from another computer. See Mageia Control Center Section Hardware > Printing menu Server -> Settings.

Shell / Terminals

"bracketed paste" mode affecting copy&paste

By default readline 8.1 enabled the so-called "bracketed paste" mode, which in turn is effective for example in the bash shell. This means that if anything is pasted in your terminal, the pasted text will be enclosed by invisible escape characters \e[200~ and \e[201~
The visible effect is that this swaps the background and foreground highlighting colors for the pasted text, and one also needs to either press any key or click with the mouse to be able to execute the pasted text.
For more information about this, refer to bracketed paste mode.

This can be disabled for bash by adding bind 'set enable-bracketed-paste off' to ~/.bashrc and sourcing ~/.bashrc or by running a new bash shell.

Supposedly it should also be possible to disable this by adding set enable-bracketed-paste off to ~/.inputrc but this does not seem to have any effect.

Upgrade issues

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

Upgrade issues Tracker bug.

If upgrade failed

If you can not boot to a usable state, boot on Classical ISO and perform an upgrade. Remember to not format any partition. Important: you must enable any update repos that has been active during previous upgrade or previous release. Also note that Classic does not use nonfree drivers, you may need wired ethernet. If that can not be accomplished, try instead the Nonfree version of Network Installer ISO - it has more wifi support. For more details see Available installation media.

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

No upgrade offered by the applet

News: enabled 2021-04-04

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

As usual, we delay enabling this message in order to solve issues found by early installers and upgraders. So just wait, or upgrade per methods described in the Release Notes.

Upgrade using DNF

Extra kernel flavour installed - DNF uses a different method to select kernel flavour than Mageia installer. This may result in that a system that was using the desktop kernel, after upgrade have both desktop and server installed, and server used. Manual fix: select at boot the desktop kernel, then uninstall server kernel. mga#28272

PHP7 dropped

Mageia 8 have no PHP7. This may cause problem if you have software that is not compatible with PHP8.

Examples:

Workaround: You may be able to compile PHP7 yourself, see our forum.

Removed packages

Generally, see at end of Release Notes.

VirtualBox

There is no longer a VirtualBox 32 bit host.

Unused packages

After upgrade, you may find that there are a lot of unused packages installed. (Reported as orphans, or you can not directly see what they are installed for.)

Be careful - they may actually be needed:

The user may have third party software that requires the modules in those lib packages or requires old packages that are not lib packages. The third party software may be compiled from source, or manually copied binary files - not installed using rpm, so the package manager do not know. Also, if you alter between using DNF and urpmi, the orphan tracking does not work for either of them.

As long as the old packages do not interfere with new packages, we have chosen to let users choose which old packages they do not need and uninstall them manually if they wish to. (If you do, please keep a log of what you uninstall.)

You will also see that the updater have not only let old packages remain, but also installed corresponding upgrade Mageia versions of them - see it as a service.

Even on a new install, there will be multiple versions or alternatives of some packages installed as being suggested by different packages. These packages are not required, just suggested or recommended, so are orphans from the moment they are installed.

For more info see Removing packages.

Various upgrade issues

If you manually upgrade by graphical tools (i.e drakrpm, not urpmi or dnf) while having Mageia 8 backport repos enabled - even if not configured - you may get too high versions of packages, not compatible with some application. Fix and workaround see Backports problems above.

mga#29182 Upgrading under Wayland using the mgaonline applet / mgaapplet-upgrade-helper does not work. Workaround: Log out and log in using Xorg. Or use another upgrading method.

Optimus / Mageia Prime may need you to run mageia-prime-uninstall followed by mageia-prime-install. See this bug comment and our Mageia Prime wiki page.

FIXED by Mageia 8 update mga#27880 - x2go server

FIXED by Mageia 8 update mga#28007 - llvm-11.0 mga8 packages conflicts with mga7 llvm-devel packages when updating MGA7 to MGA8

mga#28018 - Google Earth Pro - See our wiki page Google Earth on how to install it for Mageia 8 (and Cauldron).

FIXED by Mageia 8 update mga#28352 - KiCAD fails to enable HW acceleration. And if you need 6.x branch, try Flatpak.

mga#28419 (Fixed if using online media and if CUPS is running = online upgrade) - Boomaga virtual printer: The mga7 version remains installed after upgrading - along with the new mga8 package. Manual Fix: Uninstall the mga7 package. If it refuse to uninstall: as root rpm -e --noscripts boomaga-3.0.0-1.mga7 If you find Boomaga printer have disappeared from your printer choices, again configure it in Mageia Control Center Hardware -> Set up the Printer.... Be aware that leaving both the mga7 and mga8 versions of the Boomaga packages installed will cause the same problem with any future Boomaga updates and Mageia upgrades.

FIXED by Mageia 8 update mga#28479 - batik package conflicts from upgrading Mageia 7 to 8

FIXED by Mageia 8 update mga#28481 - npm has higher release on Mageia 7 than on Mageia 8 causing upgrade problems.

FIXED by Mageia 8 update mga#28485 - mythtv upgrade MGA7->MGA8 fails on file conflicts

FIXED by Mageia 8 update mga#28503 - php-json belongs to Mageia 7 and breaks PHP in Mageia 8 - php-json is now bundled = there is no extension anymore. Manual fix for them who already updated: Remove the lingering php-json package.

FIXED by Mageia 8 update mga#28522 - File conflicts with opencv-devel cause cascading errors during upgrade from Mageia 7 to 8

mga#28550 - If UID is 500, the $PATH variable doesn't contain /usr/games, thus games can't be launched. This affect systems originally installed with Mageia version 6 or earlier and upgraded since, or a manually set UID < 1000. This can not easily be fixed in a safe way for every case. See bug for ideas how to fix and ask on our forum if you need further help.

FIXED by Mageia 8 update mga#28636 - python3-gdal-3.1.3-7.mga8 conflicts with file from package lib(64)gdal-devel-2.4.3-1.1.mga7

FIXED by Mageia 8 update mga#28679 - Upgrade from 7 to 8 (DNF/CLI) fails on package M8 CairoSVG conflict with M7 cairosvg

mga#28724 - mgaapplet upgrade: asks where to first download all packages but dont respect neither download location nor "all first".

FIXED by Mageia 8 update mga#28743 - LibreOffice help does not work.

FIXED by Mageia 8 update mga#28914 - Some Gimp plugins are missing, which were in Mageia 7.


Samba

FIXED by Mageia 7 update mga#28042 - While upgrading to MGA8: ERROR:'script' failed for samba-client-4.10.18-1.1mga7.x86_64. In most cases you can neglect that error message.