You are not logged in.

Pages: 1 2 3 4 5

#1 2025-09-20 02:09:06

oracletoes
Member
Registered: 2025-09-20
Posts: 3

gdm broken after update

I ran an update with yay -Syyu and rebooted. When i get to the gdm greeter, i select my username and enter my password, and the screen goes black for a few seconds, as if it's loading the desktop environment, then it goes back to the initial screen of the greeter with my name selectable. I click my name again, and this time below the password text box "authentication error" is displayed, i can no longer enter text into the password box, and i can no longer use the back button which is on the left of the text box, it seems like gdm has gotten locked up somehow, but i can still select the calendar and settings on the top right, as well as select which desktop environment to use in the bottom right corner.
I can TTY and enter my username and pw and login just fine so it's clear i'm not messing up my login credentials.
I tried reinstalling gdm and gnome-session with pacman, then reenabling the service, but i encountered the same issue. So for now i installed lightdm and its greeter so i can use a graphical environment.
I would like to get gdm fixed, so if anyone can help, this is me asking for it. I'm looking at the gdm page on the arch wiki in the troubleshooting section, but i don't think any of these issues are relevant, but if the solution is obvious, I can learn.

Kernel: 6.16.7-arch1-1
CPU: 13th Gen Intel i9-13900HX (32) @ 5.200GHz
GPU: NVIDIA GeForce RTX 4090 Laptop GPU
drivers: nvidia-580.82.09-2

Last edited by oracletoes (2025-09-20 02:11:22)

Offline

#2 2025-09-20 02:20:26

afader
Member
Registered: 2013-09-12
Posts: 194

Re: gdm broken after update

Did you try downgrading systemd from 258 to 257

Offline

#3 2025-09-20 02:22:49

oracletoes
Member
Registered: 2025-09-20
Posts: 3

Re: gdm broken after update

No, i'll try that now.

Offline

#4 2025-09-20 02:37:31

oracletoes
Member
Registered: 2025-09-20
Posts: 3

Re: gdm broken after update

no luck, i downgraded and switched back to gdm with this:

sudo downgrade systemd systemd-libs systemd-resolvconf systemd-sysvcompat (selected 257 from cache)
sudo systemctl disable lightdm.service
sudo systemctl enable gdm.service
reboot

and get the same issue

Last edited by oracletoes (2025-09-20 02:40:14)

Offline

#5 2025-09-20 22:42:41

woodsb02
Member
Registered: 2013-06-03
Posts: 10

Re: gdm broken after update

I have the same issue when I upgrade to gnome 49 by enabling the extra-testing repository.
What version of gdm/gnome are you running? Do you have extra-testing, extra-staging or gnome-unstable repositories enabled in /etc/pacman.conf?

For gdm 49 - I wonder if it's related to the change from the static gdm user to using dynamic users via userdb.
https://gitlab.archlinux.org/archlinux/ … 58f577140c

Last edited by woodsb02 (2025-09-20 22:48:24)

Offline

#6 2025-09-21 01:14:26

woodsb02
Member
Registered: 2013-06-03
Posts: 10

Re: gdm broken after update

I've raised this bug report: https://gitlab.archlinux.org/archlinux/ … /issues/11

Offline

#7 2025-09-21 02:23:57

woodsb02
Member
Registered: 2013-06-03
Posts: 10

Re: gdm broken after update

This was resolved by also enabling the [core-testing] repository in /etc/pacman.conf, and performing pacman -Syu.
By doing so, the glib2 package was updated to 2.86.0-2

Offline

#8 2025-09-22 10:18:25

stesind
Member
Registered: 2023-05-07
Posts: 3

Re: gdm broken after update

"glib2 package was updated to 2.86.0-2"

I still see the black screen in GDM after updating glib2.

Offline

#9 2025-09-22 11:01:13

stronnag
Member
Registered: 2011-01-25
Posts: 74

Re: gdm broken after update

Same here on two 10+ year old machines  where gdm tries to enable a X11 session (despite the fact that a user session (e.g. via lightdm) will be wayland.
More modern machines have no gdm issue.

Fully current on *-testing.
journal with stack trace from gdm crash. http://0x0.st/KASw.txt

Offline

#10 2025-09-22 14:18:46

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,337

Re: gdm broken after update

Sep 20 22:41:26 eeyore systemd[1]: Starting User Manager for UID 60578...
Sep 20 22:41:26 eeyore unix_chkpwd[1420]: could not obtain user info (gdm-greeter)
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: PAM failed: Authentication service cannot retrieve authentication info
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: Failed to set up PAM session: Operation not permitted
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Sep 20 22:41:26 eeyore systemd[1]: user@60578.service: Main process exited, code=exited, status=224/PAM
Sep 20 22:41:26 eeyore systemd[1]: user@60578.service: Failed with result 'exit-code'.
Sep 20 22:41:26 eeyore systemd[1]: Failed to start User Manager for UID 60578.
Sep 20 22:41:26 eeyore systemd[1]: Started Session 3 of User gdm-greeter.
Sep 20 22:41:26 eeyore /usr/lib/gdm-wayland-session[1428]: dbus-daemon[1428]: [session uid=60578 pid=1428 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=60578 pid=1425 comm="/usr/lib/gdm-wayland-session gnome-session")
Sep 20 22:41:26 eeyore /usr/lib/gdm-wayland-session[1428]: dbus-daemon[1428]: [session uid=60578 pid=1428 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Failed to check if unit gnome-session-wayland@gnome-login.target is active: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Starting GNOME session target: gnome-session-wayland@gnome-login.target
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Failed to start unit gnome-session-wayland@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 20 22:41:26 eeyore kernel: traps: gnome-session-i[1432] trap int3 ip:7f4559441b8c sp:7ffd950409c0 error:0 in libglib-2.0.so.0.8504.0[64b8c,7f45593fb000+a7000]
Sep 20 22:41:26 eeyore systemd-coredump[1440]: Process 1432 (gnome-session-i) of user 60578 terminated abnormally with signal 5/TRAP, processing...
Sep 20 22:41:26 eeyore systemd[1]: Created slice Slice /system/systemd-coredump.
Sep 20 22:41:26 eeyore systemd[1]: Started Process Core Dump (PID 1440/UID 0).
Sep 20 22:41:26 eeyore systemd-coredump[1441]: Process 1432 (gnome-session-i) of user 60578 dumped core.
                                               
                                               Stack trace of thread 1432:
                                               #0  0x00007f4559441b8c g_log_structured_array (libglib-2.0.so.0 + 0x64b8c)
                                               #1  0x00007f45594422e0 g_log_default_handler (libglib-2.0.so.0 + 0x652e0)
                                               #2  0x00007f455944257a g_logv (libglib-2.0.so.0 + 0x6557a)
                                               #3  0x00007f4559442904 g_log (libglib-2.0.so.0 + 0x65904)
                                               #4  0x00005606e5cad686 n/a (/usr/lib/gnome-session-init-worker + 0x2686)
                                               #5  0x00007f4559027675 n/a (libc.so.6 + 0x27675)
                                               #6  0x00007f4559027729 __libc_start_main (libc.so.6 + 0x27729)
                                               #7  0x00005606e5cadc95 n/a (/usr/lib/gnome-session-init-worker + 0x2c95)

Testing is currently at /usr/lib/libglib-2.0.so.0.8600.0 ?

Also 

Sep 20 22:41:26 eeyore unix_chkpwd[1420]: could not obtain user info (gdm-greeter)
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: PAM failed: Authentication service cannot retrieve authentication info
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: Failed to set up PAM session: Operation not permitted
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Sep 20 22:41:26 eeyore systemd[1]: user@60578.service: Main process exited, code=exited, status=224/PAM
Sep 20 22:41:26 eeyore systemd[1]: user@60578.service: Failed with result 'exit-code'.
Sep 20 22:41:26 eeyore systemd[1]: Failed to start User Manager for UID 60578.
id 60578

systemdumb 258 has pulled a super-retarded stunt where only system groups get permissions via udev, if this is GDM and there's any permission requirement itr you might have to fix that GID.


For everyone else:

enabling the extra-testing repository … also enabling the [core-testing] repository after updating glib2.

READ https://wiki.archlinux.org/title/Offici … positories !
Testing is always ALL OR NOTHING! Do not pick isolated testing repos let alone packages. This WILL cause problems for almost sure.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2025-09-22 14:26:55

stronnag
Member
Registered: 2011-01-25
Posts: 74

Re: gdm broken after update

Seth wrote:

Testing is currently at /usr/lib/libglib-2.0.so.0.8600.0 ?

At the (shown) time of the log, yes it was.

I was suspicious about the GID, under investigation.

Offline

#12 2025-09-22 14:54:17

stronnag
Member
Registered: 2011-01-25
Posts: 74

Re: gdm broken after update

To follow up on the UID/GID. On a working system, the dynamic UID for gdm is also 60578. 

Sep 20 22:22:47 wol systemd[1]: Starting User Manager for UID 60578...
Sep 20 22:22:47 wol dbus-broker-launch[860]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Sep 20 22:22:47 wol (systemd)[1083]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[/dev/tty1] user=[gdm-greeter] ruser=[<unknown>] rhost=[<unknown>]
Sep 20 22:22:47 wol (systemd)[1083]: pam_unix(systemd-user:session): session opened for user gdm-greeter(uid=60578) by gdm-greeter(uid=0)
Sep 20 22:22:47 wol systemd-logind[875]: New session '2' of user 'gdm-greeter' with class 'manager-early' and type 'unspecified'.

The main difference being a (wol) a modern GPU and gdm not trying to use X11 (for whatever reason, as the old GPU is wayland capable).

Offline

#13 2025-09-22 15:01:40

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,337

Re: gdm broken after update

Does the worling system also have 

Sep 20 22:41:26 eeyore unix_chkpwd[1420]: could not obtain user info (gdm-greeter)
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: PAM failed: Authentication service cannot retrieve authentication info
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: Failed to set up PAM session: Operation not permitted
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Sep 20 22:41:26 eeyore systemd[1]: user@60578.service: Main process exited, code=exited, status=224/PAM
Sep 20 22:41:26 eeyore systemd[1]: user@60578.service: Failed with result 'exit-code'.
Sep 20 22:41:26 eeyore systemd[1]: Failed to start User Manager for UID 60578.

??

Sep 20 22:41:26 eeyore systemd-logind[790]: New session '3' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:26 eeyore systemd-logind[790]: New session '5' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:26 eeyore systemd-logind[790]: New session '7' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:27 eeyore systemd-logind[790]: New session '9' of user 'gdm-greeter' with class 'greeter' and type 'x11'.
Sep 20 22:41:27 eeyore systemd-logind[790]: New session '10' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:28 eeyore systemd-logind[790]: New session '12' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:28 eeyore systemd-logind[790]: New session '14' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:28 eeyore systemd-logind[790]: New session '16' of user 'gdm-greeter' with class 'greeter' and type 'x11'.
Sep 20 22:41:29 eeyore systemd-logind[790]: New session '17' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:29 eeyore systemd-logind[790]: New session '19' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:29 eeyore systemd-logind[790]: New session '21' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:30 eeyore systemd-logind[790]: New session '23' of user 'gdm-greeter' with class 'greeter' and type 'x11'.
Sep 20 22:41:30 eeyore systemd-logind[790]: New session '24' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:30 eeyore systemd-logind[790]: New session '26' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:31 eeyore systemd-logind[790]: New session '28' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:31 eeyore systemd-logind[790]: New session '30' of user 'gdm-greeter' with class 'greeter' and type 'x11'.
Sep 20 22:41:31 eeyore systemd-logind[790]: New session '31' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:32 eeyore systemd-logind[790]: New session '33' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:32 eeyore systemd-logind[790]: New session '35' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:32 eeyore systemd-logind[790]: New session '37' of user 'gdm-greeter' with class 'greeter' and type 'x11'.

GDM tries to run an X11 instance only because the wayland one is crashing (as is then the X11 one)

I'm pretty sure you main problem is 

Sep 20 22:41:26 eeyore unix_chkpwd[1420]: could not obtain user info (gdm-greeter)
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: PAM failed: Authentication service cannot retrieve authentication info

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2025-09-22 16:01:22

stronnag
Member
Registered: 2011-01-25
Posts: 74

Re: gdm broken after update

The (my) problem appears to be that GDM on X11 is broken.

  • Take a working (wayland) system

  • Edit  /etc/gdm/custom.conf to force X11

  • Enjoy GDM failing / core dumping etc. as above.

Offline

#15 2025-09-22 18:30:51

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,337

Re: gdm broken after update

GDM/X11 will fail if eg. you don't have the (optional) xorg-server package installed, but to re-iterate: gdm/x11 only fails *AFTER* gdm/wayland has crashed three times in a row. I don't believe at all that this is even remotely related to your problem.

Does your working system also have the pam errors?

pacman -Qikk gdm pam pambase

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2025-09-22 20:10:54

stronnag
Member
Registered: 2011-01-25
Posts: 74

Re: gdm broken after update

seth wrote:

GDM/X11 will fail if eg. you don't have the (optional) xorg-server package installed, but to re-iterate: gdm/x11 only fails *AFTER* gdm/wayland has crashed three times in a row. I don't believe at all that this is even remotely related to your problem.

I have X11 server; lightdm (X11) works fine as an (ugly) login manager

seth wrote:

Does your working system also have the pam errors?

No.
None of my systems had any gdm  (or pam) issues prior to Gnome 49.

Last edited by stronnag (2025-09-22 20:19:02)

Offline

#17 2025-09-22 20:14:41

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,337

Re: gdm broken after update

I have X11 server; lightdm (X11) works fine as an (ugly) login manager

On the otherwise working machine where you noticed that GDM/X11 failed?

None of my systems had any gdm  (or pam) issues prior to Gnome 49.

I'd focus on that. The working machine is on 49/testing as well?
What about the -Qikk output?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#18 2025-09-22 20:52:42

ReLoneR
Member
Registered: 2025-09-22
Posts: 4

Re: gdm broken after update

same here. Gdm fails to start on gnome 49 if WaylandEnable = false

Offline

#19 2025-09-22 21:10:17

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,337

Re: gdm broken after update

But w/ wayland works?
Because that doesn't for stronnag

Sep 20 22:41:26 eeyore systemd-logind[790]: New session '3' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 20 22:41:26 eeyore systemd[1]: Created slice User Slice of UID 60578.
Sep 20 22:41:26 eeyore systemd[1]: Starting User Runtime Directory /run/user/60578...
Sep 20 22:41:26 eeyore systemd[1149]: Reached target Sound Card.
Sep 20 22:41:26 eeyore systemd[1]: Finished User Runtime Directory /run/user/60578.
Sep 20 22:41:26 eeyore systemd[1]: Starting User Manager for UID 60578...
Sep 20 22:41:26 eeyore unix_chkpwd[1420]: could not obtain user info (gdm-greeter)
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: PAM failed: Authentication service cannot retrieve authentication info
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: Failed to set up PAM session: Operation not permitted
Sep 20 22:41:26 eeyore (systemd)[1417]: user@60578.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Sep 20 22:41:26 eeyore systemd[1]: user@60578.service: Main process exited, code=exited, status=224/PAM
Sep 20 22:41:26 eeyore systemd[1]: user@60578.service: Failed with result 'exit-code'.
Sep 20 22:41:26 eeyore systemd[1]: Failed to start User Manager for UID 60578.
Sep 20 22:41:26 eeyore systemd[1]: Started Session 3 of User gdm-greeter.
Sep 20 22:41:26 eeyore /usr/lib/gdm-wayland-session[1428]: dbus-daemon[1428]: [session uid=60578 pid=1428 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=60578 pid=1425 comm="/usr/lib/gdm-wayland-session gnome-session")
Sep 20 22:41:26 eeyore /usr/lib/gdm-wayland-session[1428]: dbus-daemon[1428]: [session uid=60578 pid=1428 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Failed to check if unit gnome-session-wayland@gnome-login.target is active: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Starting GNOME session target: gnome-session-wayland@gnome-login.target
Sep 20 22:41:26 eeyore gnome-session-i[1432]: Failed to start unit gnome-session-wayland@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 20 22:41:26 eeyore kernel: traps: gnome-session-i[1432] trap int3 ip:7f4559441b8c sp:7ffd950409c0 error:0 in libglib-2.0.so.0.8504.0[64b8c,7f45593fb000+a7000]
Sep 20 22:41:26 eeyore systemd-coredump[1440]: Process 1432 (gnome-session-i) of user 60578 terminated abnormally with signal 5/TRAP, processing...
Sep 20 22:41:26 eeyore systemd[1]: Created slice Slice /system/systemd-coredump.
Sep 20 22:41:26 eeyore systemd[1]: Started Process Core Dump (PID 1440/UID 0).
Sep 20 22:41:26 eeyore systemd-coredump[1441]: Process 1432 (gnome-session-i) of user 60578 dumped core.
                                               
                                               Stack trace of thread 1432:
                                               #0  0x00007f4559441b8c g_log_structured_array (libglib-2.0.so.0 + 0x64b8c)
                                               #1  0x00007f45594422e0 g_log_default_handler (libglib-2.0.so.0 + 0x652e0)
                                               #2  0x00007f455944257a g_logv (libglib-2.0.so.0 + 0x6557a)
                                               #3  0x00007f4559442904 g_log (libglib-2.0.so.0 + 0x65904)
                                               #4  0x00005606e5cad686 n/a (/usr/lib/gnome-session-init-worker + 0x2686)
                                               #5  0x00007f4559027675 n/a (libc.so.6 + 0x27675)
                                               #6  0x00007f4559027729 __libc_start_main (libc.so.6 + 0x27729)
                                               #7  0x00005606e5cadc95 n/a (/usr/lib/gnome-session-init-worker + 0x2c95)
                                               
                                               Stack trace of thread 1437:
                                               #0  0x00007f455911876d syscall (libc.so.6 + 0x11876d)
                                               #1  0x00007f455946c7ee g_cond_wait (libglib-2.0.so.0 + 0x8f7ee)
                                               #2  0x00007f45594031cd n/a (libglib-2.0.so.0 + 0x261cd)
                                               #3  0x00007f4559475447 n/a (libglib-2.0.so.0 + 0x98447)
                                               #4  0x00007f455947487c n/a (libglib-2.0.so.0 + 0x9787c)
                                               #5  0x00007f45590969cb n/a (libc.so.6 + 0x969cb)
                                               #6  0x00007f455911aa0c n/a (libc.so.6 + 0x11aa0c)
                                               
                                               Stack trace of thread 1438:
                                               #0  0x00007f455909f042 n/a (libc.so.6 + 0x9f042)
                                               #1  0x00007f45590931ac n/a (libc.so.6 + 0x931ac)
                                               #2  0x00007f45590931f4 n/a (libc.so.6 + 0x931f4)
                                               #3  0x00007f455910da36 ppoll (libc.so.6 + 0x10da36)
                                               #4  0x00007f455943d744 n/a (libglib-2.0.so.0 + 0x60744)
                                               #5  0x00007f455943d825 g_main_context_iteration (libglib-2.0.so.0 + 0x60825)
                                               #6  0x00007f455943d872 n/a (libglib-2.0.so.0 + 0x60872)
                                               #7  0x00007f455947487c n/a (libglib-2.0.so.0 + 0x9787c)
                                               #8  0x00007f45590969cb n/a (libc.so.6 + 0x969cb)
                                               #9  0x00007f455911aa0c n/a (libc.so.6 + 0x11aa0c)
                                               
                                               Stack trace of thread 1439:
                                               #0  0x00007f455909f042 n/a (libc.so.6 + 0x9f042)
                                               #1  0x00007f45590931ac n/a (libc.so.6 + 0x931ac)
                                               #2  0x00007f45590931f4 n/a (libc.so.6 + 0x931f4)
                                               #3  0x00007f455910da36 ppoll (libc.so.6 + 0x10da36)
                                               #4  0x00007f455943d744 n/a (libglib-2.0.so.0 + 0x60744)
                                               #5  0x00007f455943d9d7 g_main_loop_run (libglib-2.0.so.0 + 0x609d7)
                                               #6  0x00007f45596ae2a4 n/a (libgio-2.0.so.0 + 0x11a2a4)
                                               #7  0x00007f455947487c n/a (libglib-2.0.so.0 + 0x9787c)
                                               #8  0x00007f45590969cb n/a (libc.so.6 + 0x969cb)
                                               #9  0x00007f455911aa0c n/a (libc.so.6 + 0x11aa0c)
                                               ELF object binary architecture: AMD x86-64
Sep 20 22:41:26 eeyore systemd[1]: systemd-coredump@0-1-1440_1441-0.service: Deactivated successfully.
Sep 20 22:41:26 eeyore gdm[1378]: Gdm: GdmDisplay: Session never registered, failing
Sep 20 22:41:26 eeyore systemd[1]: session-3.scope: Deactivated successfully.
Sep 20 22:41:26 eeyore systemd-logind[790]: Session 3 logged out. Waiting for processes to exit.
Sep 20 22:41:26 eeyore systemd-logind[790]: Removed session 3.
Sep 20 22:41:26 eeyore gdm[1378]: Gdm: Child process -1425 was already dead.
Sep 20 22:41:26 eeyore gdm[1378]: Gdm: GdmDisplay: Session never registered, failing
Sep 20 22:41:26 eeyore gdm[1378]: Gdm: Child process -1425 was already dead.

Before than much later

Sep 20 22:41:27 eeyore systemd-logind[790]: New session '9' of user 'gdm-greeter' with class 'greeter' and type 'x11'.
Sep 20 22:41:27 eeyore systemd[1]: Created slice User Slice of UID 60584.
Sep 20 22:41:27 eeyore systemd[1]: Starting User Runtime Directory /run/user/60584...
Sep 20 22:41:27 eeyore systemd[1]: Finished User Runtime Directory /run/user/60584.
Sep 20 22:41:27 eeyore systemd[1]: Starting User Manager for UID 60584...
Sep 20 22:41:27 eeyore unix_chkpwd[1731]: could not obtain user info (gdm-greeter)
Sep 20 22:41:27 eeyore (systemd)[1730]: user@60584.service: PAM failed: Authentication service cannot retrieve authentication info
Sep 20 22:41:27 eeyore (systemd)[1730]: user@60584.service: Failed to set up PAM session: Operation not permitted
Sep 20 22:41:27 eeyore (systemd)[1730]: user@60584.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Sep 20 22:41:27 eeyore systemd[1]: user@60584.service: Main process exited, code=exited, status=224/PAM
Sep 20 22:41:27 eeyore systemd[1]: user@60584.service: Failed with result 'exit-code'.
Sep 20 22:41:27 eeyore systemd[1]: Failed to start User Manager for UID 60584.
Sep 20 22:41:27 eeyore systemd[1]: Started Session 9 of User gdm-greeter.
Sep 20 22:41:27 eeyore gdm[1378]: Gdm: GdmSession: no session desktop files installed, aborting...
Sep 20 22:41:27 eeyore kernel: traps: gdm[1378] trap int3 ip:7f577f5c364b sp:7ffee6276ef0 error:0 in libglib-2.0.so.0.8504.0[6564b,7f577f57c000+a7000]
Sep 20 22:41:27 eeyore systemd-coredump[1737]: Process 1378 (gdm) of user 0 terminated abnormally with signal 5/TRAP, processing...
Sep 20 22:41:27 eeyore systemd[1]: Started Process Core Dump (PID 1737/UID 0).
Sep 20 22:41:27 eeyore systemd-coredump[1739]: Process 1378 (gdm) of user 0 dumped core.
                                               
                                               Stack trace of thread 1378:
                                               #0  0x00007f577f5c364b g_logv (libglib-2.0.so.0 + 0x6564b)
                                               #1  0x00007f577f5c3904 g_log (libglib-2.0.so.0 + 0x65904)
                                               #2  0x000055c212c20ddc n/a (/usr/bin/gdm + 0x33ddc)
                                               #3  0x000055c212c27b65 n/a (/usr/bin/gdm + 0x3ab65)
                                               #4  0x00007f577f2aaac6 n/a (libffi.so.8 + 0x7ac6)
                                               #5  0x00007f577f2a776b n/a (libffi.so.8 + 0x476b)
                                               #6  0x00007f577f2aa06e ffi_call (libffi.so.8 + 0x706e)
                                               #7  0x00007f577f6ce818 g_cclosure_marshal_generic_va (libgobject-2.0.so.0 + 0x18818)
                                               #8  0x00007f577f6e8c77 n/a (libgobject-2.0.so.0 + 0x32c77)
                                               #9  0x00007f577f6e8d89 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32d89)
                                               #10 0x00007f577f6e8e44 g_signal_emit (libgobject-2.0.so.0 + 0x32e44)
                                               #11 0x000055c212c251f2 n/a (/usr/bin/gdm + 0x381f2)
                                               #12 0x00007f577f4349cc n/a (libgio-2.0.so.0 + 0xa89cc)
                                               #13 0x00007f577f43a472 n/a (libgio-2.0.so.0 + 0xae472)
                                               #14 0x00007f577f4aea0e n/a (libgio-2.0.so.0 + 0x122a0e)
                                               #15 0x00007f577f4349cc n/a (libgio-2.0.so.0 + 0xa89cc)
                                               #16 0x00007f577f43a472 n/a (libgio-2.0.so.0 + 0xae472)
                                               #17 0x00007f577f4a48f3 n/a (libgio-2.0.so.0 + 0x1188f3)
                                               #18 0x00007f577f4349cc n/a (libgio-2.0.so.0 + 0xa89cc)
                                               #19 0x00007f577f434a15 n/a (libgio-2.0.so.0 + 0xa8a15)
                                               #20 0x00007f577f5bcf4d n/a (libglib-2.0.so.0 + 0x5ef4d)
                                               #21 0x00007f577f5be617 n/a (libglib-2.0.so.0 + 0x60617)
                                               #22 0x00007f577f5be9d7 g_main_loop_run (libglib-2.0.so.0 + 0x609d7)
                                               #23 0x000055c212bfa22f n/a (/usr/bin/gdm + 0xd22f)
                                               #24 0x00007f577f027675 n/a (libc.so.6 + 0x27675)
                                               #25 0x00007f577f027729 __libc_start_main (libc.so.6 + 0x27729)
                                               #26 0x000055c212bfa595 n/a (/usr/bin/gdm + 0xd595)
                                               
                                               Stack trace of thread 1379:
                                               #0  0x00007f577f11876d syscall (libc.so.6 + 0x11876d)
                                               #1  0x00007f577f5ed7ee g_cond_wait (libglib-2.0.so.0 + 0x8f7ee)
                                               #2  0x00007f577f5841cd n/a (libglib-2.0.so.0 + 0x261cd)
                                               #3  0x00007f577f5f6447 n/a (libglib-2.0.so.0 + 0x98447)
                                               #4  0x00007f577f5f587c n/a (libglib-2.0.so.0 + 0x9787c)
                                               #5  0x00007f577f0969cb n/a (libc.so.6 + 0x969cb)
                                               #6  0x00007f577f11aa0c n/a (libc.so.6 + 0x11aa0c)
                                               
                                               Stack trace of thread 1381:
                                               #0  0x00007f577f09f042 n/a (libc.so.6 + 0x9f042)
                                               #1  0x00007f577f0931ac n/a (libc.so.6 + 0x931ac)
                                               #2  0x00007f577f0931f4 n/a (libc.so.6 + 0x931f4)
                                               #3  0x00007f577f10da36 ppoll (libc.so.6 + 0x10da36)
                                               #4  0x00007f577f5be744 n/a (libglib-2.0.so.0 + 0x60744)
                                               #5  0x00007f577f5be9d7 g_main_loop_run (libglib-2.0.so.0 + 0x609d7)
                                               #6  0x00007f577f4a62a4 n/a (libgio-2.0.so.0 + 0x11a2a4)
                                               #7  0x00007f577f5f587c n/a (libglib-2.0.so.0 + 0x9787c)
                                               #8  0x00007f577f0969cb n/a (libc.so.6 + 0x969cb)
                                               #9  0x00007f577f11aa0c n/a (libc.so.6 + 0x11aa0c)
                                               
                                               Stack trace of thread 1382:
                                               #0  0x00007f577f09f042 n/a (libc.so.6 + 0x9f042)
                                               #1  0x00007f577f0931ac n/a (libc.so.6 + 0x931ac)
                                               #2  0x00007f577f0931f4 n/a (libc.so.6 + 0x931f4)
                                               #3  0x00007f577f11acf5 epoll_wait (libc.so.6 + 0x11acf5)
                                               #4  0x00007f577f75a430 sd_event_wait (libsystemd.so.0 + 0x45430)
                                               #5  0x00007f577f75b844 sd_event_run (libsystemd.so.0 + 0x46844)
                                               #6  0x00007f577f75b990 sd_event_loop (libsystemd.so.0 + 0x46990)
                                               #7  0x000055c212c0a000 n/a (/usr/bin/gdm + 0x1d000)
                                               #8  0x00007f577f5f587c n/a (libglib-2.0.so.0 + 0x9787c)
                                               #9  0x00007f577f0969cb n/a (libc.so.6 + 0x969cb)
                                               #10 0x00007f577f11aa0c n/a (libc.so.6 + 0x11aa0c)
                                               
                                               Stack trace of thread 1393:
                                               #0  0x00007f577f11876d syscall (libc.so.6 + 0x11876d)
                                               #1  0x00007f577f5ee77e g_cond_wait_until (libglib-2.0.so.0 + 0x9077e)
                                               #2  0x00007f577f584197 n/a (libglib-2.0.so.0 + 0x26197)
                                               #3  0x00007f577f5f729b n/a (libglib-2.0.so.0 + 0x9929b)
                                               #4  0x00007f577f5f587c n/a (libglib-2.0.so.0 + 0x9787c)
                                               #5  0x00007f577f0969cb n/a (libc.so.6 + 0x969cb)
                                               #6  0x00007f577f11aa0c n/a (libc.so.6 + 0x11aa0c)
                                               
                                               Stack trace of thread 1380:
                                               #0  0x00007f577f09f042 n/a (libc.so.6 + 0x9f042)
                                               #1  0x00007f577f0931ac n/a (libc.so.6 + 0x931ac)
                                               #2  0x00007f577f0931f4 n/a (libc.so.6 + 0x931f4)
                                               #3  0x00007f577f10da36 ppoll (libc.so.6 + 0x10da36)
                                               #4  0x00007f577f5be744 n/a (libglib-2.0.so.0 + 0x60744)
                                               #5  0x00007f577f5be825 g_main_context_iteration (libglib-2.0.so.0 + 0x60825)
                                               #6  0x00007f577f5be872 n/a (libglib-2.0.so.0 + 0x60872)
                                               #7  0x00007f577f5f587c n/a (libglib-2.0.so.0 + 0x9787c)
                                               #8  0x00007f577f0969cb n/a (libc.so.6 + 0x969cb)
                                               #9  0x00007f577f11aa0c n/a (libc.so.6 + 0x11aa0c)
                                               ELF object binary architecture: AMD x86-64
Sep 20 22:41:27 eeyore systemd[1]: gdm.service: Main process exited, code=dumped, status=5/TRAP
Sep 20 22:41:27 eeyore systemd[1]: gdm.service: Failed with result 'core-dump'.
Sep 20 22:41:27 eeyore systemd[1]: gdm.service: Triggering OnFailure= dependencies.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#20 2025-09-22 21:33:12

stronnag
Member
Registered: 2011-01-25
Posts: 74

Re: gdm broken after update

One update:
systemd 258-3 cleans this up a lot. The pam messages are gone. gdm is still crashing, somewhat more cleanly.
Think I'll leave this in the hands of upstream for now.

Offline

#21 2025-09-22 21:40:37

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,337

Re: gdm broken after update

https://gitlab.archlinux.org/archlinux/ … mmits/main
Not sure which of the recent commits could fix the pam issues, do you still get

Process org.freedesktop.systemd1 exited with status 1

?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#22 2025-09-22 23:57:32

rudeblunt
Member
Registered: 2025-09-22
Posts: 2

Re: gdm broken after update

gdm is crashing because no /usr/share/xsessions dir is provided by gnome-session package anymore .... 

pacman -Ql | grep wayland-sessions
gnome-session /usr/share/wayland-sessions/
gnome-session /usr/share/wayland-sessions/gnome-wayland.desktop
gnome-session /usr/share/wayland-sessions/gnome.desktop
gnome-shell-extensions /usr/share/wayland-sessions/
gnome-shell-extensions /usr/share/wayland-sessions/gnome-classic-wayland.desktop
gnome-shell-extensions /usr/share/wayland-sessions/gnome-classic.desktop

I "fixed" my install by using the same ones from wayland (they work fine) 

sudo ln -s /usr/share/wayland-sessions/ /usr/share/xsessions

but I think that the gnome-session package needs some fixin'

Offline

#23 2025-09-23 07:26:46

ReLoneR
Member
Registered: 2025-09-22
Posts: 4

Re: gdm broken after update

seth wrote:

But w/ wayland works?

yes

Offline

#24 2025-09-23 07:40:44

windy
Member
Registered: 2013-11-10
Posts: 58

Re: gdm broken after update

rudeblunt wrote:

gdm is crashing because no /usr/share/xsessions dir is provided by gnome-session package anymore ....

On my system, the directory is present but I am also getting a core dump like seth.

Offline

#25 2025-09-23 07:42:48

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,337

Re: gdm broken after update

Probably just #22 which is probably of the upstream forth and back on removing X11 entirely.
https://gitlab.archlinux.org/archlinux/ … -/issues/1

Doesn't explain @stronnag's problems w/ the wayland session.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1 2 3 4 5

Board footer

Powered by FluxBB