Arch Linux

injiniero

Member

Registered: 2022-04-26

Posts: 33

Re: gdm broken after update

I guess segfaulting should™ not but has to be expected from <gnomestuff> but as mentioned: regardless of the current mess, X11 support is supposed to be completely removed w/ v50 - leaving GDM behind is inevitable if you want to stay on X11

If I understand this correctly, is it possible to continue using GNome 49 on X11 by replacing GDM with LightDM?
I can't use Wayland on my computer because it doesn't work properly with my NVIDIA GeForce GTX 760 card and the nvidia-470xx-dkms driver.

Personally, I think removing x11 support from GNome when Wayland isn't yet a mature project is a serious mistake.

---

I was a precocious child at 50

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,050

Re: gdm broken after update

No, the long shot here is/was to get GDM on X11 working.
X11 is officially not compiled into "gnome", the behavior of GDM and https://bbs.archlinux.org/viewtopic.php … 8#p2263248 suggest it might still work *there*

I think removing [N] from GNome when [M] isn't yet a mature project is a serious mistake.

Gnome has a long standing history of cutting features because they can and don't care.
It's effectively developed like a hobby pet-peeve project where you're constantly subjected to the whiffs and whims of some latest knee-jerk idea.

That being said:

I can't use Wayland on my computer because it doesn't work properly with my NVIDIA GeForce GTX 760 card and the nvidia-470xx-dkms driver.

Are you sure about that?
Unlike 390xx, the 470xx drivers support KMS and GBM - what exactly doesn't work? Do you have an open thread about that (please don't hijack this one)

---

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

jose1711

Member

Registered: 2006-07-08

Posts: 147

Re: gdm broken after update

Back to the PAM problem:
So unix_chkpwd checks /etc/shadow and is typically called from the unix pam module.

sudo grep -i gdm /etc/shadow

will likely yield no results.
If anybody has downgraded gnome to deal w/ this: do you have a shadow entry for gdm?
Also there're probably some /etc/pam.d/*gdm* ?

GDM should™ not use pam_unix/shadow when there's no shadow entry, but what if you just add

gdm-greeter:!*:20224::::::

to /etc/shadow?

@seth thank you, i finally got the GDM screen i think this post should be pinned (or at least documented in arch wiki).

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,050

Re: gdm broken after update

That's been a workaround for what's most likely actually a now mis-/insufficiently configured nsswitch.conf, https://bbs.archlinux.org/viewtopic.php … 5#p2263495

---

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

sultanoswing

Member

Registered: 2008-07-23

Posts: 316

Re: gdm broken after update

Thanks for the nsswitch.conf and /etc/shadow fixes....I ran into the same black screen / blinking cursor bug after upgrading this afternoon.

---

Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | ThinkPad X1 | ASUS ux303ua | Surface Laptop 2 | Minisforum UM780

Dexter23

Member

Registered: 2022-02-19

Posts: 27

Re: gdm broken after update

Hi have a problem now with AnyDesk i use when connecting to remote pc it seems slow/lagging on wayland server, but i want to use Gnome as DE.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,050

Re: gdm broken after update

@sultanoswing, you should not require the shadow entry, I only suggested that as a mitigation to give the pam module what it wasn't supposed to ask for anyway

@Dexter23, please open a new thread.
This one's busy enough and not to be hijacked with follow-up "but gnome wayland causes problems".

---

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

sultanoswing

Member

Registered: 2008-07-23

Posts: 316

Re: gdm broken after update

@sultanoswing, you should not require the shadow entry, I only suggested that as a mitigation to give the pam module what it wasn't supposed to ask for anyway

Awww...but I like belts & braces

Removed.

---

Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | ThinkPad X1 | ASUS ux303ua | Surface Laptop 2 | Minisforum UM780

nuclearpidgeon

Member

Registered: 2023-04-07

Posts: 4

Website

Re: gdm broken after update

Hello from a first-gen Framework 13 with this exact same issue - I pacman updated and all of a sudden got hit with a black screen and blinking underscore cursor after boot.
The update included:
* gdm 48.0-2 -> 49.0.1-1
* systemd 257.9-1 -> 258-4

I have Wayland set up but as others noted, gdm will fall back to trying X11 if a Wayland start fails, which can lead to some misleading logs. (incidentally it seems there's a 5x failure retry too):

Sep 28 23:28:12 fishtin gnome-session[3559]: 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 28 23:28:12 fishtin gnome-session[3614]: 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 28 23:28:12 fishtin gnome-session[3656]: 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 28 23:28:12 fishtin gnome-session[3697]: 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 28 23:28:13 fishtin gnome-session[3737]: 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 28 23:28:13 fishtin gnome-session[3777]: 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 28 23:28:13 fishtin gnome-session[3827]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 28 23:28:14 fishtin gnome-session[3886]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 28 23:28:14 fishtin gnome-session[3944]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 28 23:28:15 fishtin gnome-session[4002]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 28 23:28:15 fishtin gnome-session[4060]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist

---

adding the gdm-greeter user to /etc/shadow worked. GDM started, and I succesfully logged in to gnome 49 on wayland.

gdm-greeter:!*:20224::::::

This also worked as a fix for me at first. I just saw the nsswitch stuff as well though - my one had shadow: files too, so I backed out the /etc/shadow change and changed the /etc/nsswitch.conf line to shadow: files systemd and that also seems to work.

Thanks all for your detective work here!

---

Re: any org.freedesktop.systemd1 errors like:

Sep 28 23:10:40 fishtin /usr/lib/gdm-wayland-session[1269]: dbus-daemon[1269]: [session uid=60579 pid=1269 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

it seems systemd is... just "like that" - there's a service file for that dbus name that... has /bin/false as an exec rule https://github.com/systemd/systemd/issu … -762250216

Last edited by nuclearpidgeon (2025-09-28 14:55:20)

drslmr

Member

Registered: 2011-05-14

Posts: 58

Re: gdm broken after update

I tried the suggested modification in nsswitch.conf and adding gdm-greeeter to shadow and symlinking xsession.

I still can't start gdm.

Where in nsswitch.conf I have to deal with sss as well.

Is it necessary in addition to add gdm-greeter to passwd? Because my system says gdm-greeter is unknown user?

My system may be quit different, since I'm using openafs, kerboros and ldap to login using the home under afs. And therefore I had to modify pam and some other files in etc.

Sep 30 10:43:56 myhost systemd[1]: Started Accounts Service.
Sep 30 10:43:56 myhost systemd[1]: Startup finished in 15.808s (firmware) + 477ms (loader) + 4.732s (kernel) + 9.025s (userspace) = 30.043s.
Sep 30 10:43:56 myhost systemd-logind[712]: New session '1' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 30 10:43:56 myhost systemd[1]: Created slice User Slice of UID 60584.
Sep 30 10:43:56 myhost systemd[1]: Starting User Runtime Directory /run/user/60584...
Sep 30 10:43:56 myhost systemd[1]: Finished User Runtime Directory /run/user/60584.
Sep 30 10:43:56 myhost systemd[1]: Starting User Manager for UID 60584...
Sep 30 10:43:56 myhost sssd_be[707]: Backend is online
Sep 30 10:43:56 myhost (systemd)[851]: pam_sss(systemd-user:account): Access denied for user gdm-greeter: 10 (User not known to the underlying authentication module)
Sep 30 10:43:56 myhost (systemd)[851]: user@60584.service: PAM failed: User not known to the underlying authentication module
Sep 30 10:43:56 myhost (systemd)[851]: user@60584.service: Failed to set up PAM session: Operation not permitted
Sep 30 10:43:56 myhost (systemd)[851]: user@60584.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Sep 30 10:43:56 myhost systemd[1]: user@60584.service: Main process exited, code=exited, status=224/PAM
Sep 30 10:43:56 myhost systemd[1]: user@60584.service: Failed with result 'exit-code'.
Sep 30 10:43:56 myhost systemd[1]: Failed to start User Manager for UID 60584.
Sep 30 10:43:56 myhost systemd[1]: Started Session 1 of User gdm-greeter.
Sep 30 10:43:56 myhost /usr/lib/gdm-wayland-session[857]: dbus-daemon[857]: [session uid=60584 pid=857 pidfd=8] Activating service name='org.freedesktop.systemd1' reque>
Sep 30 10:43:56 myhost /usr/lib/gdm-wayland-session[857]: dbus-daemon[857]: [session uid=60584 pid=857 pidfd=8] Activated service 'org.freedesktop.systemd1' failed: Pro>
Sep 30 10:43:56 myhost gnome-session-i[861]: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.syste>
Sep 30 10:43:56 myhost gnome-session-i[861]: Failed to check if unit gnome-session-wayland@gnome-login.target is active: GDBus.Error:org.freedesktop.DBus.Error.NameHasN>
Sep 30 10:43:56 myhost gnome-session-i[861]: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd>
Sep 30 10:43:56 myhost gnome-session-i[861]: Starting GNOME session target: gnome-session-wayland@gnome-login.target
Sep 30 10:43:56 myhost gnome-session-i[861]: Failed to start unit gnome-session-wayland@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name >
Sep 30 10:43:56 myhost kernel: traps: gnome-session-i[861] trap int3 ip:7f8db9176b8c sp:7ffd86aa8b60 error:0 in libglib-2.0.so.0.8600.0[64b8c,7f8db9130000+a7000]
Sep 30 10:43:56 myhost systemd-coredump[869]: Process 861 (gnome-session-i) of user 60584 terminated abnormally with signal 5/TRAP, processing...
Sep 30 10:43:57 myhost systemd[1]: Created slice Slice /system/systemd-coredump.
Sep 30 10:43:57 myhost systemd[1]: Started Process Core Dump (PID 869/UID 0).
Sep 30 10:43:57 myhost systemd-coredump[870]: [?] Process 861 (gnome-session-i) of user 60584 dumped core.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,050

Re: gdm broken after update

Please post your current /etc/nsswitch.conf (and please don't copy/paste out of the pager, it truncates output. In doubt run "/etc/nsswitch.conf | curl -F 'file=@-' 0x0.st" and post the link)

---

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

drslmr

Member

Registered: 2011-05-14

Posts: 58

Re: gdm broken after update

cat /etc/nsswitch.conf
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: compat sss systemd
group: compat sss systemd
shadow: compat sss systemd
gshadow: compat sss systemd

publickey: compat

#hosts: compat mymachines myhostname resolve [!UNAVAIL=return] dns
hosts: compat mymachines myhostname resolve dns
networks: compat

protocols: compat
services: compat
ethers: compat
rpc: compat

netgroup: compat sss

drslmr

Member

Registered: 2011-05-14

Posts: 58

Re: gdm broken after update

I had already modified nsswitch.conf. Adding the gshadow line and replacing files with compat.

Last edited by drslmr (2025-09-30 11:45:41)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,050

Re: gdm broken after update

https://gitlab.archlinux.org/archlinux/ … type=heads
https://bbs.archlinux.org/viewtopic.php … 5#p2263495
I suppose sss is getting in the way?

---

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

drslmr

Member

Registered: 2011-05-14

Posts: 58

Re: gdm broken after update

Ok, I will check later. But pam_unix is tried first, I guess, and sss only if unix falls?

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,050

Re: gdm broken after update

The key entry in nsswitch is "shadow: files systemd" - yours is now "shadow: compat sss systemd" so if sss shortcuts this you never reach systemd (the apparently important stage)

---

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

drslmr

Member

Registered: 2011-05-14

Posts: 58

Re: gdm broken after update

I changed nsswitch.conf to:

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files  systemd
group: files  systemd
shadow: files  systemd
gshadow: files  systemd

publickey: files

#hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
hosts: files mymachines myhostname resolve dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files 

But still no success.

Sep 30 15:21:32 myhost systemd[1]: Finished Permit User Sessions.
Sep 30 15:21:32 myhost systemd[1]: Started Command Scheduler.
Sep 30 15:21:32 myhost systemd[1]: Starting GNOME Display Manager...
Sep 30 15:21:32 myhost crond[786]: (CRON) STARTUP (1.7.2)
Sep 30 15:21:32 myhost crond[786]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 69% if used.)
Sep 30 15:21:32 myhost crond[786]: (CRON) INFO (running with inotify support)
Sep 30 15:21:32 myhost crond[786]: (dressel) ORPHAN (no passwd entry)
Sep 30 15:21:32 myhost systemd[1]: Started GNOME Display Manager.
Sep 30 15:21:32 myhost systemd-hostnamed[730]: Hostname set to <myhost> (static)
Sep 30 15:21:32 myhost systemd[1]: Starting Accounts Service...
Sep 30 15:21:32 myhost accounts-daemon[794]: started daemon version 23.13.0
Sep 30 15:21:32 myhost systemd[1]: Started Accounts Service.
Sep 30 15:21:32 myhost systemd[1]: Started The Apache HTTP Server.
Sep 30 15:21:32 myhost systemd-logind[701]: New session '1' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 30 15:21:32 myhost systemd[1]: Created slice User Slice of UID 60578.
Sep 30 15:21:32 myhost systemd[1]: Reached target Multi-User System.
Sep 30 15:21:32 myhost systemd[1]: Reached target Graphical Interface.
Sep 30 15:21:32 myhost systemd[1]: Starting User Runtime Directory /run/user/60578...
Sep 30 15:21:32 myhost systemd[1]: Finished User Runtime Directory /run/user/60578.
Sep 30 15:21:32 myhost systemd[1]: Starting User Manager for UID 60578...
Sep 30 15:21:32 myhost (systemd)[826]: pam_sss(systemd-user:account): Access denied for user gdm-greeter: 10 (User not known to the underlying authentication module)
Sep 30 15:21:32 myhost (systemd)[826]: user@60578.service: PAM failed: User not known to the underlying authentication module
Sep 30 15:21:32 myhost (systemd)[826]: user@60578.service: Failed to set up PAM session: Operation not permitted
Sep 30 15:21:32 myhost (systemd)[826]: user@60578.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Sep 30 15:21:32 myhost systemd[1]: user@60578.service: Main process exited, code=exited, status=224/PAM
Sep 30 15:21:32 myhost systemd[1]: user@60578.service: Failed with result 'exit-code'.
Sep 30 15:21:32 myhost systemd[1]: Failed to start User Manager for UID 60578.
Sep 30 15:21:32 myhost systemd[1]: Started Session 1 of User gdm-greeter.
Sep 30 15:21:32 myhost systemd[1]: Startup finished in 13.518s (firmware) + 475ms (loader) + 1.770s (kernel) + 7.875s (userspace) = 23.640s.
Sep 30 15:21:32 myhost /usr/lib/gdm-wayland-session[833]: dbus-daemon[833]: [session uid=60578 pid=833 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=60578 pid=830 comm="/usr/lib/gdm-wayland-session gnome-session")
Sep 30 15:21:32 myhost /usr/lib/gdm-wayland-session[833]: dbus-daemon[833]: [session uid=60578 pid=833 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Sep 30 15:21:32 myhost gnome-session-i[837]: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 30 15:21:32 myhost gnome-session-i[837]: 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 30 15:21:32 myhost gnome-session-i[837]: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Sep 30 15:21:32 myhost gnome-session-i[837]: Starting GNOME session target: gnome-session-wayland@gnome-login.target
Sep 30 15:21:32 myhost gnome-session-i[837]: 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 30 15:21:32 myhost kernel: traps: gnome-session-i[837] trap int3 ip:7f6321389b8c sp:7ffe95cc3b60 error:0 in libglib-2.0.so.0.8600.0[64b8c,7f6321343000+a7000]
Sep 30 15:21:32 myhost systemd-coredump[845]: Process 837 (gnome-session-i) of user 60578 terminated abnormally with signal 5/TRAP, processing...
Sep 30 15:21:32 myhost systemd[1]: Created slice Slice /system/systemd-coredump.
Sep 30 15:21:32 myhost systemd[1]: Started Process Core Dump (PID 845/UID 0).
Sep 30 15:21:32 myhost systemd-coredump[846]: Process 837 (gnome-session-i) of user 60578 dumped core.
                                                  
                                                  Stack trace of thread 837:
                                                  #0  0x00007f6321389b8c g_log_structured_array (libglib-2.0.so.0 + 0x64b8c)
                                                  #1  0x00007f632138a2e0 g_log_default_handler (libglib-2.0.so.0 + 0x652e0)
                                                  #2  0x00007f632138a57a g_logv (libglib-2.0.so.0 + 0x6557a)
                                                  #3  0x00007f632138a904 g_log (libglib-2.0.so.0 + 0x65904)
                                                  #4  0x000055b23c112686 n/a (/usr/lib/gnome-session-init-worker + 0x2686)
                                                  #5  0x00007f6321027675 n/a (libc.so.6 + 0x27675)
                                                  #6  0x00007f6321027729 __libc_start_main (libc.so.6 + 0x27729)
                                                  #7  0x000055b23c112c95 n/a (/usr/lib/gnome-session-init-worker + 0x2c95)
                                                  
                                                  Stack trace of thread 842:
                                                  #0  0x00007f632111876d syscall (libc.so.6 + 0x11876d)
                                                  #1  0x00007f63213b47ee g_cond_wait (libglib-2.0.so.0 + 0x8f7ee)
                                                  #2  0x00007f632134b1cd n/a (libglib-2.0.so.0 + 0x261cd)
                                                  #3  0x00007f63213bd447 n/a (libglib-2.0.so.0 + 0x98447)
                                                  #4  0x00007f63213bc87c n/a (libglib-2.0.so.0 + 0x9787c)
                                                  #5  0x00007f63210969cb n/a (libc.so.6 + 0x969cb)
                                                  #6  0x00007f632111aa0c n/a (libc.so.6 + 0x11aa0c)
                                                  
                                                  Stack trace of thread 844:
                                                  #0  0x00007f632109f042 n/a (libc.so.6 + 0x9f042)
                                                  #1  0x00007f63210931ac n/a (libc.so.6 + 0x931ac)
                                                  #2  0x00007f63210931f4 n/a (libc.so.6 + 0x931f4)
                                                  #3  0x00007f632110da36 ppoll (libc.so.6 + 0x10da36)
                                                  #4  0x00007f6321385744 n/a (libglib-2.0.so.0 + 0x60744)
                                                  #5  0x00007f63213859d7 g_main_loop_run (libglib-2.0.so.0 + 0x609d7)
                                                  #6  0x00007f63215f6264 n/a (libgio-2.0.so.0 + 0x11a264)
                                                  #7  0x00007f63213bc87c n/a (libglib-2.0.so.0 + 0x9787c)
                                                  #8  0x00007f63210969cb n/a (libc.so.6 + 0x969cb)
                                                  #9  0x00007f632111aa0c n/a (libc.so.6 + 0x11aa0c)
                                                  
                                                  Stack trace of thread 843:
                                                  #0  0x00007f632109f042 n/a (libc.so.6 + 0x9f042)
                                                  #1  0x00007f63210931ac n/a (libc.so.6 + 0x931ac)
                                                  #2  0x00007f63210931f4 n/a (libc.so.6 + 0x931f4)
                                                  #3  0x00007f632110da36 ppoll (libc.so.6 + 0x10da36)
                                                  #4  0x00007f6321385744 n/a (libglib-2.0.so.0 + 0x60744)
                                                  #5  0x00007f6321385825 g_main_context_iteration (libglib-2.0.so.0 + 0x60825)
                                                  #6  0x00007f6321385872 n/a (libglib-2.0.so.0 + 0x60872)
                                                  #7  0x00007f63213bc87c n/a (libglib-2.0.so.0 + 0x9787c)
                                                  #8  0x00007f63210969cb n/a (libc.so.6 + 0x969cb)
                                                  #9  0x00007f632111aa0c n/a (libc.so.6 + 0x11aa0c)
                                                  ELF object binary architecture: AMD x86-64

I guess it is in the pam configuration?

It could not be the missing gdm-greeter user?

$ groups gdm
gdm : gdm

$ groups gdm-greeter
groups: ‘gdm-greeter’: no such user

drslmr

Member

Registered: 2011-05-14

Posts: 58

Re: gdm broken after update

Now I found an issue in my /et/pam.d/system-auth

I had the following line:

account     [default=bad success=ok] pam_sss.so forward_pass

and now, for testing,  replaced the bad with ignore:

account     [default=ignore success=ok] pam_sss.so forward_pass

This lets the system succeed in starting gdm.

Not sure if "ignore" is a good idea. But that would be a different topic.
Thanks seth for the quick and great support. And sorry, it was my mistake.

ManuVice

Member

Registered: 2023-05-03

Posts: 4

Re: gdm broken after update

nsswitch.conf

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files systemd
gshadow: files systemd

publickey: files

hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

Last edited by ManuVice (2025-09-30 14:12:31)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,050

Re: gdm broken after update

@drslmr \o/ but you fixed it all by yourself
https://man.archlinux.org/man/pam_sss.8#RETURN_VALUES
Looks like PAM_IGNORE is only issued for unknown users what should™ be ok (as long as this doesn't result in automatic acceptance but is caught by other modules)

@ManuVice that's the default nsswitch, do you have a problem w/ GDM?
Journal?

---

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

ManuVice

Member

Registered: 2023-05-03

Posts: 4

Re: gdm broken after update

nope all is working fine here

gkun

Member

Registered: 2016-06-11

Posts: 98

Re: gdm broken after update

Hi everyone, I still have the problem after trying every workaround:

ott 02 13:31:04 Giankun-PC gnome-session-i[1115]: Starting GNOME session target: gnome-session-x11@gnome-login.target
ott 02 13:31:04 Giankun-PC gnome-session-i[1115]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-session-x11@gnome-login.target not found.
ott 02 13:31:04 Giankun-PC kernel: traps: gnome-session-i[1115] trap int3 ip:7fcc5dfc6b8c sp:7fffe2ee5ae0 error:0 in libglib-2.0.so.0.8600.0[64b8c,7fcc5df80000+a7000]
ott 02 13:31:04 Giankun-PC systemd-coredump[1123]: Process 1115 (gnome-session-i) of user 60578 terminated abnormally with signal 5/TRAP, processing...
ott 02 13:31:04 Giankun-PC systemd[1]: Created slice Slice /system/systemd-coredump.
ott 02 13:31:04 Giankun-PC systemd[1]: Started Process Core Dump (PID 1123/UID 0).
ott 02 13:31:04 Giankun-PC systemd-coredump[1124]: Process 1115 (gnome-session-i) of user 60578 dumped core.

My /etc/nsswitch.conf is:

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files systemd
gshadow: files systemd

publickey: files

hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns
networks: files

protocols: files
services: files
ethers: files
rpc: files
netgroup: files

and just to make sure I also added

 gdm-greeter:!*:20224:::::: 

to my /etc/shadow (it did not work with or without it)... short of switching to lightdm, what should I do?

gkun

Member

Registered: 2016-06-11

Posts: 98

Re: gdm broken after update

I tried to enable lightdm, but:

ott 02 14:50:14 Giankun-PC dbus-broker-launch[1631]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
ott 02 14:50:14 Giankun-PC systemd[1611]: Started D-Bus User Message Bus.
ott 02 14:50:14 Giankun-PC dbus-broker-launch[1631]: Ready
ott 02 14:50:14 Giankun-PC lightdm[1524]: gkr-pam: unlocked login keyring
ott 02 14:50:14 Giankun-PC kernel: traps: gnome-session-i[1633] trap int3 ip:7f17d56d5b8c sp:7ffde0950970 error:0 in libglib-2.0.so.0.8600.0[64b8c,7f17d568f000+a7000]
ott 02 14:50:14 Giankun-PC systemd-coredump[1658]: Process 1633 (gnome-session-i) of user 1000 terminated abnormally with signal 5/TRAP, processing...
ott 02 14:50:14 Giankun-PC systemd[1]: Started Process Core Dump (PID 1658/UID 0).
ott 02 14:50:14 Giankun-PC systemd-coredump[1659]: Process 1633 (gnome-session-i) of user 1000 dumped core.
                                                   
                                                   Stack trace of thread 1633:
                                                   #0  0x00007f17d56d5b8c g_log_structured_array (libglib-2.0.so.0 + 0x64b8c)
                                                   #1  0x00007f17d56d62e0 g_log_default_handler (libglib-2.0.so.0 + 0x652e0)
                                                   #2  0x00007f17d56d657a g_logv (libglib-2.0.so.0 + 0x6557a)
                                                   #3  0x00007f17d56d6904 g_log (libglib-2.0.so.0 + 0x65904)
                                                   #4  0x0000557135c38686 n/a (/usr/lib/gnome-session-init-worker + 0x2686)
                                                   #5  0x00007f17d5427675 n/a (libc.so.6 + 0x27675)
                                                   #6  0x00007f17d5427729 __libc_start_main (libc.so.6 + 0x27729)
                                                   #7  0x0000557135c38c95 n/a (/usr/lib/gnome-session-init-worker + 0x2c95)
                                                   
                                                   Stack trace of thread 1655:
                                                   #0  0x00007f17d551876d syscall (libc.so.6 + 0x11876d)
                                                   #1  0x00007f17d57007ee g_cond_wait (libglib-2.0.so.0 + 0x8f7ee)
                                                   #2  0x00007f17d56971cd n/a (libglib-2.0.so.0 + 0x261cd)
                                                   #3  0x00007f17d5709447 n/a (libglib-2.0.so.0 + 0x98447)
                                                   #4  0x00007f17d570887c n/a (libglib-2.0.so.0 + 0x9787c)
                                                   #5  0x00007f17d54969cb n/a (libc.so.6 + 0x969cb)
                                                   #6  0x00007f17d551aa0c n/a (libc.so.6 + 0x11aa0c)
                                                   
                                                   Stack trace of thread 1657:
                                                   #0  0x00007f17d549f042 n/a (libc.so.6 + 0x9f042)
                                                   #1  0x00007f17d54931ac n/a (libc.so.6 + 0x931ac)
                                                   #2  0x00007f17d54931f4 n/a (libc.so.6 + 0x931f4)
                                                   #3  0x00007f17d550da36 ppoll (libc.so.6 + 0x10da36)
                                                   #4  0x00007f17d56d1744 n/a (libglib-2.0.so.0 + 0x60744)
                                                   #5  0x00007f17d56d19d7 g_main_loop_run (libglib-2.0.so.0 + 0x609d7)
                                                   #6  0x00007f17d5942264 n/a (libgio-2.0.so.0 + 0x11a264)
                                                   #7  0x00007f17d570887c n/a (libglib-2.0.so.0 + 0x9787c)
                                                   #8  0x00007f17d54969cb n/a (libc.so.6 + 0x969cb)

something is wrong

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,050

Re: gdm broken after update

ott 02 13:31:04 Giankun-PC gnome-session-i[1115]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-session-x11@gnome-login.target not found.

You're trying to start an X11 session here, did you configure https://wiki.archlinux.org/title/GDM#Use_Xorg_backend ?
If not and certainly because of the second post, please post your complete system journal for the boot:

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

---

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

gkun

Member

Registered: 2016-06-11

Posts: 98

Re: gdm broken after update

ott 02 13:31:04 Giankun-PC gnome-session-i[1115]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-session-x11@gnome-login.target not found.

You're trying to start an X11 session here, did you configure https://wiki.archlinux.org/title/GDM#Use_Xorg_backend ?
If not and certainly because of the second post, please post your complete system journal for the boot:

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

Hi, yes in the boot which returned the error the /etc/gdm/custom.conf file was:

# GDM configuration storage

[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

I posted the journal for the boot at: http://0x0.st/KMj4.txt

Gian Andrea