gdm broken after update

gkun · 2025-10-02 14:25:22

By the way, I am using wayland which is ok for most things, but one app I was using (docky) does not work and seems to be unusable on wayland... other that for that I might just use wayland as it is not so bad now.

seth · 2025-10-02 14:32:29

yes in the boot which returned the error

That will not work, remove that config or comment the "WaylandEnable=false" entry.
The journal doesn't show lightdm at all - still same GDM problem.

gkun · 2025-10-02 14:39:27

seth wrote:

yes in the boot which returned the error
That will not work, remove that config or comment the "WaylandEnable=false" entry.
The journal doesn't show lightdm at all - still same GDM problem.

Wait I posted a boot with GDM (the main goal was to start an xorg session with GDM for which the workarounds don't seem to work), of course when I used Xorg on gdm I had set the entry as WaylandEnable=false. I will post a complete boot with lightdm later.

seth · 2025-10-02 14:46:39

Also test GDM w/o "WaylandEnable=false"

gkun · 2025-10-02 14:47:44

I disabled gdm, enabled lightdm, commented the WaylandEnable=false entry, and when I tried to login on xorg it crashed:

http://0x0.st/KMe8.txt

Last edited by gkun (2025-10-02 14:48:37)

Scimmia · 2025-10-02 14:54:21

gkunand wrote:

when I tried to login on xorg

It's been said over and over, GNOME doesn't support xorg anymore. Stop trying to use it. Start reading the thread you're posting in.

gkun · 2025-10-02 18:03:45

Scimmia wrote:

gkunand wrote:
when I tried to login on xorg
It's been said over and over, GNOME doesn't support xorg anymore. Stop trying to use it. Start reading the thread you're posting in.

Sorry I did not read carefully two pages of this thread... I understand now, my choice is wayland or another de.

drslmr · 2025-10-21 17:46:40

I'm confused, sorry.

On a different laptop, I had the problem with crashing gnome-shell again, after applying the fixes found in this topic.

It happened for a certain user. and not for another one.

I did some kind of bisecting the about 90 entries (files and directories) in the ~/.config and found that the systemd seems to be the culprit. In the .config of the "bad" user it looks like this:

# inside ~/.config:

find systemd/
systemd/
systemd/user
systemd/user/default.target

cat systemd/user/default.target
[Unit]
AllowIsolate=yes

If I remove the directory systemd from ~/.config gnome-shell does not crash anymore.

Does this make sense?

For completion:
In journalctl, the gnome-shell crash did look like this:

Okt 21 19:16:00 host systemd[1]: Started User Manager for UID 1000.
Okt 21 19:16:00 host systemd[1]: Started Session 3 of User myuser.
Okt 21 19:16:01 host kernel: rfkill: input handler enabled
Okt 21 19:16:01 host systemd[1267]: Reached target Sound Card.
Okt 21 19:16:01 host systemd[650]: Reached target Sound Card.
Okt 21 19:16:01 host /usr/lib/gdm-wayland-session[1350]: dbus-daemon[1350]: [session uid=1000 pid=1350 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=1334 comm="/usr/lib/gdm-wayland-session /usr/bin/gnome-sessio")
Okt 21 19:16:01 host /usr/lib/gdm-wayland-session[1350]: dbus-daemon[1350]: [session uid=1000 pid=1350 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Okt 21 19:16:02 host gnome-session-i[1355]: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Okt 21 19:16:02 host gnome-session-i[1355]: Failed to check if unit gnome-session-wayland@gnome.target is active: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Okt 21 19:16:02 host gnome-session-i[1355]: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Okt 21 19:16:02 host gnome-session-i[1355]: Starting GNOME session target: gnome-session-wayland@gnome.target
Okt 21 19:16:02 host gnome-session-i[1355]: Failed to start unit gnome-session-wayland@gnome.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Okt 21 19:16:02 host kernel: traps: gnome-session-i[1355] trap int3 ip:7fb72a432b8c sp:7ffd9754a840 error:0 in libglib-2.0.so.0.8600.0[64b8c,7fb72a3ec000+a7000]
Okt 21 19:16:02 host systemd-coredump[1374]: Process 1355 (gnome-session-i) of user 1000 terminated abnormally with signal 5/TRAP, processing...
Okt 21 19:16:02 host systemd[1]: Created slice Slice /system/systemd-coredump.
Okt 21 19:16:02 host systemd[1]: Started Process Core Dump (PID 1374/UID 0).
Okt 21 19:16:03 host sshd-session[1274]: Failed password for invalid user testuser from 196.251.88.103 port 37884 ssh2
Okt 21 19:16:03 host sshd-session[1274]: Connection closed by invalid user testuser 196.251.88.103 port 37884 [preauth]
Okt 21 19:16:03 host systemd-coredump[1375]: Process 1355 (gnome-session-i) of user 1000 dumped core.
                                               
                                               Stack trace of thread 1355:
                                               #0  0x00007fb72a432b8c g_log_structured_array (libglib-2.0.so.0 + 0x64b8c)
                                               #1  0x00007fb72a4332e0 g_log_default_handler (libglib-2.0.so.0 + 0x652e0)
                                               #2  0x00007fb72a43357a g_logv (libglib-2.0.so.0 + 0x6557a)
                                               #3  0x00007fb72a433904 g_log (libglib-2.0.so.0 + 0x65904)
                                               #4  0x0000561763026686 n/a (/usr/lib/gnome-session-init-worker + 0x2686)
                                               #5  0x00007fb72a027675 n/a (libc.so.6 + 0x27675)
                                               #6  0x00007fb72a027729 __libc_start_main (libc.so.6 + 0x27729)
                                               #7  0x0000561763026c95 n/a (/usr/lib/gnome-session-init-worker + 0x2c95)

seth · 2025-10-21 19:48:21

https://bbs.archlinux.org/viewtopic.php … 3#p2268463 - but that doesn't sound like GDM is involved?

drslmr · 2025-10-21 20:19:29

Yes, it is not realy GDM. So wrong topic.

Arch Linux

#126 2025-10-02 14:25:22

Re: gdm broken after update

#127 2025-10-02 14:32:29

Re: gdm broken after update

#128 2025-10-02 14:39:27

Re: gdm broken after update

#129 2025-10-02 14:46:39

Re: gdm broken after update

#130 2025-10-02 14:47:44

Re: gdm broken after update

#131 2025-10-02 14:54:21

Re: gdm broken after update

#132 2025-10-02 18:03:45

Re: gdm broken after update

#133 2025-10-21 17:46:40

Re: gdm broken after update

#134 2025-10-21 19:48:21

Re: gdm broken after update

#135 2025-10-21 20:19:29

Re: gdm broken after update

Board footer