Unable to log in using GDM after Jan. 4 2026 update

heistp · 6 January 2026 11:19

After the update on Jan. 4, 2026, I’m unable to log in using GDM. I enter the credentials and the mouse pointer freezes. I see the log below in journalctl when logging in. I am able to work around it by using lightdm.service instead of gdm.service, suggesting a problem related to GDM. I am using Gnome, with the amdgpu video driver and Wayland, on a Ryzen 5 4500U (HP Probook 455 G7).

Any ideas?

Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmManager: trying to open reauthentication channel for user admin
Jan 06 12:03:39 localhost gdm[46783]: Gdm: Finding a graphical session for user 60578
Jan 06 12:03:39 localhost gdm[46783]: Gdm: Considering session '12'
Jan 06 12:03:39 localhost gdm[46783]: Gdm: Session '12' is not a graphical session (type: 'unspecified')
Jan 06 12:03:39 localhost gdm[46783]: Gdm: Considering session '11'
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmManager: looking for login screen session for user admin
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmManager: no matching sessions found
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: starting conversation gdm-password for session (0x55dd5a7592c0)
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSessionWorkerJob: Starting worker...
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSessionWorkerJob: Running session_worker_job process: gdm-session-worker [pam/gdm-password] /usr/lib/gdm-session-worker
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSessionWorkerJob: : SessionWorkerJob on pid 48665
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: Enabling debugging
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: connecting to address: unix:path=/run/gdm/dbus/dbus-h8Cx0R27
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmDBusServer: new connection 0x7f5c18001820
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: Handling new connection from worker
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: Authenticating new connection
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: worker connection is 0x7f5c18001820
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: Emitting conversation-started signal
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmManager: session conversation started for service gdm-password on session
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmManager: ignoring session conversation since its not automatic login conversation
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: checking if file 'gnome.desktop' is wayland session: yes
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: setting session to type 'wayland'
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: Set up service gdm-password for username admin on session (0x55dd5a7592c0)
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: selecting user 'admin' for session '(null)' (0x55dd5a7592c0)
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: Beginning initialization
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: checking if file 'gnome.desktop' is wayland session: yes
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:39 localhost gdm[46783]: Gdm: GdmSession: Conversation started
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: trying to track new user with username admin
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: finding user 'admin' state 1
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: waiting for user manager to load before finding user 'admin'
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: Finding a graphical session for user 0
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: Failed to identify the current session
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: seat unloaded, so trying to set loaded property
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: Seat wouldn't load, so giving up on it and setting loaded property
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: user manager now loaded, proceeding with fetch user request for user 'admin'
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: finding user 'admin' state 2
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: Looking for user 'admin' in accounts service
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: already loaded, so not setting loaded property
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: Found object path of user 'admin': /org/freedesktop/Accounts/User1000
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: finding user 'admin' state 3
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: user 'admin' fetched
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: user admin is now loaded
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: user admin was not yet known, adding it
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: tracking user 'admin'
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: not yet loaded, so not emitting user-added signal
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: no pending users, trying to set loaded property
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: already loaded, so not setting loaded property
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionSettings: saved session is  (type )
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionSettings: saved language is
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: queuing setup for user: admin (null)
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: finished handling request for user 'admin'
Jan 06 12:03:39 localhost gdm-password][48665]: accountsservice: ActUserManager: unrefing manager owned by fetch user request
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: attempting to change state to SETUP_COMPLETE
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: initializing PAM; service=gdm-password username=admin seat=seat0
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'XDG_SEAT=seat0'
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: state SETUP_COMPLETE
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: attempting to change state to AUTHENTICATED
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: authenticating user admin
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: 1 new messages received from PAM
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: username is 'admin'
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: old-username='admin' new-username='admin'
Jan 06 12:03:39 localhost gdm-password][48665]: Gdm: GdmSessionWorker: received pam message of type 1 with payload 'Password: '
Jan 06 12:03:41 localhost systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jan 06 12:03:42 localhost systemd[1]: systemd-localed.service: Deactivated successfully.
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: trying to get updated username
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: PAM conversation returning 0: Success
Jan 06 12:03:43 localhost gdm-password][48665]: gkr-pam: unable to locate daemon control file
Jan 06 12:03:43 localhost gdm-password][48665]: gkr-pam: stashed password to try later in open session
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: state AUTHENTICATED
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: trying to get updated username
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: username is 'admin'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: old-username='admin' new-username='admin'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: attempting to change state to AUTHORIZED
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: determining if authenticated user (password required:0) is authorized to session
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: state AUTHORIZED
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: attempting to change state to ACCREDITED
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LOGNAME=admin'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'USER=admin'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'USERNAME=admin'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'HOME=/home/admin'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'PWD=/home/admin'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'SHELL=/usr/bin/bash'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'PATH=/usr/local/bin:/usr/local/sbin:/usr/bin'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: state ACCREDITED
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: type wayland, program? no, seat seat0
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: session display mode set to new-vt
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_TYPE=wayland'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: attempting to change state to ACCOUNT_DETAILS_SAVED
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: saving account details for user admin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: attempting to change state to SESSION_OPENED
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'XDG_VTNR=3'
Jan 06 12:03:43 localhost gdm-password][48665]: pam_unix(gdm-password:session): session opened for user admin(uid=1000) by admin(uid=0)
Jan 06 12:03:43 localhost systemd-logind[838]: New session '13' of user 'admin' with class 'user' and type 'wayland'.
Jan 06 12:03:43 localhost systemd[1]: Started Session 13 of User admin.
Jan 06 12:03:43 localhost systemd[11525]: Started GNOME Keyring daemon.
Jan 06 12:03:43 localhost gnome-keyring-daemon[48773]: gnome-keyring-daemon: no process capabilities, insecure memory might get used
Jan 06 12:03:43 localhost gnome-keyring-daemon[48773]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 06 12:03:43 localhost systemd[11525]: Starting D-Bus User Message Bus...
Jan 06 12:03:43 localhost dbus-broker-launch[48778]: Service file '/usr/share/dbus-1/services/org.jackaudio.service' is not named after the D-Bus name 'org.jackaudio.service'.
Jan 06 12:03:43 localhost systemd[11525]: Started D-Bus User Message Bus.
Jan 06 12:03:43 localhost dbus-broker-launch[48778]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jan 06 12:03:43 localhost dbus-broker-launch[48778]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jan 06 12:03:43 localhost dbus-broker-launch[48778]: Ready
Jan 06 12:03:43 localhost gdm-password][48665]: gkr-pam: unlocked login keyring
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: state SESSION_OPENED
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Emitting 'session-opened' signal
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmManager: Will start session when ready
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmManager: start or jump to session
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Ignoring session (null) as requested
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmManager: no matching sessions found
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmManager: migrated: 0
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: type wayland, program? no, seat seat0
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmManager: session has its display server, reusing our server for another login screen
Jan 06 12:03:43 localhost gdm[46783]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
Jan 06 12:03:43 localhost gdm[46783]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
Jan 06 12:03:43 localhost gdm[46783]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
Jan 06 12:03:43 localhost gdm[46783]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
Jan 06 12:03:43 localhost gdm[46783]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
Jan 06 12:03:43 localhost gdm[46783]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
Jan 06 12:03:43 localhost gdm[46783]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Creating D-Bus server for worker for session
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: D-Bus server for workers listening on unix:path=/run/gdm/dbus/dbus-rkMf4Rdt
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Creating D-Bus server for greeters and such for session (null) (0x55dd5a77c0f0)
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: D-Bus server for greeters listening on unix:path=/run/gdm/dbus/dbus-hjv9ftrh
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Setting display device: (null)
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Created user session for user 60578 on display /org/gnome/DisplayManager/Displays/94409193747808 (seat seat0)
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: id: (null)
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: seat id: (null)
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: session class: greeter
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: initial: no
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: allow timed login: yes
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: local: yes
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: supported session types: (null)
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: session class: user
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: seat id: seat0
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: session id: 13
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplayStore: Adding display /org/gnome/DisplayManager/Displays/94409193937968 to store
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Stopping all conversations except for gdm-password
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: type wayland, program? no, seat seat0
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: 'gnome.desktop' registers self
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: checking if file 'gnome.desktop' is wayland session: yes
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Session (null) bypasses Xsession wrapper script
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: getting desktop names for file 'gnome.desktop'
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: type wayland, program? no, seat seat0
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LC_PAPER=en_US.UTF-8'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LC_TIME=en_US.UTF-8'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LC_MEASUREMENT=en_US.UTF-8'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LC_MONETARY=en_US.UTF-8'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LC_MESSAGES=en_US.UTF-8'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_DESKTOP=gnome'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'DESKTOP_SESSION=gnome'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'XDG_CURRENT_DESKTOP=GNOME'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LC_ADDRESS=en_US.UTF-8'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LANG=en_US.UTF-8'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'GDM_LANG=en_US.UTF-8'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: Set PAM environment variable: 'GDMSESSION=gnome'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: start program: /usr/lib/gdm-wayland-session "/usr/bin/gnome-session"
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: attempting to change state to SESSION_STARTED
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: opening user session with program '/usr/lib/gdm-wayland-session'
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: jumping to VT 3
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: first setting graphics mode to prevent flicker
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: VT mode did not need to be fixed
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: received VT change event
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: VT changed from 1 to 3
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: VT of login window is 1
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Trying script /etc/gdm/PostLogin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: script /etc/gdm/PostLogin not found; skipping
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Trying script /etc/gdm/PostLogin/Default
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Running process: /etc/gdm/PostLogin/Default
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: VT switched from login window
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: killing login window once its unused
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: display status changed: 3
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: active VT is not initial VT, so ignoring
Jan 06 12:03:43 localhost kernel: rfkill: input handler enabled
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: PATH=/usr/local/bin:/usr/local/sbin:/usr/bin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: LOGNAME=admin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: USER=admin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: USERNAME=admin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: PWD=/home/admin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: SHELL=/usr/bin/bash
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: RUNNING_UNDER_GDM=true
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: GROUP=admin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Gdm: script environment: HOME=/home/admin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Process exit status: 1
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: uninitializing PAM
Jan 06 12:03:43 localhost gdm-password][48665]: pam_unix(gdm-password:session): session closed for user admin
Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: GdmSessionWorker: state NONE
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: stopping conversation gdm-password
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSessionWorkerJob: Stopping job pid:48665
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmCommon: sending signal 15 to process 48665
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Emitting 'session-start-failed' signal
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmManager: session failed to start: GDBus.Error:org.gnome.DisplayManager.SessionWorker.Error.OpeningSession: Failed to execute PostLogin script
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplay: Session never registered, failing
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: display status changed: 5
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: display for seat seat0 requested
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: display status changed: 2
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmLocalDisplayFactory: session 11 found, activating.
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Closing session
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Stopping all conversations
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSessionWorkerJob: Stopping job pid:48665
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmCommon: sending signal 15 to process 48665
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSessionWorkerJob: Waiting on process 48665
Jan 06 12:03:43 localhost systemd[1]: session-13.scope: Deactivated successfully.
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmCommon: process (pid:48665) done (status:0)
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSessionWorkerJob: SessionWorkerJob died
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Disposing session
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Closing session
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmSession: Stopping all conversations
Jan 06 12:03:43 localhost gdm[46783]: Gdm: GdmDisplayStore: Unreffing display: 0x55dd5a77dc30
Jan 06 12:03:43 localhost systemd-logind[838]: Removed session 13.

linux-aarhus · 6 January 2026 12:39

Do you use gnome-remote-desktop to connect to the system remotely ?

Do you have a user named admin ?

The user with UID 60578 is a dynamic user

heistp · 6 January 2026 15:41

No, I do not use gnome-remote-desktop. It’s a local login.

I have changed the original username in the logs to admin so as to keep it private, but the username that’s actually in the logs exists.

The UID 60578 does not match the username in the logs. If that number is for a dynamic user, I can’t explain that.

I’ve made no changes to the system that I’m aware of prior to installing the Jan. 4 update, and I was able to log in before, so something has changed. Why I can still log in with LightDM, I also do not know…

linux-aarhus · 6 January 2026 16:01

I would point to an issue with gdm. I asked about gnome-remote-desktop because I have been researching how to do this with Plasma Wayland.

During that research I came across how gnome provides a shared rdp user which gives remote access to gdm, and enable a system user to sign in.

That is where the UID came in as I could verify that it is a viable UID for a dynamic greeter user. The userdbctl utility will give you some basic info.

userdbctl

heistp · 7 January 2026 08:42

This line in the log looks suspicious:

Jan 06 12:03:43 localhost gdm-password][48665]: Gdm: Process exit status: 1

It’s after that time that the login process seems to unwind. Unfortunately, it doesn’t say what process exits with status 1, and this is already the output from GDM with debugging enabled (Enable=true under the debug section in /etc/gdm/custom.conf).

I could work on configuring auditd to try to figure out which process this is, but this would take time, which is in short supply at the moment.

Yes, userdbctl also shows for me that 48665 is the first dynamic greeter user, so thanks, that explains that…

heistp · 8 January 2026 09:46

I also noticed that I’m now unable to update packages:

$ sudo pacman -Syu
:: Synchronizing package databases…
error: restricting filesystem access failed because Landlock is not supported by the kernel!
error: switching to sandbox user ‘alpm’ failed!
error: failed to synchronize all databases (failed to retrieve some files)

I’m just using the regular linux612 package for the 6.12 kernel, and according to /proc/config.gz, CONFIG_SECURITY_LANDLOCK=y, so I don’t understand why it’s saying that Landlock isn’t supported by the kernel.

But, based on this post, I uncommented two lines in pacman.conf, DisableSandboxFilesystem and DisableSandboxSyscalls, and that fixed the pacman problem, but it doesn’t feel correct to be running with a non-standard config edit like this so that updates work.

Thinking that maybe Landlock is also affecting GDM, I instead tried running with lsm=landlock,lockdown,yama,integrity,apparmor,bpf added to the kernel command line, but that neither fixed GDM nor allowed pacman to work without the DisableSandbox settings.

I also see this log entry some time after boot:
[ 68.974607] landlock: Disabled but requested by user space. You should enable Landlock at boot time: Landlock: unprivileged access control — The Linux Kernel documentation

But, I see that CONFIG_LSM=“landlock,lockdown,yama,integrity,bpf” in /proc/config.gz, so Landlock should be loaded at boot time.

Is Landlock somehow related to what I’m seeing with GDM? I’m not sure yet…

linux-aarhus · 8 January 2026 11:34

I am sure it is - but it is not enabled - this must be done using kernel argument.

Edit the file /etc/default/grub and add to the cmdline

GRUB_CMDLINE_LINUX_DEFAULT=".. lsm=landlock,lockdown,yama,integrity,apparmor,bpf .."

Then rebuild grub configuration

update-grub

I don’t know - I wish I did.

heistp · 8 January 2026 12:16

Right, my mistake, I’m using systemd-boot, not grub. It’s been a long time since I’ve looked at this config. So, I changed /etc/kernel/cmdline to include the parameter lsm=landlock,lockdown,yama,integrity,apparmor,bpf (the trick to getting the kernel to update was to remove and reinstall the kernel with mhwd-kernel -r and mhwd-kernel -i, which could probably also be done from Manjaro Settings). Note that I have edits to /etc/kernel/cmdline for a needed LUKS parameter, among other things.

That fixes pacman, but does not fix the login issue with GDM. So, it’s useful, but unrelated…

heistp · 9 January 2026 10:45

Ok, I found the problem. The file /etc/gdm/PostLogin/Default contained the following:

#!/bin/sh
#Manjaro tweak to kill double shell
grep -q ^AutomaticLoginEnable=True /etc/gdm/custom.conf || pkill -KILL -u gdm

The problem is, that script exits with status 1 because I do not have AutomaticLoginEnable=True set in /etc/gdm/custom.conf, and there is no explicit exit 0 at the end of the script. This is a common bash programming mistake when using the || construct this way at the end of a script or function. My guess is, after the Jan. 4 update, GDM is now more conservative and fails the login if that script exits with status 1 where it didn’t before.

The solution is one of the following:

Add exit 0 to the end of /etc/gdm/PostLogin/Default.
Remove or move away /etc/gdm/PostLogin/Default altogether. Is it still needed?

If the file is still needed, this could be fixed in the Manjaro installer by adding exit 0 at the end. I wonder though, why haven’t others seen this, or have they just not spoken up? I would think this would be a common problem…

linux-aarhus · 9 January 2026 11:16

Or would become one - I don’t know - Mark @Yochanan or Stefano @Ste74 may know…

Yochanan · 9 January 2026 22:42

No. That was removed several years ago.

heistp · 10 January 2026 13:25

Thanks @Yochanan.

What’s still mysterious is that the commit removing the Default file is dated May 18, 2018, but Manjaro was first installed on my machine on July 7, 2020 (same as the last modified date of the Default file). So, I wonder how I even ended up getting that file. Nevertheless, the problem is solved.

linux-aarhus · 10 January 2026 15:22

The installation date, may not correctly reflect the ISO used, but as it is long time ago - so it is impossible to investigate.

heistp · 12 January 2026 09:12

Apparently it got installed somehow, and was not removed in a subsequent upgrade. In any case, I guess we’ll hear from others if they see the same thing…

heistp · 12 January 2026 10:01

For clarity, the final solution is to remove /etc/gdm/PostLogin/Default, if it exists.

Molski · 13 January 2026 00:22

Curious as to what the layout should be. I don’t have that file, and I’ve never modified here to my knowledge.

$ cd /etc/gdm
$ find .
./Init
./Init/Default
./PostLogin
./PostLogin/Default.sample
./PostSession
./PostSession/Default
./PreSession
./PreSession/Default
./Xsession
./custom.conf

And with the exception of Init, the other scripts are mainly empty:

/etc/gdm/PostSession/Default
#!/bin/sh

exit 0

system · 16 January 2026 00:23

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.