You are not logged in.

Pages: 1 2

#1 2023-08-12 01:22:06

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

[SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Restarting GNOME with Alt-f2 + r with systemd 253 works fine, but ever since upgrading to systemd 254, Alt-f2 + r says that "something has gone wrong", the system can't recover, and prompts me to logout.

Here are what appear to be the relevant logs:

Aug 11 21:26:56 poxter gnome-character[4335]: JS LOG: Characters Application exiting
Aug 11 21:26:57 poxter kernel: gnome-shell[3668]: segfault at 0 ip 00007f22092fef37 sp 00007ffe70945d80 error 4 in libX11.so.6.4.0[7f22092d9000+8b000] likely on CPU 4 (core 4, socket 0)
Aug 11 21:26:57 poxter gnome-disks[4726]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Aug 11 21:26:57 poxter gnome-disks[4726]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Aug 11 21:26:57 poxter systemd[574]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=11/SEGV
Aug 11 21:26:57 poxter systemd[574]: org.gnome.Shell@x11.service: Failed with result 'core-dump'.
Aug 11 21:26:57 poxter systemd[574]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
Aug 11 21:26:57 poxter systemd[574]: org.gnome.Shell@x11.service: Consumed 2.956s CPU time.
Aug 11 21:26:57 poxter systemd[574]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
Aug 11 21:26:57 poxter systemd[574]: org.gnome.Shell-disable-extensions.service: multiple trigger source candidates for exit status propagation (org.gnome.Shell@x11.service, org.gnome.Shell@wayland.service), skipping.
Aug 11 21:26:57 poxter gnome-shell[4792]: Running GNOME Shell (using mutter 44.3) as a X11 window and compositing manager
Aug 11 21:26:57 poxter gsd-media-keys[3918]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell”
Aug 11 21:26:57 poxter polkitd[585]: Registered Authentication Agent for unix-session:5 (system bus name :1.155 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Aug 11 21:26:57 poxter gnome-shell[4792]: Telepathy is not available, chat integration will be disabled.
Aug 11 21:26:57 poxter gnome-shell[4792]: Failed to create file /run/user/1000/gnome-shell-disable-extensions: Error opening file “/run/user/1000/gnome-shell-disable-extensions”: File exists
Aug 11 21:26:57 poxter dbus-daemon[3607]: [session uid=1000 pid=3607] Activating service name='org.gnome.Shell.Notifications' requested by ':1.99' (uid=1000 pid=4792 comm="/usr/bin/gnome-shell")

Last edited by GeneralPoxter (2023-09-18 08:47:57)

Offline

#2 2023-08-12 06:31:28

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

How about you also post the "irrelevant" part of the logs? Gnome seems to have crashed multiple times in a row by the time what you deemed relevant.
Therefore also https://wiki.archlinux.org/title/Core_d … _core_dump

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

Offline

#3 2023-08-12 06:56:45

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

I tried it again, so here are all the logs containing "gnome" leading up to the segfault until the crash notification appeared on my screen:

Aug 12 02:45:42 poxter gnome-software[1103]: Only 5 apps for curated list, hiding
Aug 12 02:45:45 poxter kernel: gnome-shell[789]: segfault at 0 ip 00007f7708042f37 sp 00007fff6ef2a490 error 4 in libX11.so.6.4.0[7f770801d000+8b000] likely on CPU 3 (core 3, socket 0)
Aug 12 02:45:45 poxter gnome-disks[1837]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Aug 12 02:45:45 poxter gnome-disks[1837]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=11/SEGV
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Failed with result 'core-dump'.
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Consumed 3.442s CPU time.
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
Aug 12 02:45:46 poxter systemd[538]: org.gnome.Shell-disable-extensions.service: multiple trigger source candidates for exit status propagation (org.gnome.Shell@wayland.service, org.gnome.Shell@x11.service), skipping.
Aug 12 02:45:46 poxter gnome-shell[1896]: Running GNOME Shell (using mutter 44.3) as a X11 window and compositing manager
Aug 12 02:45:46 poxter gsd-media-keys[1059]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell”
Aug 12 02:45:46 poxter polkitd[575]: Registered Authentication Agent for unix-session:3 (system bus name :1.88 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Aug 12 02:45:46 poxter gnome-shell[1896]: Telepathy is not available, chat integration will be disabled.
Aug 12 02:45:46 poxter gnome-shell[1896]: Failed to create file /run/user/1000/gnome-shell-disable-extensions: Error opening file “/run/user/1000/gnome-shell-disable-extensions”: File exists
Aug 12 02:45:46 poxter dbus-daemon[728]: [session uid=1000 pid=728] Activating service name='org.gnome.Shell.Notifications' requested by ':1.105' (uid=1000 pid=1896 comm="/usr/bin/gnome-shell")
Aug 12 02:45:46 poxter devilspie.desktop[1093]: Window Title: 'Untitled window'; Application Name: 'gnome-session-failed'; Class: 'Gnome-session-failed'; Geometry: 1920x1200+1920+0
Aug 12 02:45:46 poxter devilspie.desktop[1093]: Window Title: 'Untitled window'; Application Name: 'gnome-session-failed'; Class: 'Gnome-session-failed'; Geometry: 1920x1200+0+0
Aug 12 02:45:46 poxter dbus-daemon[728]: [session uid=1000 pid=728] Successfully activated service 'org.gnome.Shell.Notifications'

Here is the complete journal output of that crash starting from the segfault:

Aug 12 02:45:45 poxter wpa_supplicant[475]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Aug 12 02:45:45 poxter wpa_supplicant[475]: wlan0: SME: Trying to authenticate with b8:f8:53:9c:dc:7a (SSID='jaevfafa' freq=2462 MHz)
Aug 12 02:45:45 poxter kernel: wlan0: authenticate with b8:f8:53:9c:dc:7a
Aug 12 02:45:45 poxter NetworkManager[474]: <info>  [1691822745.8382] device (wlan0): supplicant interface state: scanning -> authenticating
Aug 12 02:45:45 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 1/3)
Aug 12 02:45:45 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 2/3)
Aug 12 02:45:45 poxter kernel: gnome-shell[789]: segfault at 0 ip 00007f7708042f37 sp 00007fff6ef2a490 error 4 in libX11.so.6.4.0[7f770801d000+8b000] likely on CPU 3 (core 3, socket 0)
Aug 12 02:45:45 poxter kernel: Code: 41 54 55 53 48 89 d3 48 83 ec 58 64 48 8b 04 25 28 00 00 00 48 89 44 24 48 48 8b 87 30 0a 00 00 48 8b 97 f8 00 00 00 83 e2 01 <48> 8b 30 48 89 34 24 0f 85 7c 01 00 00 48 8b b7 a8 00 00 00 48 89
Aug 12 02:45:45 poxter polkitd[575]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.37, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Aug 12 02:45:45 poxter gnome-disks[1837]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Aug 12 02:45:45 poxter gnome-disks[1837]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=11/SEGV
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Failed with result 'core-dump'.
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Consumed 3.442s CPU time.
Aug 12 02:45:45 poxter systemd[538]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
Aug 12 02:45:46 poxter systemd[538]: Started GNOME Session Failed lockdown screen (user).
Aug 12 02:45:46 poxter systemd[538]: Reached target GNOME Session Failed.
Aug 12 02:45:46 poxter systemd[538]: org.gnome.Shell-disable-extensions.service: multiple trigger source candidates for exit status propagation (org.gnome.Shell@wayland.service, org.gnome.Shell@x11.service), skipping.
Aug 12 02:45:46 poxter systemd[538]: Started Disable GNOME Shell extensions after failure.
Aug 12 02:45:46 poxter systemd[538]: Starting GNOME Shell on X11...
Aug 12 02:45:46 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 3/3)
Aug 12 02:45:46 poxter gnome-shell[1896]: Running GNOME Shell (using mutter 44.3) as a X11 window and compositing manager
Aug 12 02:45:46 poxter kernel: wlan0: authentication with b8:f8:53:9c:dc:7a timed out
Aug 12 02:45:46 poxter NetworkManager[474]: <info>  [1691822746.1824] device (wlan0): supplicant interface state: authenticating -> disconnected
Aug 12 02:45:46 poxter gsd-media-keys[1059]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell”
Aug 12 02:45:46 poxter mutter-x11-fram[1922]: Theme parser error: gtk.css:5626:3-9: No property named "height"
Aug 12 02:45:46 poxter mutter-x11-fram[1922]: Theme parser error: gtk.css:5626:3-9: No property named "height"
Aug 12 02:45:46 poxter mutter-x11-fram[1922]: Theme parser error: gtk-dark.css:5626:3-9: No property named "height"
Aug 12 02:45:46 poxter polkitd[575]: Registered Authentication Agent for unix-session:3 (system bus name :1.88 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Aug 12 02:45:46 poxter gnome-shell[1896]: Telepathy is not available, chat integration will be disabled.
Aug 12 02:45:46 poxter gnome-shell[1896]: Failed to create file /run/user/1000/gnome-shell-disable-extensions: Error opening file “/run/user/1000/gnome-shell-disable-extensions”: File exists
Aug 12 02:45:46 poxter dbus-daemon[728]: [session uid=1000 pid=728] Activating service name='org.gnome.Shell.Notifications' requested by ':1.105' (uid=1000 pid=1896 comm="/usr/bin/gnome-shell")
Aug 12 02:45:46 poxter devilspie.desktop[1093]: Window Title: 'Untitled window'; Application Name: 'gnome-session-failed'; Class: 'Gnome-session-failed'; Geometry: 1920x1200+1920+0
Aug 12 02:45:46 poxter devilspie.desktop[1093]: Window Title: 'Untitled window'; Application Name: 'gnome-session-failed'; Class: 'Gnome-session-failed'; Geometry: 1920x1200+0+0
Aug 12 02:45:46 poxter dbus-daemon[728]: [session uid=1000 pid=728] Successfully activated service 'org.gnome.Shell.Notifications'
Aug 12 02:45:46 poxter gnome-shell[1896]: Unable to connect to ibus: Could not connect: Connection refused
Aug 12 02:45:46 poxter gnome-shell[1896]: Could not issue 'GetUnit' systemd call
Aug 12 02:45:46 poxter gnome-disks[1837]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Aug 12 02:45:46 poxter systemd[538]: Started GNOME Shell on X11.
Aug 12 02:45:46 poxter gnome-shell[1896]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory)
Aug 12 02:45:46 poxter gnome-shell[1896]: Failed to get METAR data: Error resolving “www.aviationweather.gov”: Name or service not known
Aug 12 02:45:46 poxter gnome-shell[1896]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 12 02:45:46 poxter NetworkManager[474]: <info>  [1691822746.7421] agent-manager: agent[d58586d675d57b22,:1.88/org.gnome.Shell.NetworkAgent/1000]: agent registered
Aug 12 02:45:46 poxter gnome-shell[1896]: Update check failed: Error resolving “extensions.gnome.org”: Name or service not known
Aug 12 02:45:46 poxter gnome-shell[1896]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Aug 12 02:45:46 poxter gnome-shell[1896]: Failed to get met.no forecast data: Error resolving “aa037rv1tsaszxi6o.api.met.no”: Name or service not known
Aug 12 02:45:46 poxter gnome-disks[1837]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Aug 12 02:45:46 poxter gnome-shell[1896]: Property 'libinput Accel Profile Enabled Default' for device 'PixArt HP USB Optical Mouse' returned 3 items, expected 2
Aug 12 02:45:46 poxter gnome-shell[1896]: Property 'libinput Accel Profiles Available' for device 'PixArt HP USB Optical Mouse' returned 3 items, expected 2

I tried coredumpctl list multiple times (even switching to tty immediately after the crash), but for some reason no coredumps are listed and /var/lib/systemd/coredump/ is empty.

The reason why it seems multiple crashes occurred in the original post was because I had repeated the Alt+F2+r crash multiple times before the original log excerpt to try and determine whether my gnome extensions are responsible (I don't think they are).

Last edited by GeneralPoxter (2023-08-12 06:58:47)

Offline

#4 2023-08-12 06:58:24

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Stop randomly grepping around, 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

Offline

#5 2023-08-12 07:00:00

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Done: http://0x0.st/H_IZ.txt

I repeated the Alt-F2-r crash twice in those logs (one at 2:45 and one at 2:46) to try and find the coredumps.

Last edited by GeneralPoxter (2023-08-12 07:03:12)

Offline

#6 2023-08-12 07:42:53

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Aug 12 02:45:29 poxter gnome-shell[789]: Running GNOME Shell (using mutter 44.3) as a X11 window and compositing manager
…
Aug 12 02:45:45 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 1/3)
Aug 12 02:45:45 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 2/3)
Aug 12 02:45:45 poxter kernel: gnome-shell[789]: segfault at 0 ip 00007f7708042f37 sp 00007fff6ef2a490 error 4 in libX11.so.6.4.0[7f770801d000+8b000] likely on CPU 3 (core 3, socket 0)
…
Aug 12 02:45:46 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 3/3)
Aug 12 02:45:46 poxter gnome-shell[1896]: Running GNOME Shell (using mutter 44.3) as a X11 window and compositing manager
…
Aug 12 02:45:49 poxter systemd[538]: Stopping GNOMEShell on X11...
Aug 12 02:45:49 poxter gnome-shell[1896]: Shutting down GNOME Shell
Aug 12 02:45:49 poxter kernel: gnome-shell[1896]: segfault at 28 ip 00007ff1926ef3a4 sp 00007ffe730301c0 error 4 in libmutter-clutter-12.so.0.0.0[7ff192664000+bb000] likely on CPU 3 (core 3, socket 0)
…
Aug 12 02:45:55 poxter systemd-logind[466]: New session 5 of user poxter.
…
Aug 12 02:45:56 poxter systemd[538]: Starting GNOME Shell on X11...
…
Aug 12 02:46:09 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 1/3)
Aug 12 02:46:09 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 2/3)
Aug 12 02:46:09 poxter kernel: wlan0: send auth to b8:f8:53:9c:dc:7a (try 3/3)
Aug 12 02:46:09 poxter kernel: wlan0: authentication with b8:f8:53:9c:dc:7a timed out
Aug 12 02:46:09 poxter wpa_supplicant[475]: BSSID b8:f8:53:9c:dc:7a ignore list count incremented to 2, ignoring for 10 seconds
Aug 12 02:46:09 poxter wpa_supplicant[475]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="jaevfafa" auth_failures=2 duration=20 reason=CONN_FAILED
Aug 12 02:46:09 poxter NetworkManager[474]: <info>  [1691822769.7007] device (wlan0): supplicant interface state: authenticating -> disconnected
Aug 12 02:46:16 poxter kernel: gnome-shell[2343]: segfault at 0 ip 00007eff64efef37 sp 00007ffdb615eae0 error 4 in libX11.so.6.4.0[7eff64ed9000+8b000] likely on CPU 4 (core 4, socket 0)
…
Aug 12 02:46:17 poxter systemd[538]: Started GNOME Shell on X11.
…
Aug 12 02:46:38 poxter systemd[538]: Stopping GNOME Shell on X11...
Aug 12 02:46:38 poxter gnome-shell[3069]: Shutting down GNOME Shell
Aug 12 02:46:38 poxter kernel: gnome-shell[3069]: segfault at 28 ip 00007f031f8523a4 sp 00007ffd5304f630 error 4 in libmutter-clutter-12.so.0.0.0[7f031f7c7000+bb000] likely on CPU 6 (core 6, socket 0)

gnome starts, crashes in libX11 with what looks like a corrupted stack during wifi init, restarts, stops 3s later, crashes in libmutter (w/ stack corrupted?) restarts after a re-login, crashes in libX11 again (again around wifi failures), restarts, stops 19s later, crashes in libmutter

You're not getting rid of /run/user/1000/gnome-shell-disable-extensions after the first crash.

Are you certain that it's the systemd update (did you try to downgrade systemd?)
The two crashes in libX11 don't look like they're related to explicit restart events are happen out of the blue (save the suspicious wifi activity)

Can you reboot and only use the ethernet connection? Do you still get those crashes in libX11?

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

Offline

#7 2023-08-12 07:49:47

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

The crash after re-login was manually triggered by me, so it appears to only be 2 segfaults per Alt+F2+r. What I visually observed when I run Alt + F2 + r is that first the GNOME crash screen appears, then the gnome-shell automatically tries to reset my workspace, only for the crash screen to appear again.

I am sure it is related to the systemd update, because I have downgraded back to 253 multiple times, and it is consistently on 254 where this is a problem.

I do not have ethernet, and I doubt wifi has anything to do with it since these crashes occur regardless of my network stability. I only run GNOME in XOrg, so I'm not sure what you mean by still getting the crashes in libX11.

Last edited by GeneralPoxter (2023-08-12 07:53:47)

Offline

#8 2023-08-12 08:09:23

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Have you downgraded systemd in isolation or the entire system for those tests?
(I don't like the stack corruption and there's some massive problem glibc right now)

There's a similar https://bugs.launchpad.net/mutter/+bug/1942031 - on a wild guess and because it's gnome, does this also happen when using GDM isntead of lightdm?

so I'm not sure what you mean by still getting the crashes in libX11.

There're two different crash patterns, the one ending in libX11 likely the originator when you try to restart and the one in libmutter the follow-up crash when gnome tries to recover from that.

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

Offline

#9 2023-08-12 08:13:45

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

I only downgraded systemd for those tests using the downgrade package from the AUR.

Edit: Disabling lightdm and enabling gdm still leads to the same crash: http://0x0.st/H_IJ.txt

Last edited by GeneralPoxter (2023-08-12 08:18:01)

Offline

#10 2023-08-12 13:23:13

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Does the Alt+F2 window actually show up?
Can you 

dbus-send --type=method_call --print-reply --dest=org.gnome.Shell /org/gnome/Shell org.gnome.Shell.Eval string:'global.reexec_self()'

w/o the crash?

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

Offline

#11 2023-08-12 13:37:49

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

The window does show up, and running commands like "rt" (which restart only the shell theme) appear to work fine.

Output is:

method return time=1691847425.387602 sender=:1.13 -> destination=:1.102 serial=635 reply_serial=2
   boolean false
   string ""

Offline

#12 2023-08-12 14:57:06

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Oh, great. You cannot trigger this externally anymore.
https://github.com/ramottamado/unsafe-mode

As if anybody would ever want to debug *what* "hAs gOnE WrOnG"… roll

You probably want to test the behavior w/ a fresh user account to ensure it's not a local config/extension (though gnome plans to deactivate them) and then file a bug upstream (gnome)

I suspect that something™ wants to talk to the X11 server during the process termination what fails w/ an X error, gtk figures it's time for a pointless segfault instead of handling (or just ignoring) that error (which is unfortunately normal) and induces a crash-on-exit where the stack is already gone.
Because of the systemd update being relevant, this is probably related to some user service and ultimately a race condition.

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

Offline

#13 2023-08-12 15:18:44

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Sounds good, thanks for the help!

Offline

#14 2023-08-14 18:55:16

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Oh wait, it turns out gnome-shell restart also segfaults on systemd 253: the only difference is that it doesn't segfault twice and GNOME doesn't show the crash page.

Here's the journal log for the 253 segfault (extensions are off): http://0x0.st/HL-Q.txt

Offline

#15 2023-08-14 20:52:31

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Still no https://wiki.archlinux.org/title/Core_d … _core_dump ?
Remove the static config (/etc/X11/xorg.conf) and check 

pacman -Qikk libX11 gnome-shell

as well as 

type gnome-shell; ldd /usr/bin/gnome-shell

to make sure you're not loading some local library there.
Finally check https://bugs.archlinux.org/task/79300 - I really don't like that there's no coredump …

Maybe attach gdb to the gnbome-shell process from another VT, maybe that gets us a backtrace hmm
You'll have to

sudo sysctl kernel.yama.ptrace_scope=0

to attach gdb as unprivileged user (even to your own process)

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

Offline

#16 2023-08-14 23:46:32

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Nope, no coredumps listed under coredumpctl.

By removing /etc/X11/xorg.conf, do you mean renaming the file and rebooting?

Here is the output of pacman:

Name            : libx11
Version         : 1.8.6-1
Description     : X11 client-side library
Architecture    : x86_64
URL             : https://xorg.freedesktop.org/
Licenses        : custom
Groups          : None
Provides        : None
Depends On      : libxcb  glibc  xorgproto
Optional Deps   : None
Required By     : aalib  at-spi2-core  audacity  cairo  ffmpeg  ffmpeg4.4  freerdp
                  ghostscript  gimp  gst-plugins-bad-libs  gtk3  gtk4  libcaca  libepoxy
                  libreoffice-fresh  libspnav  libva  libwmf  libxext  libxfixes  libxkbfile
                  libxklavier  libxrender  libxt  lightdm  mpv  openxr  qemu-ui-gtk
                  qemu-ui-sdl  sdl2  simplescreenrecorder  spice-gtk  startup-notification
                  vdpauinfo  webkit2gtk  webkit2gtk-4.1  webkitgtk-6.0  xorg-x11perf
                  xorg-xcmsdb  xorg-xcursorgen  xorg-xdpyinfo  xorg-xdriinfo  xorg-xev
                  xorg-xgamma  xorg-xhost  xorg-xinput  xorg-xkbutils  xorg-xkill
                  xorg-xmodmap  xorg-xpr  xorg-xprop  xorg-xrandr  xorg-xrdb  xorg-xrefresh
                  xorg-xsetroot  xorg-xvinfo  xorg-xwd  xorg-xwud  zoom  zvbi
Optional For    : brltty  glew  hwloc  mtools  suil
Conflicts With  : None
Replaces        : None
Installed Size  : 9.86 MiB
Packager        : T.J. Townsend <blakkheim@archlinux.org>
Build Date      : Thu 15 Jun 2023 03:42:56 PM EDT
Install Date    : Fri 16 Jun 2023 01:48:46 PM EDT
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

libx11: 1264 total files, 0 altered files
Name            : gnome-shell
Version         : 1:44.3-1
Description     : Next generation desktop shell
Architecture    : x86_64
URL             : https://wiki.gnome.org/Projects/GnomeShell
Licenses        : GPL
Groups          : gnome
Provides        : None
Depends On      : accountsservice  gcr-4  gjs  gnome-autoar  gnome-session
                  gnome-settings-daemon  gsettings-desktop-schemas  gtk4  libadwaita
                  libcanberra-pulse  libgdm  libgweather-4  libibus  libnma-gtk4  libsecret
                  libsoup3  mutter  unzip  upower  libmutter-12.so=0-64
Optional Deps   : evolution-data-server: Evolution calendar integration [installed]
                  gnome-bluetooth-3.0: Bluetooth support [installed]
                  gnome-control-center: System settings [installed]
                  gnome-disk-utility: Mount with keyfiles [installed]
                  gst-plugin-pipewire: Screen recording
                  gst-plugins-good: Screen recording [installed]
                  power-profiles-daemon: Power profile switching
                  switcheroo-control: Multi-GPU support
Required By     : gdm  gnome-browser-connector  gnome-control-center
                  gnome-shell-extension-pop-shell-git  gnome-shell-extensions
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 11.53 MiB
Packager        : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date      : Thu 06 Jul 2023 04:10:16 PM EDT
Install Date    : Thu 13 Jul 2023 02:24:38 PM EDT
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

gnome-shell: 442 total files, 0 altered files

And here is the output of type gnome-shell:

gnome-shell is /usr/bin/gnome-shell
	linux-vdso.so.1 (0x00007fff6634d000)
	libshell-12.so => /usr/lib/gnome-shell/libshell-12.so (0x00007f3996400000)
	libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f399622a000)
	libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f39967f7000)
	libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f39966ac000)
	libatk-bridge-2.0.so.0 => /usr/lib/libatk-bridge-2.0.so.0 (0x00007f39961ef000)
	libgjs.so.0 => /usr/lib/libgjs.so.0 (0x00007f399608b000)
	libmutter-clutter-12.so.0 => /usr/lib/mutter-12/libmutter-clutter-12.so.0 (0x00007f3995f4a000)
	libmutter-cogl-pango-12.so.0 => /usr/lib/mutter-12/libmutter-cogl-pango-12.so.0 (0x00007f3995f3e000)
	libgirepository-1.0.so.1 => /usr/lib/libgirepository-1.0.so.1 (0x00007f3995f1a000)
	libmutter-12.so.0 => /usr/lib/libmutter-12.so.0 (0x00007f3995c00000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f3995ef5000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f3995800000)
	libgnome-shell-menu.so => /usr/lib/gnome-shell/libgnome-shell-menu.so (0x00007f3995eea000)
	libst-12.so => /usr/lib/gnome-shell/libst-12.so (0x00007f3995b52000)
	libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00007f3995ea4000)
	libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00007f39956ce000)
	libmutter-cogl-12.so.0 => /usr/lib/mutter-12/libmutter-cogl-12.so.0 (0x00007f3995a96000)
	libgraphene-1.0.so.0 => /usr/lib/libgraphene-1.0.so.0 (0x00007f3995e85000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f399558b000)
	libpolkit-agent-1.so.0 => /usr/lib/libpolkit-agent-1.so.0 (0x00007f3995e79000)
	libpolkit-gobject-1.so.0 => /usr/lib/libpolkit-gobject-1.so.0 (0x00007f3995a79000)
	libgcr-4.so.4 => /usr/lib/libgcr-4.so.4 (0x00007f39954f9000)
	libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x00007f3995406000)
	libnm.so.0 => /usr/lib/libnm.so.0 (0x00007f3995295000)
	libsecret-1.so.0 => /usr/lib/libsecret-1.so.0 (0x00007f3995231000)
	libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f3995e71000)
	libgnome-desktop-4.so.2 => /usr/lib/libgnome-desktop-4.so.2 (0x00007f3995a59000)
	libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f3995e6a000)
	libz.so.1 => /usr/lib/libz.so.1 (0x00007f3995217000)
	libmount.so.1 => /usr/lib/libmount.so.1 (0x00007f39951c6000)
	libffi.so.8 => /usr/lib/libffi.so.8 (0x00007f3995a4e000)
	libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x00007f399512b000)
	libatspi.so.0 => /usr/lib/libatspi.so.0 (0x00007f39950f1000)
	libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00007f39950c9000)
	libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f3995078000)
	libmozjs-102.so => /usr/lib/libmozjs-102.so (0x00007f3993200000)
	libreadline.so.8 => /usr/lib/libreadline.so.8 (0x00007f3995021000)
	libcairo-gobject.so.2 => /usr/lib/libcairo-gobject.so.2 (0x00007f3995016000)
	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f3992e00000)
	libjson-glib-1.0.so.0 => /usr/lib/libjson-glib-1.0.so.0 (0x00007f3994feb000)
	libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00007f3993197000)
	libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f399308c000)
	libfribidi.so.0 => /usr/lib/libfribidi.so.0 (0x00007f3992de0000)
	libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00007f399307c000)
	libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00007f3992dc8000)
	libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f3992d79000)
	libm.so.6 => /usr/lib/libm.so.6 (0x00007f3992c8c000)
	libwayland-server.so.0 => /usr/lib/libwayland-server.so.0 (0x00007f3992c74000)
	libEGL.so.1 => /usr/lib/libEGL.so.1 (0x00007f3992c62000)
	libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f3992bdc000)
	libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f3992bc7000)
	libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f3992bc2000)
	libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00007f3992bbd000)
	libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f3992bae000)
	libXtst.so.6 => /usr/lib/libXtst.so.6 (0x00007f3992ba6000)
	libXi.so.6 => /usr/lib/libXi.so.6 (0x00007f3992b92000)
	libwacom.so.9 => /usr/lib/libwacom.so.9 (0x00007f3992b84000)
	libcolord.so.2 => /usr/lib/libcolord.so.2 (0x00007f3992b29000)
	liblcms2.so.2 => /usr/lib/liblcms2.so.2 (0x00007f3992ac3000)
	libxkbcommon.so.0 => /usr/lib/libxkbcommon.so.0 (0x00007f3992a7a000)
	libcanberra.so.0 => /usr/lib/libcanberra.so.0 (0x00007f3992a67000)
	libgudev-1.0.so.0 => /usr/lib/libgudev-1.0.so.0 (0x00007f3992a5a000)
	libudev.so.1 => /usr/lib/libudev.so.1 (0x00007f3992a23000)
	libstartup-notification-1.so.0 => /usr/lib/libstartup-notification-1.so.0 (0x00007f3992a18000)
	libpipewire-0.3.so.0 => /usr/lib/libpipewire-0.3.so.0 (0x00007f3992936000)
	libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00007f399292f000)
	libICE.so.6 => /usr/lib/libICE.so.6 (0x00007f3992911000)
	libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f3992905000)
	libxkbfile.so.1 => /usr/lib/libxkbfile.so.1 (0x00007f39928dd000)
	libxkbcommon-x11.so.0 => /usr/lib/libxkbcommon-x11.so.0 (0x00007f39928d4000)
	libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0x00007f39928cf000)
	libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f39928a2000)
	libxcb-randr.so.0 => /usr/lib/libxcb-randr.so.0 (0x00007f3992890000)
	libxcb-res.so.0 => /usr/lib/libxcb-res.so.0 (0x00007f399288a000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f3992885000)
	libSM.so.6 => /usr/lib/libSM.so.6 (0x00007f399287a000)
	libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007f3992863000)
	libinput.so.10 => /usr/lib/libinput.so.10 (0x00007f399280d000)
	libgbm.so.1 => /usr/lib/libgbm.so.1 (0x00007f39927fd000)
	/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f399688d000)
	libGLESv2.so.2 => /usr/lib/libGLESv2.so.2 (0x00007f39927eb000)
	libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f39927b1000)
	libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f3992705000)
	libtiff.so.6 => /usr/lib/libtiff.so.6 (0x00007f399266c000)
	libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f399259e000)
	libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f3992591000)
	libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007f3992582000)
	libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x00007f399257d000)
	libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007f39924d0000)
	libgck-2.so.2 => /usr/lib/libgck-2.so.2 (0x00007f399249b000)
	libp11-kit.so.0 => /usr/lib/libp11-kit.so.0 (0x00007f3992305000)
	libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007f39921bd000)
	libcap.so.2 => /usr/lib/libcap.so.2 (0x00007f39921b1000)
	liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007f399218f000)
	liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f399215a000)
	libzstd.so.1 => /usr/lib/libzstd.so.1 (0x00007f3992087000)
	libsmime3.so => /usr/lib/libsmime3.so (0x00007f399205f000)
	libnss3.so => /usr/lib/libnss3.so (0x00007f3991f27000)
	libnspr4.so => /usr/lib/libnspr4.so (0x00007f3991ee6000)
	libtss2-esys.so.0 => /usr/lib/libtss2-esys.so.0 (0x00007f3991e49000)
	libtss2-mu.so.0 => /usr/lib/libtss2-mu.so.0 (0x00007f3991df7000)
	libtss2-rc.so.0 => /usr/lib/libtss2-rc.so.0 (0x00007f3991ded000)
	libtss2-tctildr.so.0 => /usr/lib/libtss2-tctildr.so.0 (0x00007f3991de3000)
	libxkbregistry.so.0 => /usr/lib/libxkbregistry.so.0 (0x00007f3991dd9000)
	libseccomp.so.2 => /usr/lib/libseccomp.so.2 (0x00007f3991dba000)
	libblkid.so.1 => /usr/lib/libblkid.so.1 (0x00007f3991d7c000)
	libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0x00007f3991d05000)
	libthai.so.0 => /usr/lib/libthai.so.0 (0x00007f3991cfa000)
	libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f3991cd7000)
	libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f3991cac000)
	libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007f3991bf2000)
	libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007f3991bc0000)
	libvorbisfile.so.3 => /usr/lib/libvorbisfile.so.3 (0x00007f3991bb5000)
	libtdb.so.1 => /usr/lib/libtdb.so.1 (0x00007f3991b9d000)
	libltdl.so.7 => /usr/lib/libltdl.so.7 (0x00007f3991b92000)
	libxcb-util.so.1 => /usr/lib/libxcb-util.so.1 (0x00007f3991b89000)
	libxcb-xkb.so.1 => /usr/lib/libxcb-xkb.so.1 (0x00007f3991b6a000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f3991b62000)
	libuuid.so.1 => /usr/lib/libuuid.so.1 (0x00007f3991b59000)
	libmtdev.so.1 => /usr/lib/libmtdev.so.1 (0x00007f3991b52000)
	libevdev.so.2 => /usr/lib/libevdev.so.2 (0x00007f3991b32000)
	libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f3991b1f000)
	libbrotlidec.so.1 => /usr/lib/libbrotlidec.so.1 (0x00007f3991b11000)
	libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f3991aeb000)
	libnssutil3.so => /usr/lib/libnssutil3.so (0x00007f3991ab9000)
	libplds4.so => /usr/lib/libplds4.so (0x00007f3991ab2000)
	libplc4.so => /usr/lib/libplc4.so (0x00007f3991aab000)
	libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x00007f3991400000)
	libtss2-sys.so.1 => /usr/lib/libtss2-sys.so.1 (0x00007f3991a84000)
	libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f399191e000)
	libdatrie.so.1 => /usr/lib/libdatrie.so.1 (0x00007f3991913000)
	libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00007f39913d2000)
	libogg.so.0 => /usr/lib/libogg.so.0 (0x00007f3991908000)
	libbrotlicommon.so.1 => /usr/lib/libbrotlicommon.so.1 (0x00007f39913af000)
	libicuuc.so.73 => /usr/lib/libicuuc.so.73 (0x00007f3991000000)
	libicudata.so.73 => /usr/lib/libicudata.so.73 (0x00007f398f000000)

Last edited by GeneralPoxter (2023-08-14 23:47:28)

Offline

#17 2023-08-15 06:00:06

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

do you mean renaming the file and rebooting?

Or delete it, but moving/renaming it will do.
I've limited hopes for this (server seems to close cleanly) but static server configs occlude problems, so maybe someting shows up in the xorg log w/o it.

The packages are ok and gnome-shell doesn't link anything weird either.

seth wrote:

You probably want to test the behavior w/ a fresh user account to ensure it's not a local config/extension

Did you, btw?

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

Offline

#18 2023-08-15 06:15:23

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Ah my bad it does appear to be a problem local to my user. I cannot replicate the behavior on the new user account.

Do you know which local config files I should be checking to figure out what's wrong? I did try turning off the gnome extensions via the extensions panel and rebooting, but that didn't seem to work.

Last edited by GeneralPoxter (2023-08-15 06:26:59)

Offline

#19 2023-08-15 06:27:43

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

I didn't inspect the logs carefully enough: https://0x0.st/HLXm.txt

Even on the fresh user account, there's a segfault.

Offline

#20 2023-08-15 06:34:26

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Here are the logs after I moved my xorg.conf to xorg.conf.moved: https://0x0.st/HLXQ.txt

I am on systemd 253, and still no coredumps

Offline

#21 2023-08-15 06:45:12

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

The logout crash doesn't show up in https://0x0.st/HLXm.txt ?

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

Offline

#22 2023-08-15 06:46:03

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

That's because I ran both of these on systemd 253, and it seems that upgrading to systemd 254 was what led to two crashes occurring instead of one.

Offline

#23 2023-08-15 06:58:33

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

No, there's only

Aug 15 02:11:46 poxter gnome-shell[924]: Registering session with GDM
Aug 15 02:11:46 poxter gnome-shell[924]: Error registering session with GDM: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files
Aug 15 02:11:48 poxter gnome-software[1156]: Only 5 apps for curated list, hiding
Aug 15 02:11:49 poxter gnome-software[1156]: Tried to set invalid release date: 2022
Aug 15 02:11:49 poxter gnome-software[1156]: Tried to set invalid release date: 2022
Aug 15 02:11:52 poxter systemd[859]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=11/SEGV
Aug 15 02:11:52 poxter systemd[859]: org.gnome.Shell@x11.service: Failed with result 'core-dump'.

which doesn't look like the other crashes hmm

Did you see https://bugs.archlinux.org/task/79300 ?
It's a long stretch, but loqs posted patched glibc packages there that stand a good chance to fix the issue, you could try those. With a  little luck we'll at least get a backtrace.

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

Offline

#24 2023-08-19 06:11:13

GeneralPoxter
Member
Registered: 2020-09-25
Posts: 60

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

Updating to glibc 2.38-3 does not seem to fix the issue.

Offline

#25 2023-08-19 06:26:43

seth
Member
Registered: 2012-09-03
Posts: 59,716

Re: [SOLVED] Updating systemd from 253 to 254 breaks gnome-shell restart

No backtrace either?
Attach gdb before you log out and hope for the best.

Did you mayhaps enable process lingering  (KillUserProcesses in /etc/systemd/logind.conf, https://wiki.archlinux.org/title/System … _instances )?

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

Offline

Pages: 1 2

Board footer

Powered by FluxBB