Wayland GNOME session not working after KDE login

Hi,

I usually run GNOME as my desktop environment, but wanted to test out KDE. So I tested KDE for a short while, but decided to revert back to GNOME.

Now the Wayland version of GNOME won’t start (which worked perfectly prior), but the X11 version will. I do see that I have a bunch of core dumps from /nix/store/6pq0v0hj0jg40frpbq44h2sqbmpmlzs8-gnome-shell-3.36.5/bin/.gnome-shell-wrapped when running coredumpctl.
The stack trace is not very enlightening to me, and I don’t really know how to debug this further. Any tips or pointers as to where I should look?

Using host libthread_db library "/nix/store/0c7c96gikmzv87i7lv3vq5s1cmfjd6zf-glibc-2.31-74/lib/libthread_db.so.1".
Core was generated by `/nix/store/6pq0v0hj0jg40frpbq44h2sqbmpmlzs8-gnome-shell-3.36.5/bin/gnome-shell'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
--Type <RET> for more, q to quit, c to continue without paging--
#0  0x00007f72bf5feffa in raise () from /nix/store/0c7c96gikmzv87i7lv3vq5s1cmfjd6zf-glibc-2.31-74/lib/libc.so.6
[Current thread is 1 (Thread 0x7f72ba5b1d80 (LWP 23213))]
(gdb) where
#0  0x00007f72bf5feffa in raise () from /nix/store/0c7c96gikmzv87i7lv3vq5s1cmfjd6zf-glibc-2.31-74/lib/libc.so.6
#1  0x0000000000403e92 in dump_gjs_stack_on_signal_handler ()
#2  <signal handler called>
#3  0x00007f72c0451415 in _g_log_abort () from /nix/store/ai5054xzilz0q285c0ldabmkvhyyl6yq-glib-2.64.6/lib/libglib-2.0.so.0
#4  0x00007f72c0452485 in g_log_default_handler () from /nix/store/ai5054xzilz0q285c0ldabmkvhyyl6yq-glib-2.64.6/lib/libglib-2.0.so.0
#5  0x0000000000403f4a in default_log_handler ()
#6  0x00007f72c04526cc in g_logv () from /nix/store/ai5054xzilz0q285c0ldabmkvhyyl6yq-glib-2.64.6/lib/libglib-2.0.so.0
#7  0x00007f72c04528af in g_log () from /nix/store/ai5054xzilz0q285c0ldabmkvhyyl6yq-glib-2.64.6/lib/libglib-2.0.so.0
#8  0x00007f72bf7f67e8 in meta_cursor_sprite_xcursor_realize_texture () from /nix/store/64b7zs5pyh70sdqp0a5q8dsp28sj3cgd-mutter-3.36.5/lib/libmutter-6.so.0
#9  0x00007f72bf8bfc74 in meta_cursor_renderer_native_update_cursor () from /nix/store/64b7zs5pyh70sdqp0a5q8dsp28sj3cgd-mutter-3.36.5/lib/libmutter-6.so.0
#10 0x00007f72bf7f5c84 in meta_cursor_renderer_update_cursor () from /nix/store/64b7zs5pyh70sdqp0a5q8dsp28sj3cgd-mutter-3.36.5/lib/libmutter-6.so.0
#11 0x00007f72bf7f6b86 in sync_cursor () from /nix/store/64b7zs5pyh70sdqp0a5q8dsp28sj3cgd-mutter-3.36.5/lib/libmutter-6.so.0
#12 0x00007f72bf83d80e in meta_display_reload_cursor () from /nix/store/64b7zs5pyh70sdqp0a5q8dsp28sj3cgd-mutter-3.36.5/lib/libmutter-6.so.0
#13 0x00007f72bf83f105 in meta_display_open () from /nix/store/64b7zs5pyh70sdqp0a5q8dsp28sj3cgd-mutter-3.36.5/lib/libmutter-6.so.0
#14 0x00007f72bf8495cc in meta_run () from /nix/store/64b7zs5pyh70sdqp0a5q8dsp28sj3cgd-mutter-3.36.5/lib/libmutter-6.so.0
#15 0x000000000040383d in main ()

Thanks

1 Like

I would check the systemd journal. Note that a single crash can cause a chain reaction of crashes so look for all the previous warnings/errors as well.

Also note that GNOME support on stable NixOS is limited since it has very outdated versions.

Thanks, so here’s where I try to login on the Wayland GNOME session:

apr 22 18:34:42 crow .gnome-shell-wr[1604]: Could not find cursor. Perhaps set XCURSOR_PATH?
apr 22 18:34:42 crow gnome-shell[1604]: == Stack trace for context 0x22b1160 ==
apr 22 18:34:42 crow systemd[1]: Created slice system-systemd\x2dcoredump.slice.
apr 22 18:34:42 crow systemd[1]: Started Process Core Dump (PID 1667/UID 0).
apr 22 18:34:43 crow systemd[1566]: gnome-shell-wayland.service: Main process exited, code=dumped, status=5/TRAP
apr 22 18:34:43 crow systemd[1566]: gnome-shell-wayland.service: Failed with result 'core-dump'.
apr 22 18:34:43 crow systemd[1566]: Failed to start GNOME Shell on Wayland.
apr 22 18:34:43 crow systemd[1566]: Dependency failed for GNOME Shell on Wayland.
apr 22 18:34:43 crow systemd[1566]: Dependency failed for GNOME Wayland Session.
apr 22 18:34:43 crow systemd[1566]: Dependency failed for GNOME Wayland Session (session: gnome).
apr 22 18:34:43 crow systemd[1566]: gnome-session-wayland@gnome.target: Job gnome-session-wayland@gnome.target/start failed with result 'dependency'.
apr 22 18:34:43 crow systemd[1566]: gnome-session-wayland.target: Job gnome-session-wayland.target/start failed with result 'dependency'.
apr 22 18:34:43 crow systemd[1566]: gnome-session-wayland.target: Triggering OnFailure= dependencies.
apr 22 18:34:43 crow systemd[1566]: gnome-shell-wayland.target: Job gnome-shell-wayland.target/start failed with result 'dependency'.
apr 22 18:34:43 crow systemd[1566]: gnome-shell-wayland.service: Triggering OnFailure= dependencies.
apr 22 18:34:43 crow systemd[1566]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped.
apr 22 18:34:43 crow systemd[1566]: Stopped target GNOME Session Manager is ready.
apr 22 18:34:43 crow systemd[1566]: Stopping GNOME Session Manager (session: gnome)...
apr 22 18:34:43 crow systemd[1566]: gnome-session-manager@gnome.service: Succeeded.
apr 22 18:34:43 crow systemd[1566]: Stopped GNOME Session Manager (session: gnome).
apr 22 18:34:43 crow systemd[1566]: Stopped target Tasks to be run before GNOME Session starts.
apr 22 18:34:43 crow systemd[1566]: Stopped target Session services which should run early before the graphical session is brought up.
apr 22 18:34:43 crow systemd[1566]: Reached target Shutdown running GNOME Session.
apr 22 18:34:43 crow systemd[1566]: Stopping Monitor Session leader for GNOME Session...
apr 22 18:34:43 crow systemd[1566]: Starting Restart DBus after GNOME Session shutdown...
apr 22 18:34:43 crow systemd[1566]: Stopped target Shutdown running GNOME Session.
apr 22 18:34:43 crow systemd[1566]: Reached target Shutdown running GNOME Session.
apr 22 18:34:43 crow systemd[1566]: Stopped target Shutdown running GNOME Session.
apr 22 18:34:43 crow systemd[1566]: gnome-session-monitor.service: Succeeded.
apr 22 18:34:43 crow systemd[1566]: Stopped Monitor Session leader for GNOME Session.
apr 22 18:34:43 crow systemd[1566]: Started Restart DBus after GNOME Session shutdown.
apr 22 18:34:43 crow gdm-password][1487]: pam_unix(gdm-password:session): session closed for user jon
apr 22 18:34:43 crow systemd[1566]: Stopping D-Bus User Message Bus...
apr 22 18:34:43 crow systemd[1566]: gnome-session-restart-dbus.service: Succeeded.
apr 22 18:34:43 crow systemd[1566]: dbus.service: Succeeded.
apr 22 18:34:43 crow systemd[1566]: Stopped D-Bus User Message Bus.
apr 22 18:34:43 crow systemd[1566]: at-spi-dbus-bus.service: Succeeded.
apr 22 18:34:43 crow systemd[1566]: Started D-Bus User Message Bus.
apr 22 18:34:43 crow systemd-coredump[1668]: Process 1604 (.gnome-shell-wr) of user 1000 dumped core.

I did find a reference to a code fix for the XCURSOR_PATH in gnome. But what puzzles me is, what did KDE change to make it so GNOME stopped working? I don’t have a great intuition for what services could be affected.

Reading gnome-shell crashes when a cursor is not found (#355) · Issues · GNOME / mutter · GitLab, maybe plasma changed the cursor theme?

Indeed the final comment that sets the correct cursor theme fixes the issue:

gsettings set org.gnome.desktop.interface cursor-theme 'Adwaita'

Thanks!