You are not logged in.
- Topics: Active | Unanswered
#1 2025-09-24 09:04:34
- Cpt_Liam
- Member
- Registered: 2025-09-24
- Posts: 2
[SOLVED] GDM breaks with gnome-session-49
Hi all,
after updating to gnome-session-49, GDM segfaults on startup:
journalctl -u gdm
...
<date> Gdm: GdmSession: no session desktop files installed, aborting...
Process 1596 (gdm) of user 0 dumped core.
#0 ... g_logv (libglib-2.0.so.0)
...(forgive me for not retyping the whole thing, my desktop doesn't work, I can't copy paste from there...)
After digging a little, I noticed that /usr/share/wayland-sessions/ exists, but /usr/share/xsessions does not.
I tried rolling back by installing gnome-session-48.0-1 and gnome-mimeapps-0.1-1 from cache (the latter is a dependency). This restores the /usr/share/xsessions directory but starting GDM now simply results in a black screen with absolutely no visual feedback. No logs in journalctl, either, except "Starting GNOME Display Manager..." and "Started GNOME Display Manager.".
There were dozens of other updates and other gnome related things, I don't know where to start.
Update: I tried rolling back more packages (gnome-session-48.0, gnome-mimeapps-0.1, gnome-shell-1:48.5, mutter-48.5), but same result (black screen, logs simply say "Starting GNOME Display Manager..." and "Started GNOME Display Manager.")
Please help me restore a working system 
Last edited by Cpt_Liam (2025-09-24 15:33:03)
Offline
#2 2025-09-24 10:48:05
- gatherer
- Member
- Registered: 2025-09-24
- Posts: 1
Re: [SOLVED] GDM breaks with gnome-session-49
This is likely due to Gnome 49 dropping support for X11.
Offline
#3 2025-09-24 11:00:00
- lavjamanxd
- Member
- Registered: 2018-03-30
- Posts: 4
Re: [SOLVED] GDM breaks with gnome-session-49
This is likely due to Gnome 49 dropping support for X11.
I am getting similar results since the update from yesterday, i am not using X11 at all, my system was running wayland only since the install.
szept 23 19:03:17 sindragosa systemd[1]: Starting GNOME Display Manager...
szept 23 19:03:17 sindragosa systemd[1]: Started GNOME Display Manager.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2813 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2813 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2857 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2857 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2901 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2901 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2947 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2947 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2991 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -2991 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -3035 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmDisplay: Session never registered, failing
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: Child process -3035 was already dead.
szept 23 19:03:17 sindragosa gdm[2794]: Gdm: GdmSession: no session desktop files installed, abortin>
szept 23 19:03:17 sindragosa systemd-coredump[3080]: [?] Process 2794 (gdm) of user 0 dumped core.
Stack trace of thread 2794:
#0 0x00007f8478d5b319 g_logv (libglib-2.0.so.0>
#1 0x00007f8478d5b59c g_log (libglib-2.0.so.0 >
#2 0x0000556e37fa5cfe n/a (/usr/bin/gdm + 0x39>
#3 0x0000556e37fae1f5 n/a (/usr/bin/gdm + 0x42>
#4 0x00007f847891643e n/a (libffi.so.8 + 0x843>
#5 0x00007f8478912a5d n/a (libffi.so.8 + 0x4a5>
#6 0x00007f84789157ce ffi_call (libffi.so.8 + >
#7 0x00007f8478e7d988 g_cclosure_marshal_gener>
#8 0x00007f8478ea2d55 n/a (libgobject-2.0.so.0>
#9 0x00007f8478e90c49 g_signal_emit_valist (li>
#10 0x00007f8478e9f23c g_signal_emit (libgobjec>
#11 0x0000556e37fab5b4 n/a (/usr/bin/gdm + 0x3f>
#12 0x00007f8478ba6d15 n/a (libgio-2.0.so.0 + 0>
#13 0x00007f8478c22b15 n/a (libgio-2.0.so.0 + 0>
#14 0x00007f8478ba6d15 n/a (libgio-2.0.so.0 + 0>
#15 0x00007f8478c1aa83 n/a (libgio-2.0.so.0 + 0>
#16 0x00007f8478b9ddf8 n/a (libgio-2.0.so.0 + 0>
#17 0x00007f8478d4d9a9 n/a (libglib-2.0.so.0 + >
#18 0x00007f8478d4edf8 n/a (libglib-2.0.so.0 + >
#19 0x00007f8478d4f0ef g_main_loop_run (libglib>
#20 0x0000556e37f79758 n/a (/usr/bin/gdm + 0xd7>
#21 0x00007f8478627b0b n/a (libc.so.6 + 0x27b0b)
#22 0x00007f8478627bbb __libc_start_main (libc.>
#23 0x0000556e37f79b05 n/a (/usr/bin/gdm + 0xdb>
Stack trace of thread 2796:
#0 0x00007f84786b2e42 n/a (libc.so.6 + 0xb2e42)
#1 0x00007f84786a64df n/a (libc.so.6 + 0xa64df)
#2 0x00007f8478733c43 ppoll (libc.so.6 + 0x133>
#3 0x00007f8478d4ee50 n/a (libglib-2.0.so.0 + >
#4 0x00007f8478d4ef32 g_main_context_iteration>
#5 0x00007f8478d4ef82 n/a (libglib-2.0.so.0 + >
#6 0x00007f8478d951d9 n/a (libglib-2.0.so.0 + >
#7 0x00007f84786aa4f8 n/a (libc.so.6 + 0xaa4f8)
#8 0x00007f8478740fdc n/a (libc.so.6 + 0x140fd>
Stack trace of thread 2803:
#0 0x00007f847873e45d syscall (libc.so.6 + 0x1>
#1 0x00007f8478d8b317 g_cond_wait_until (libgl>
#2 0x00007f8478d0b93e g_async_queue_timeout_po>
#3 0x00007f8478d95c4b n/a (libglib-2.0.so.0 + >
#4 0x00007f8478d951d9 n/a (libglib-2.0.so.0 + >
#5 0x00007f84786aa4f8 n/a (libc.so.6 + 0xaa4f8)
#6 0x00007f8478740fdc n/a (libc.so.6 + 0x140fd>
Stack trace of thread 2798:
#0 0x00007f84786b2e42 n/a (libc.so.6 + 0xb2e42)
#1 0x00007f84786a64df n/a (libc.so.6 + 0xa64df)
#2 0x00007f84787410c1 epoll_wait (libc.so.6 + >
#3 0x00007f8478f18430 sd_event_wait (libsystem>
#4 0x00007f8478f19844 sd_event_run (libsystemd>
#5 0x00007f8478f19990 sd_event_loop (libsystem>
#6 0x0000556e37f8a520 n/a (/usr/bin/gdm + 0x1e>
#7 0x00007f8478d951d9 n/a (libglib-2.0.so.0 + >
#8 0x00007f84786aa4f8 n/a (libc.so.6 + 0xaa4f8)
#9 0x00007f8478740fdc n/a (libc.so.6 + 0x140fd>
Stack trace of thread 2797:
#0 0x00007f84786b2e42 n/a (libc.so.6 + 0xb2e42)
#1 0x00007f84786a64df n/a (libc.so.6 + 0xa64df)
#2 0x00007f8478733c43 ppoll (libc.so.6 + 0x133>
#3 0x00007f8478d4ee50 n/a (libglib-2.0.so.0 + >
#4 0x00007f8478d4f0ef g_main_loop_run (libglib>
#5 0x00007f8478c1ba0c n/a (libgio-2.0.so.0 + 0>
#6 0x00007f8478d951d9 n/a (libglib-2.0.so.0 + >
#7 0x00007f84786aa4f8 n/a (libc.so.6 + 0xaa4f8)
#8 0x00007f8478740fdc n/a (libc.so.6 + 0x140fd>
Stack trace of thread 2795:
#0 0x00007f847873e45d syscall (libc.so.6 + 0x1>
#1 0x00007f8478d8a685 g_cond_wait (libglib-2.0>
#2 0x00007f8478d0b78d g_async_queue_pop_unlock>
#3 0x00007f8478d95797 n/a (libglib-2.0.so.0 + >
#4 0x00007f8478d951d9 n/a (libglib-2.0.so.0 + >
#5 0x00007f84786aa4f8 n/a (libc.so.6 + 0xaa4f8)
#6 0x00007f8478740fdc n/a (libc.so.6 + 0x140fd>
ELF object binary architecture: AMD x86-64
szept 23 19:03:17 sindragosa systemd[1]: gdm.service: Main process exited, code=dumped, status=5/TRAP
szept 23 19:03:17 sindragosa systemd[1]: gdm.service: Failed with result 'core-dump'.
szept 23 19:03:17 sindragosa systemd[1]: gdm.service: Triggering OnFailure= dependencies.
szept 23 19:03:18 sindragosa systemd[1]: gdm.service: Scheduled restart job, restart counter is at 5.
szept 23 19:03:18 sindragosa systemd[1]: gdm.service: Start request repeated too quickly.
szept 23 19:03:18 sindragosa systemd[1]: gdm.service: Failed with result 'core-dump'.
szept 23 19:03:18 sindragosa systemd[1]: Failed to start GNOME Display Manager.
szept 23 19:03:18 sindragosa systemd[1]: gdm.service: Triggering OnFailure= dependencies.I tried some workarounds from the other threads and from reddit and all i was able to get is a blinking screen and no signals on my monitor.
Without any config changes it just shows a single "_" character at a black screen cant switch tty, sometimes ctrl+alt+del reboots the pc but usually i can only restart it by pressing the power button.
Also gnome itself can't start for some reason, i tried to run it from terminal then tried to install SDDM and run it from there without any luck.
Tried to downgrade kernel, systemd, gdm, gnome-shell etc to previous versions but still getting similar results. I'm a bit lost at this point what can try.
Last edited by lavjamanxd (2025-09-24 13:20:57)
Offline
#4 2025-09-24 13:01:00
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 68,325
Re: [SOLVED] GDM breaks with gnome-session-49
Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
See https://bbs.archlinux.org/viewtopic.php?id=308372&p=3 - there was a change in GDMs pam module and that's sensitive to stale nss (now "mis"-)configurations.
@Cpt_Liam, even if you'd manage to restore X11 function for now (the v49 situation is messy) that's not a sustainable strategy - if you want to continue to use gnome/GDM, switch to wayland.
If you can or don't want to use wayland, you'll have to shop around for a new desktop.
Online
#5 2025-09-24 13:41:54
- lavjamanxd
- Member
- Registered: 2018-03-30
- Posts: 4
Re: [SOLVED] GDM breaks with gnome-session-49
Sorry, fixed my post.
I checked that file and my install is fresher than the others, so i did not have an nsswitch.conf.pacnew file.
Looking into that file has the correct line what others saying that it solved the problem for them.
shadow: files systemdOffline
#6 2025-09-24 14:29:29
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 68,325
Re: [SOLVED] GDM breaks with gnome-session-49
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stOnline
#7 2025-09-24 14:47:50
- lavjamanxd
- Member
- Registered: 2018-03-30
- Posts: 4
Re: [SOLVED] GDM breaks with gnome-session-49
I was only able to get a journalctl -b-1 because as soon as gdm or gnome-shell starts up the pc just locks up and the system only reacts to the power button.
Last edited by lavjamanxd (2025-09-24 14:48:09)
Offline
#8 2025-09-24 14:56:26
- Cpt_Liam
- Member
- Registered: 2025-09-24
- Posts: 2
Re: [SOLVED] GDM breaks with gnome-session-49
gatherer's post solved it for me. Sending this from my fixed system
I had a file /etc/gdm/custom.conf with
[daemon]
WaylandEnable=falselying around. There was nothing else in the file and I deleted it. Oddly enough, restarting gdm just froze everything, but a reboot fixed my system.
Edit: I do not remember why I had this line. The file was last modified in 2021. The most likely scenario is that something Wayland didn't work for me back then and that I completely forgot about it.
Big thanks to everyone! And good luck to everyone who's still struggling.
Last edited by Cpt_Liam (2025-09-24 15:05:31)
Offline
#9 2025-09-24 15:05:34
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 68,325
Re: [SOLVED] GDM breaks with gnome-session-49
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
@lavjamanxd your situation is different from pretty much everyone elses
szept 24 16:33:59 sindragosa systemd[1]: Starting GNOME Remote Desktop...
szept 24 16:34:00 sindragosa gnome-remote-desktop-daemon[742]: Init TPM credentials failed because Failed to initialize transmission interface context: tcti:IO failure, using GKeyFile as fallback
szept 24 16:34:00 sindragosa systemd[1]: Started GNOME Remote Desktop.
szept 24 16:34:06 sindragosa systemd[990]: Listening on GNOME Keyring daemon.
szept 24 16:34:06 sindragosa systemd[990]: Started GNOME Keyring daemon.
szept 24 16:34:06 sindragosa gnome-keyring-daemon[1003]: gnome-keyring-daemon: no process capabilities, insecure memory might get used
szept 24 16:34:06 sindragosa gnome-keyring-daemon[1003]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
szept 24 16:34:12 sindragosa systemd[1]: Starting GNOME Display Manager...
szept 24 16:34:12 sindragosa systemd[1]: Started GNOME Display Manager.
szept 24 16:34:13 sindragosa systemd[1]: Starting Configure GNOME Remote Desktop...
szept 24 16:34:13 sindragosa gnome-remote-desktop-configuration-daemon[1435]: Init TPM credentials failed because Failed to initialize transmission interface context: tcti:IO failure, using GKeyFile as fallback
szept 24 16:34:13 sindragosa systemd[1]: Started Configure GNOME Remote Desktop.
szept 24 16:34:13 sindragosa gnome-remote-desktop-daemon[742]: RDP server started
szept 24 16:34:13 sindragosa systemd[1446]: Listening on GNOME Keyring daemon.
szept 24 16:34:13 sindragosa gnome-session-i[1468]: Starting GNOME session target: gnome-session-wayland@gnome-login.target
szept 24 16:34:13 sindragosa systemd[1446]: Created slice Slice /app/gnome-session-manager.
szept 24 16:34:13 sindragosa systemd[1446]: Reached target GNOME Wayland Session.
szept 24 16:34:13 sindragosa systemd[1446]: Reached target GNOME Shell.
szept 24 16:34:13 sindragosa systemd[1446]: Starting Monitor Session leader for GNOME Session...
szept 24 16:34:13 sindragosa systemd[1446]: Started Monitor Session leader for GNOME Session.
szept 24 16:34:13 sindragosa systemd[1446]: Reached target Tasks to be run before GNOME Session starts.
szept 24 16:34:13 sindragosa systemd[1446]: Starting GNOME Session Manager (session: gnome-login)...
szept 24 16:34:13 sindragosa systemd[1446]: Started GNOME Session Manager (session: gnome-login).
szept 24 16:34:13 sindragosa systemd[1446]: Reached target GNOME Session Manager is ready.
szept 24 16:34:13 sindragosa systemd[1446]: Starting GNOME Shell on Wayland...
szept 24 16:34:13 sindragosa gnome-shell[1484]: Running GNOME Shell (using mutter 49.0) as a Wayland display server
szept 24 16:34:13 sindragosa gnome-shell[1484]: Thread 'KMS thread' will be using high priority scheduling
szept 24 16:34:13 sindragosa gnome-shell[1484]: Device '/dev/dri/card1' prefers shadow buffer
szept 24 16:34:13 sindragosa gnome-shell[1484]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
szept 24 16:34:13 sindragosa gnome-shell[1484]: Device '/dev/dri/card0' prefers shadow buffer
szept 24 16:34:13 sindragosa gnome-shell[1484]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
szept 24 16:34:13 sindragosa gnome-shell[1484]: Created gbm renderer for '/dev/dri/card1'
szept 24 16:34:13 sindragosa gnome-shell[1484]: Created gbm renderer for '/dev/dri/card0'
szept 24 16:34:13 sindragosa gnome-shell[1484]: Boot VGA GPU /dev/dri/card1 selected as primary
szept 24 16:34:13 sindragosa gnome-shell[1484]: Obtained a high priority EGL context
szept 24 16:34:13 sindragosa gnome-shell[1484]: cannot register existing type 'GIRepository'
szept 24 16:34:13 sindragosa gnome-shell[1484]: g_once_init_leave_pointer: assertion 'result != 0' failed
szept 24 16:34:13 sindragosa gnome-shell[1484]: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
szept 24 16:34:13 sindragosa gnome-shell[1484]: g_object_add_weak_pointer: assertion 'G_IS_OBJECT (object)' failed
szept 24 16:34:13 sindragosa gnome-shell[1484]: g_once_init_leave: assertion 'result != 0' failed
szept 24 16:34:13 sindragosa gnome-shell[1484]: g_object_ref: assertion 'G_IS_OBJECT (object)' failedDo you have any relevant AUR packages flying around?
Do you require https://archlinux.org/packages/extra/x8 … e-desktop/ ? What if you remove/disable that?
Online
#10 2025-09-24 15:20:02
- lavjamanxd
- Member
- Registered: 2018-03-30
- Posts: 4
Re: [SOLVED] GDM breaks with gnome-session-49
Oh actually i had something...
So i tried to disable gnome-remote-desktop -> no luck same as before.
But i noticed that i had a weird gjs-nohammer package from AUR, so after reinstalling the normal gjs from arch repository, gdm and gnome starts successfully.
Looks like my case was different from the others in the end.
Thank you @seth for pointing out that i might have something fishy installed from AUR.
Last edited by lavjamanxd (2025-09-24 15:20:28)
Offline