From Mageia wiki
Jump to: navigation, search
(GNOME)
(Upgrade issues)
Line 47: Line 47:
 
Bug 28129  - nemo hangs at start from launcher or terminal. This can be resolved by installing the
 
Bug 28129  - nemo hangs at start from launcher or terminal. This can be resolved by installing the
 
updated nemo package either during installation, or after install.
 
updated nemo package either during installation, or after install.
 +
 +
=== Drakxtools ===
 +
 +
'''Bug 28280  - Drakxtools fail to launch in GUI mode after configuring network'''
 +
 +
As per https://bugs.mageia.org/show_bug.cgi?id=28280 mcc will fail to start in graphics mode
 +
if the hostname for the network is left at it's default of localhost.
 +
 +
The current workarounds are to either specify a hostname other then localhost during network setup,
 +
or by running (as root) the command "xhost +si:localuser:root" before starting mcc.
 +
 +
A proper fix will be decided on and implemented before the final iso images are produced.
  
 
== Upgrade issues ==
 
== Upgrade issues ==

Revision as of 23:37, 4 February 2021


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


Notes

This page is a companion to the Release Notes.

Note that we will be adding issues from the bugtracker, i.e beta1, beta2, rc1, rc2 as they are decided.

Boot

Live images

Installer images

32 bit installer must be on DVD to work as repository

After system install, the Classic Installer ISOs can be utilised as repository, to install software from without using internet.

The 64 bit ISO works for this both when placed on DVD and on a USB stick. The 32 bit ISO do not work as repository from USB.

Graphics

Nvidia

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

Desktops

GNOME

1) By default GNOME uses the Wayland display server. Wayland is still not fully mature, and may not work well on some hardware. Normally GNOME will automatically fall back to using the X.org display server if Wayland fails to start, but in some cases this fails to happen. If the GNOME desktop fails to launch after completing the initial language and locale selection, or if you experience display problems, you can try forcing GNOME to use the X.org display server by adding nowayland to the boot options in the initial boot menu (press e to edit the boot options).

2) 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.

CINNAMON

1) Installations from the Mageia-8-rc-i586.iso image without online repositories enabled will encounter Bug 28129 - nemo hangs at start from launcher or terminal. This can be resolved by installing the updated nemo package either during installation, or after install.

Drakxtools

Bug 28280 - Drakxtools fail to launch in GUI mode after configuring network

As per https://bugs.mageia.org/show_bug.cgi?id=28280 mcc will fail to start in graphics mode if the hostname for the network is left at it's default of localhost.

The current workarounds are to either specify a hostname other then localhost during network setup, or by running (as root) the command "xhost +si:localuser:root" before starting mcc.

A proper fix will be decided on and implemented before the final iso images are produced.

Upgrade issues

Upgrade using dnf

Kernel flavour

DNF use a different method to select kernel flavour than Mageia installer. This may result in that a system that was using 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. mga#28272