[resolved] Failed to start Display Manager

[Bequimao]

Hi,

this morning, my Cauldron installation failed to boot into the login screen. There were several error messages ( Excerpt form # journalctl -p err)

Code: Select all

-- Reboot --
May 19 10:00:14 localhost.localdomain systemd[1]: Failed to start Show Plymouth Boot Screen.
May 19 10:00:18 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-primary.device: Dev dev-disk-by\x2dpartlabel-primary.device appeared twice with different sysfs path
May 19 10:00:19 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:00:19 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:00:19 localhost.localdomain systemd-backlight[870]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
May 19 10:00:19 localhost.localdomain systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
May 19 10:01:14 localhost.localdomain kernel: Bluetooth: Patch file not found ar3k/AthrBT_0x01020200.dfu
May 19 10:01:14 localhost.localdomain kernel: Bluetooth: Loading patch file failed
May 19 10:01:28 localhost.localdomain systemd[1]: Failed to start Show Plymouth Boot Screen.
May 19 10:01:33 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-primary.device: Dev dev-disk-by\x2dpartlabel-primary.device appeared twice with different sysfs path
May 19 10:01:34 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:34 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-primary.device: Dev dev-disk-by\x2dpartlabel-primary.device appeared twice with different sysfs path
May 19 10:01:34 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:34 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:34 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:35 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:35 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:37 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:37 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-primary.device: Dev dev-disk-by\x2dpartlabel-primary.device appeared twice with different sysfs path
May 19 10:01:37 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:37 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:38 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:38 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-primary.device: Dev dev-disk-by\x2dpartlabel-primary.device appeared twice with different sysfs path
May 19 10:01:39 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:01:39 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-primary.device: Dev dev-disk-by\x2dpartlabel-primary.device appeared twice with different sysfs path
May 19 10:01:40 localhost.localdomain systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partiti
May 19 10:02:10 localhost.localdomain systemd[1]: Failed to start Irda Support.
May 19 10:02:14 localhost.localdomain systemd[1]: Failed to start Display Manager.
May 19 10:02:38 localhost.localdomain systemd[1]: Failed to start Network Manager Wait Online.
May 19 10:02:38 localhost.localdomain systemd[1]: Failed to start Irda Support.
May 19 10:03:03 localhost.localdomain systemd[1]: Failed to start Network Manager Wait Online.
May 19 10:03:20 localhost.localdomain /etc/sysconfig/network-scripts/ifup-eth[3511]: Device eth0 does not seem to be present, delaying initialization.
May 19 10:03:20 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.
May 19 10:03:33 localhost.localdomain kernel: xt_addrtype: ipv6 does not support BROADCAST matching
May 19 10:09:14 localhost.localdomain systemd[1]: Failed to start Show Plymouth Power Off Screen.
May 19 10:09:15 localhost.localdomain systemd[1]: Failed unmounting /var/log.
-- Reboot --


The culprit should be one of these updates

Code: Select all

restarting urpmi
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch   
(medium "Core Release")
  curl                           7.49.0       1.mga6        x86_64 
  imagemagick                    6.9.4.2      1.mga6        x86_64 
  lftp                           4.7.2        1.mga6        x86_64 
  lib64curl4                     7.49.0       1.mga6        x86_64 
  lib64expat1                    2.1.1        2.mga6        x86_64 
  lib64lftp0                     4.7.2        1.mga6        x86_64 
  lib64magick-6Q16_2             6.9.4.2      1.mga6        x86_64 
  lib64ndp0                      1.6          1.mga6        x86_64 
  lib64rpmbuild7                 4.13.0       0.rc1.33.mga6 x86_64 
  lib64taglib1                   1.11         1.mga6        x86_64 
  lib64wayland-client0           1.10.91      1.mga6        x86_64 
  lib64wayland-cursor0           1.10.91      1.mga6        x86_64 
  lib64wayland-server0           1.10.91      1.mga6        x86_64 
  lib64xfont1                    1.5.1        4.mga6        x86_64 
  lib64xml2_2                    2.9.3        3.mga6        x86_64 
  libxml2-python                 2.9.3        3.mga6        x86_64 
  libxml2-utils                  2.9.3        3.mga6        x86_64 
  openvpn                        2.3.11       1.mga6        x86_64 
  rpm-mageia-setup               2.20         3.mga6        x86_64 
  wpa_supplicant                 2.5          4.mga6        x86_64 
78KB of disk space will be freed.
5.6MB of packages will be retrieved.
Proceed with the installation of the 20 packages? (Y/n) n
[root@localhost ~]#


The hardware is a Sony Vaio E Series SVE1713G4EW notebook with AMD/ATI graphics.

Code: Select all

# lspci -nnk | grep -iA3 vga
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841]
        Subsystem: Sony Corporation Device [104d:90ac]
        Kernel driver in use: radeon
        Kernel modules: radeon


The system is installed on a btrfs filesystem, and I was able to reset to an earlier snapshot. The error logs are still there, because they are located in a different subvolume, which is excluded from snapshotting.

Best regards,
Bequimão

[doktor5000]

What does/did /var/log/Xorg.0.log or /var/log/Xorg.9.log say, and what about the

Code: Select all

journalctl -ab-1 -u dm_name

log entries?
Hint: You would need to replace dm_name with the systemd unit name of the display manager you're using, e.g. gdm, or prefdm or sddm etc ...

[Bequimao]

Hi Doc,

The issue was dealt in today's QA session. The fix is already there, it is the package lib64xfont1-1.5.1-5.mga6. I have already tested the update. Works fine!

It is very nice to have btrfs snapshots at hand at such issues.

Thanks,
Bequimão

[Bequimao]

I use Plasma 5 with display manager sddm. Please not that there is no systemd unit sddm.
To retrieve the messages use

Code: Select all

journalctl -b --no-pager | grep sddm | less


Bequimão

[doktor5000]

Please not that there is no systemd unit sddm.

Yes, there is the standard systemd unit for sddm as provided by upstream: /usr/lib/systemd/system/sddm.service