You are not logged in.
I have installed GNOME and enabled gdm.service as described on the wiki.
GDM always works when I start it using 'sudo systemctl start gdm.service' after booting. However, if gdm.service is enabled, then it previously caused the boot to hang before getting to a graphical login screen. According to https://bugs.archlinux.org/task/59262, the solution is to downgrade systemd, systemd-sysvcompat, and libsystemd to 238.133-4. After I did this, I can boot to a login screen, but when I log in the system hangs again. It just stays forever on the gray screen that you normally see right after login.
The information in journalctl is not helpful:
$ journalctl -e -u gdm
-- Reboot --
Aug 02 13:39:30 shallan systemd[1]: Starting GNOME Display Manager...
Aug 02 13:39:30 shallan systemd[1]: Started GNOME Display Manager.
Aug 02 13:39:30 shallan gdm[433]: Child process -478 was already dead.
Aug 02 13:39:30 shallan gdm[433]: Child process 464 was already dead.
Aug 02 13:39:30 shallan gdm[433]: Unable to kill session worker process
Aug 02 13:39:30 shallan gdm[433]: Child process -493 was already dead.
Aug 02 13:39:30 shallan gdm[433]: Child process 482 was already dead.
Aug 02 13:39:30 shallan gdm[433]: Unable to kill session worker process
... more of this ...
Aug 02 13:39:31 shallan gdm[433]: Child process -644 was already dead.
Aug 02 13:39:31 shallan gdm[433]: Child process 634 was already dead.
Aug 02 13:39:31 shallan gdm[433]: Unable to kill session worker process
Aug 02 13:40:08 shallan gdm-password][928]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=raxod502
Aug 02 13:40:15 shallan gdm-password][933]: pam_unix(gdm-password:session): session opened for user raxod502 by (uid=0)I have disabled Wayland in /etc/gdm/custom.conf, because Wayland doesn't support xmodmap. Otherwise, I haven't changed GDM configuration.
I am using a Dell XPS 15 9570.
How can this be debugged?
Last edited by raxod502 (2018-08-04 21:35:57)
Offline
What lead you to conclude it was https://bugs.archlinux.org/task/59262 ? With wayland disabled in /etc/gdm/custom.conf 59262 should not be triggered.
Does the coredump match 59262?
Offline
What led me to that conclusion was that downgrading systemd fixed the problem immediately.
However, I upgraded systemd again and now it gets to the login screen without hanging at the console. I suspect that the hang may occur nondeterministically.
Offline
The problem was resolved by following the instructions in https://cnly.github.io/2017/08/25/fix-s … -9560.html.
If you don't know how to "add to grub command line", see https://askubuntu.com/a/952939/585408.
Offline