From Mageia wiki
Revision as of 17:00, 26 April 2015 by Tmb (talk | contribs) (Hardware Issues)
Jump to: navigation, search

This page is also available in other languages:

Classic Installer DVDs

Live CD/DVD

GNOME live isos

After install, booting into Gnome may fail right after giving a root password and a user name + user password. Rebooting again was seen to solve this. See comment 4 in bug 14489 which is really bug 13687

KDE live isos

Installer Issues

UEFI-installs

Because there were so many improvements at a late stage in Mageia 5 development, we have not been able to update our official installer manual. For instructions on how to perform an UEFI install, please read Installing_on_systems_with_UEFI_firmware which we keep up-to-date.


Upgrade Issues

If you have a non-efi system with Grub2, there is a chance that you won't be able to boot with the newest kernel after rebooting into your upgraded system, see bug 11827

However, booting an old kernel will still work.

Update: this should be fixed, but keeping it in the errata for now in case someone hits it again.

Software Issues

Internationalization

For KDE, XFce, and other desktop or window manager except GNOME, ibus-daemon is not started in desktop session. One workaround is to run "ibus-daemon -d -x &" or add it in ~/.bashrc. bug 15464

For GNOME, a default input method is not set in desktop session. You need to set it manually in Settings.

Spice vdagent (KVM/XEN)

for spice-vdagent to work, you will have to boot guests with kernel parameter "pci=nomsi" . if you don't, the spice guest socket will not be instantiated and thus spice-vdagent will not be able to connect to the host interface.

Enlightenment

Enlightenment has been updated to 0.18.8.

Mageia tools do not start under E18 due to missing polkit agent

Enlightenment does not start applications from /etc/xdg/autostart by default, which means that no polkit agent will be started. Since Mageia 4 all Mageia configuration tools have been ported to polkit

Users will need to enable a polkit agent either via the menu => settings => all => applications => autostart applications and enable a polkit agent. Or enable autostart via the command line:

 echo "/etc/xdg/autostart/polkit-mate-authentication-agent-1.desktop" >> ~/.e/e/applications/startup/.order

See bug 13029 for more details.

GTK

various gtk issues in installer, particularly noticable on drop down menus and summary screen

KDE

  • For KDE Frameworks 5 / Plasma 5 currently some dependencies are missing from the metapackages plasma-desktop / plasma-workspace This is currently being worked on via bug 13883 Also Plasma 5 conflicts with KDE 4 and cannot be installed in parallel. For more details check the blogpost of Nicolas Lecureil (Mageia KDE team)
    The following should give you enough packages to start a session via startkde
 urpme -a kde-l10n kdebase4-workspace
 urpmi plasma-desktop plasma-workspace oxygen kinit qttools5 qttools5-qtdbus dbus-x11 solid kded plasma5-libkscreen kconfig kio kservice kf5-krunner kf5-kfilemetadata plasma5-libkscreen kwin plasma-workspace-wallpapers xinit xauth xmessage socat
  • Using Onboard (on screen keyboard) Accessibility Package in KDE will cause the opening of KDE GUI tools as root to take up to 120 seconds. If you regularly use KDE GUI applications as root e.g. Dolphin, Kate, Kwrite etc. and wish to use Onboard then the delay may be removed by uninstalling the qtatspi-plugin package. This will disable one or two subtle features of Onboard which will probably go unnoticed. https://bugs.mageia.org/show_bug.cgi?id=11975

GNOME

Please notice that the current version of GNOME *requires* the composite extension of the X server to be enabled. If this is not the case, either from unsupported X drivers or if you have explicitely disabled "translucency" within the Mageia Control Center, the gnome session will fail at login time.

LXQt & RazorQt

LXQt is the successor of razorqt. It looks the same, although it adds quite a lot of desktop functionality. Most of the applications come from LXDE, but as QT version. razorqt has been obsoleted, and people will get LXQt after an upgrade to Mageia 5 if they had razor-qt before.


For cauldron users, manual removal and reinstallation of the lxmenu-data package might be necessary.
The versioning of the lxmenu-data package was corrected, and if you have version 0.7 or 0.8 installed, you would need to

 rpm -e --nodeps lxmenu-data; urpmi lxmenu-data

to receive the corrected lxmenu-data-0.1.4-1.mga5. This is not necessary when upgrading from Mageia 4.


More information on LXQt is available via User:Doktor5000#Replacing_Razor-qt_with_LXQt

LXDE

LXDE has seen quite some updates since Mageia 4 (add details here).

Mate

  • Due to Bluez5 incompability, Template:Pkg and Template:Pkg packages dropped and Mate Desktop does not provide bluetooth support for now. Mate developers suggest to use Blueman when it is fully migrated to Bluez5. Blueman with bluez5 support is at its alpha stage and many functions are not working. When a stable version released it will be provided via backports repository. As a workaround MATE users may use Template:Pkg to get bluetooth support.
  • There is an issue with panel drawer applet. When drawer applet added to panel and filled with other applets, it stretches along the screen and drawer icon may disappear. This is a long known issue by upstream and still being investigated. See Mate Github Issue 44 and Mate Github Issue 120 for further information.

dkms-iscsitarget

dkms-iscsitarget is deprecated in favour of targetcli

autofs

to configure the autofs "/net/hostname" feature you would have commented out the /net line in /etc/autofs/auto.master. however the current line /net -hosts is wrong.

to make it work replace the line with

/net /etc/autofs/auto.net

relates to a redhat bug https://bugzilla.redhat.com/show_bug.cgi?id=1038356

sddm

Bug 15357 sddm will show the US flag for the keyboard layout, but when typing the first letter it should switch to the correct one.

Grub2

  • Support in Drakboot
Grub2 is supported by drakboot (Mageia's boot configuration tool, used in installers and the Mageia control Center) but its configuration is only partial. For example editing of entries is offered but does not work. If you need more options, it is recommended to use one of the native grub2 methods described in /usr/share/doc/grub2/README.Mageia. (Bug 9627)
  • Kernel options
like some special graphic modes may need to be added manually in /etc/default/grub.
They may be added into this line:-
GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=792 nokmsboot resume....."
Note: After making changes to /etc/default/grub run update-grub (or update-grub2 which does the same) and enter the root password if asked.
  • Multi-booting
When 'installing' grub2 to a partition (for multi-booting) using drakboot or the installer, nothing is written to the partition boot sector as this is not recommended for reliability reasons related to the use of block lists. These are prone to overwriting by some file system utilities, and not even possible on some file systems. Instead a copy of the grub2 kernel is written as /boot/grub2/i386-pc/core.img and this may be booted from either grub legacy or grub2 used in a dedicated master bootloader or from another system.

A suitable entry in a grub legacy menu.lst for booting Mageia using grub2 installed to sda7 would be:

title Mageia 5 on sda7
root (hd0,6)
kernel /boot/grub2/i386-PC/core.img

An entry in a manually created /boot/grub2/grub.cfg (for a dedicated master bootloader) or when adding to an automatically generated menu using /boot/grub2/custom.cfg the entry would be:

menuentry 'Mageia 5 on sda7' {
root=(hd0,msdos7)
multiboot /boot/grub2/i386-pc/core.img
}

If /boot is on a separate partition (e.g. needed when btrfs is used for root) then a suitable entry (where /boot is on sda6) would be as below. Note also the changed multiboot path:

menuentry 'Mageia-5 (btrfs root)' {
root=(hd0,msdos6)
multiboot /grub2/i386-pc/core.img
}

A major advantage of grub2 over grub legacy is the ability to use partition labels without knowledge of unreliable device assignments. If the Mageia root partition is labelled 'mageia-4' (assuming /boot is not on a separate partition) then this may be used:

menuentry 'Mageia 5' {
search --no-floppy --label --set=root mageia-5
multiboot /boot/grub2/i386-pc/core.img
}

Note that since the partition boot record is not used by grub2, it may be used by grub legacy while both are installed together, allowing for chainloading into grub legacy and multibooting into grub2 from two separate master menu entries.

  • Minimal installs

When a minimal install of grub2 is needed it may be installed with urpmi grub2 --no-recommends which will omit os-prober and the grub2-mageia-theme, giving a classical grub2 text only menu with no other systems listed. os-prober may be installed later as may a grub2 theme package - just install or un-install these at will and the effect will be seen at the next boot.

  • KDE Leave menu

To use the KDE options on the Leave > Reboot sub-menu (accessed by clicking on the yellow icon - not the text) with grub2, it is necessary to change /etc/default/grub to include:

GRUB_DEFAULT=saved

Run update-grub after editing /etc/default/grub

Also systemsettings > System Administration > Login Screen > Shutdown tab > Boot Manager needs grub2 to be selected.


Roundcubemail

The new php-5.6 doesn't let Roundcubemail find the certificates and as a result the verification of the user at log-in fails. To resolve this problem, you need to edit file /etc/php.ini and ad this line in section [openssl]

openssl.cafile=/etc/pki/tls/certs/cyrus-imapd.pem

Hardware Issues

Proprietary drivers are known to be problematic with new Xorg

Example: fglrx for AMD/ATI Radeon. Workaround is to use xorg ati or vesa driver.