Lock screen key shortcut causes abnormal session termination

Desktop
1

Hello,

I am currently using GNOME 46.6 on Fedora 40. I noticed that if I press the lock screen shortcut (super + L) when the activities overview screen is activated (pressing the super button), this causes an immediate termination of the current gnome session ( all current programs are closed, and I am logged out). The issue can be reproduced by pressing the super button, and then when the activities overview screen appears, pressing super + L triggers the session termination. Can this be considered as a bug ?

I checked the gnome shell logs, and I found the following entries that happened at the same time the session was lost:

Nov 30 21:15:12 fedora gnome-shell[10580]: Connection to xwayland lost
Nov 30 21:15:12 fedora gnome-shell[10580]: Xwayland terminated, exiting since it was mandatory
Nov 30 21:15:12 fedora gnome-shell[10580]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly
                                           @resource:///org/gnome/shell/ui/init.js:21:20
Nov 30 21:15:12 fedora gnome-shell[10580]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
1 Like
2

I cannot reproduce this issue in GNOME 46.6 / Fedora 40 using GNOME Boxes.

If the issue is reproducible even after disabling all shell extensions (if any), then please report an issue at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues.

1 Like
3

Thanks for trying. The only extension I am using is “Dash To Dock”. After disabling it, the issue disappeared, so it should related to dash dock. I found a recent issue in the extension repo: activitity overview + screen lock crashed gnome shell (fedora 40, fedora 41) when dash to dock extension is enabled · Issue #2338 · micheleg/dash-to-dock · GitHub

I tried digging more into logs, and I found that the error happens here exactly: src/st/st-theme-node.c · main · GNOME / gnome-shell · GitLab

Before the stacktrace, I am seeing the following entry

Nov 30 21:15:03 fedora kernel: traps: gnome-shell[8623] general protection fault ip:7fd36357e6ab sp:7ffdf82bacb8 error:0 in libc.so.6[16f6ab,7fd363437000+16d000]

It could be that this is due to a segmentation fault when comparing against something null in strcmp. Let’s see what the extension maintainers say.

4

FWIW, this means Xwayland terminated, and that isn’t handled properly in the lock screen, probably since it’s using the legacy service management code and not the systemd one, which is required for surviving Xwayland going away unexpectedly.

1 Like
5

By the way, I found a related gnome-shell issue: A CSS-only extension causes gnome-shell to crash (#7339) · Issues · GNOME / gnome-shell · GitLab

This is also relevant: Crash during box shadow css lookup (#4851) · Issues · GNOME / gnome-shell · GitLab

6

Same issue here, on Fedora 41, but I experienced the same on Ubuntu 24 with Gnome 46.

For now I will try to avoid hitting the “super” key twice.

7

I am trying to fix the issue on gnome-shell. Anybody has an idea how to workaround key shortcuts not working in the gnome dev environment ? It’s mentionned here in the documentation docs/building-and-running.md · main · GNOME / gnome-shell · GitLab.
I was able to build and launch gnome, but without key shortcuts, I am not sure how can I reproduce the issue.

8

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.