[solved] Can't login to GNOME since 46

leonardof · 2024-03-24 20:59:43

Since the update to 46 minutes ago, when I login to GNOME (X.org or Wayland) it sort of freezes on gdm after I enter my password and type Enter. I can still eg use the mouse to reboot, but the screen never leaves gdm for GNOME. Can't open tty2 but can switch to it if I have already opened it. Switching back from tty2 shows me the initial gdm state, as if I never had selected my user.

Looking at systemctl, there's a message from gdm-password saying gkr-pam was unable to locate daemon control file; dbus-broker-launch about ignoring duplicate name in GNOME Autenticator's search provider service (this are the bright red ones). Both before and after the attempted login, bluetoothd quits over and over again saying it failed to remove UUID: failed (0x03); and org.gnome.Shell.desktop warns (both before and after attempting to login?!) about the keyboard compiler warning about unsupported maximum keycode 700, X11 (?!) not being able to support after 255, and then listing keysims XF86CameraAccessEnable and similarly named ones as "could not resolve".

Tried without success advice given for a user whose system was throwing different error messages.

Can anyone point me what can I do to log in?

Edit: I'm getting around the problem by disabling gdm and starting a Wayland GNOME session directly:

$ XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

Last edited by leonardof (2024-03-25 22:40:42)

seth · 2024-03-24 21:40:46

Looking at systemctl, there's

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
https://bbs.archlinux.org/viewtopic.php … 6#p2159426
Otherwise please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

bus-broker-launch about ignoring duplicate name in GNOME Autenticator's search provider service (this are the bright red ones)

Probably irrelevant (see linked thread)

bluetoothd quits over and over again saying it failed to remove UUID: failed (0x03)

Most likely irrelevant.

and org.gnome.Shell.desktop warns (both before and after attempting to login?!) about the keyboard compiler warning about unsupported maximum keycode 700, X11 (?!) not being able to support after 255, and then listing keysims XF86CameraAccessEnable and similarly named ones as "could not resolve".

completely irrelevant, this reports legacy constraints since ~1 decade or so.

leonardof · 2024-03-24 22:50:55

seth wrote:

…
Otherwise please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
…

Thanks! Here it is

seth · 2024-03-24 23:14:20

mar 24 19:41:51 prata systemd-logind[419]: New session 1 of user gdm.
mar 24 19:41:51 prata (systemd)[519]: pam_unix(systemd-user:session): session opened for user gdm(uid=120) by gdm(uid=0)
mar 24 19:41:52 prata systemd[1]: Started Session 1 of User gdm.
mar 24 19:41:52 prata systemd[519]: Created slice User Core Session Slice.
mar 24 19:41:54 prata gnome-shell[554]: Will monitor session 1
mar 24 19:41:54 prata org.gnome.Shell.desktop[554]: Window manager warning: Failed to parse saved session file: Falha ao abrir arquivo “/var/lib/gdm/.config/mutter/sessions/1055e05a74d6c8c2be171132011248920100000005420000.ms”: Arquivo ou diretório inexistente
mar 24 19:41:55 prata systemd[519]: Started Multimedia Service Session Manager.
mar 24 19:41:55 prata kernel: Bluetooth: RFCOMM TTY layer initialized
mar 24 19:41:55 prata gnome-shell[554]: Registering session with GDM
mar 24 19:41:59 prata systemd[1]: Started Getty on tty2.
mar 24 19:41:59 prata agetty[1006]: failed to open credentials directory
mar 24 19:42:03 prata login[1006]: pam_unix(login:session): session opened for user leonardof(uid=1000) by leonardof(uid=0)
mar 24 19:42:03 prata systemd-logind[419]: New session 3 of user leonardof.
mar 24 19:42:03 prata (systemd)[1074]: pam_unix(systemd-user:session): session opened for user leonardof(uid=1000) by leonardof(uid=0)
mar 24 19:42:03 prata systemd[1]: Started Session 3 of User leonardof.
mar 24 19:42:03 prata login[1006]: LOGIN ON tty2 BY leonardof
mar 24 19:42:15 prata gdm-password][1173]: pam_unix(gdm-password:session): session opened for user leonardof(uid=1000) by leonardof(uid=0)
mar 24 19:42:15 prata systemd-logind[419]: New session 5 of user leonardof.
mar 24 19:42:15 prata systemd[1]: Started Session 5 of User leonardof.
mar 24 19:42:15 prata systemd[1074]: Created slice User Core Session Slice.
mar 24 19:42:28 prata sudo[1278]: leonardof : TTY=tty2 ; PWD=/home/leonardof ; USER=root ; COMMAND=/usr/bin/journalctl -b
mar 24 19:42:28 prata sudo[1278]: pam_unix(sudo:session): session opened for user root(uid=0) by leonardof(uid=1000)

GDM starts, you log in on TTY2, you try to log in w/ gdm.
If we condense the following "session" it looks like

mar 24 19:42:15 prata systemd-logind[419]: New session 5 of user leonardof.
mar 24 19:42:15 prata systemd[1]: Started Session 5 of User leonardof.
mar 24 19:42:15 prata systemd[1074]: Started GNOME Keyring daemon.
mar 24 19:42:15 prata gnome-keyring-daemon[1185]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
mar 24 19:42:15 prata systemd[1074]: Created slice User Core Session Slice.
mar 24 19:42:15 prata systemd[1074]: Starting D-Bus User Message Bus...
…
mar 24 19:42:15 prata systemd[1074]: Started D-Bus User Message Bus.
mar 24 19:42:15 prata dbus-broker-launch[1198]: Ready
mar 24 19:42:15 prata gdm-password][1173]: gkr-pam: unlocked login keyring
mar 24 19:42:15 prata gnome-shell[554]: Dropping signal SessionOpened of type (ss) since the type from the expected interface is (s)
mar 24 19:42:20 prata systemd-timesyncd[406]: Contacted time server [2804:2ea0::aaaa]:123 (2.arch.pool.ntp.org).
mar 24 19:42:20 prata systemd-timesyncd[406]: Initial clock synchronization to Sun 2024-03-24 19:42:20.475405 -03.
mar 24 19:42:25 prata systemd[1]: systemd-localed.service: Deactivated successfully.
mar 24 19:42:25 prata systemd[1]: systemd-hostnamed.service: Deactivated successfully.

And what sticks out there is

mar 24 19:42:15 prata gnome-shell[554]: Dropping signal SessionOpened of type (ss) since the type from the expected interface is (s)

There's https://www.mail-archive.com/debian-bug … 62026.html

pacman -Qs gdm # aur package etc?

leonardof · 2024-03-25 03:18:53

gdm 46.0.1 and libgdm-prime 3.34.1-1, none of them from AUR

seth · 2024-03-25 09:28:39

Errr… you mean https://aur.archlinux.org/packages/libgdm-prime which is entirely from the AUR and https://aur.archlinux.org/packages/libg … ent-963369 ?

davorh · 2024-03-25 09:32:08

I had the same issue, and replacing libgdm-plymouth (some old version) with libgdm 46.0-1 solved it. I guess its the same problem 'cos you mention some old libgdm-prime version.

leonardof · 2024-03-25 22:40:26

seth wrote:

Errr… you mean https://aur.archlinux.org/packages/libgdm-prime which is entirely from the AUR and https://aur.archlinux.org/packages/libg … ent-963369 ?

(facepalm and tears of joy emojis)

Yes, that was it1!

Before, when I tried to uninstall libgdm-prime, pacman told me libgdm depended on it. I thought it weird but thought it was from extra anyway! Of course, libgdm-prime was providing (or something) libgdm, and replacing libgdm-prime with libgdm made the login work again

Arch Linux

#1 2024-03-24 20:59:43

[solved] Can't login to GNOME since 46

#2 2024-03-24 21:40:46

Re: [solved] Can't login to GNOME since 46

#3 2024-03-24 22:50:55

Re: [solved] Can't login to GNOME since 46

#4 2024-03-24 23:14:20

Re: [solved] Can't login to GNOME since 46

#5 2024-03-25 03:18:53

Re: [solved] Can't login to GNOME since 46

#6 2024-03-25 09:28:39

Re: [solved] Can't login to GNOME since 46

#7 2024-03-25 09:32:08

Re: [solved] Can't login to GNOME since 46

#8 2024-03-25 22:40:26

Re: [solved] Can't login to GNOME since 46

Board footer