FS#69055 - [systemd] GDM no longer appears automatically after updating to systemd 247.2-1
Attached to Project:
Arch Linux
Opened by Doğukan Korkmaztürk (dogukan) - Monday, 21 December 2020, 15:23 GMT
Last edited by Toolybird (Toolybird) - Saturday, 15 April 2023, 22:28 GMT
Opened by Doğukan Korkmaztürk (dogukan) - Monday, 21 December 2020, 15:23 GMT
Last edited by Toolybird (Toolybird) - Saturday, 15 April 2023, 22:28 GMT
|
Details
Description:
After updating to systemd 247.2-1, GDM login screen no longer appears automatically even though gdm.service is enabled through systemctl. I think the service starts because a simple workaround of switching to another terminal using Ctrl+Alt+F2 and switching back to GDM using Ctrl+Alt+F1 makes the login screen appear. It is just not displayed automatically after booting the system. I have an AMD Vega 64 graphics card and I use mesa and amdgpu. My GDM configuration should be using Wayland. I have not tried it using X. It seems like there are other people having the same problem: https://www.reddit.com/r/archlinux/comments/kfmbhx/after_upgrading_to_systemd_24721_gnome_login/. I see these two lines when I run journalctl -p 3 -xb Dec 21 08:26:15 ArchDesk gnome-session-binary[607]: Unrecoverable failure in required component org.gnome.Shell.desktop Dec 21 08:26:28 ArchDesk gdm-password][1436]: gkr-pam: unable to locate daemon control file Additional info: * package version(s): systemd 247.2-1, gdm 3.38.2.1-1, mesa 20.3.1-1, linux 5.9.14.arch1-1 |
This task depends upon
Closed by Toolybird (Toolybird)
Saturday, 15 April 2023, 22:28 GMT
Reason for closing: None
Additional comments about closing: This is old and stale and doesn't seem to be a problem lately. Please refer to https://wiki.archlinux.org/title/GDM#Tro ubleshooting
Saturday, 15 April 2023, 22:28 GMT
Reason for closing: None
Additional comments about closing: This is old and stale and doesn't seem to be a problem lately. Please refer to https://wiki.archlinux.org/title/GDM#Tro ubleshooting
I am using the Nvidia proprietary drivers. I tried downgrading the drivers, but that had no effect.
It appears that the combination of systemd 247.2-1 and libseccomp 2.5.1-2 is the cause. Downgrading either of those packages seems to fix it.
I was able to reproduce with lightdm and gdm. It appears that Xorg is actually failing.
Log attached. Note that the log is taken from GamerOS (an Arch Linux derived distro), but I was also able to reproduce on an Arch Linux machine.
According to the log, Xorg is not finding the nvidia driver.
Strangely, the issue does not manifest until you reboot for the second time after installing the affected systemd and libseccomp packages.
Also, restarting lightdm or gdm manually from a tty works.
Fatal server error:
[ 3.724] (EE) no screens found(EE)
[ 3.724] (EE)
I have Arch installed on 4 different machines, and this issue appears on 3 of them. The issue appears on:
Desktop running AMD Ryzen 5 3600 with Vega VII GPU
Desktop running AMD Ryzen 7 1800x with 5700XT
Laptop running AMD 4800u with Vega 8 iGPU
This issue does NOT happen on this laptop:
Intel 5200u with iGPU + nVidia 940m running proprietary drivers with switchable graphics.
The workaround to switch TTY and back again mentioned in the original post also works on all 3 machines having the issue, but it's an annoying workaround that shouldn't be needed.
https://wiki.archlinux.org/index.php/LightDM#LightDM_does_not_appear_or_monitor_only_displays_TTY_output
Does it help for anyone here after trying following?
cp ~/.config/monitors.xml /var/lib/gdm/.config/
But now after rebooting again and an external monitor connected I get almost the same error again.
Now see an aditional message:
snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]
Output here: https://pastebin.com/CF4s1YHp
Basically it's stuck at `restart_syscall(<... resuming interrupted read ...>) = 1` till i switch back to the gdm tty
My hardware is a Dell XPS, kaby lake i7 with integrated Intel graphics.
Let me know if/how i can help and what sort of additional information can assist
edit: Update. I have both linux and linux-lts installed. This does NOT occur when booting the LTS kernel