gnome-shell is crashing when trying to lock the screen
Bug #1881542 reported by
Slavo Roikhel
This bug report is a duplicate of:
Bug #1877774: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel].
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Versions:
Ubuntu 20.04 LTS focal
GNOME Shell 3.36.2
gnome-screensaver 3.6.1-11ubuntu4
Using gdm3 as a display manager GDM 3.34.1
Expected:
When locking the computer it should lock it.
What happens instead:
Can't lock my screen at all with:
1) Super + L keys
2) Manually pressing 'Lock' on Menu
3)'gnome-
I have to Log out/ shutdown my computer at the end of the day.
In case I can't lock my screen it's a security issue.
syslog output:
Jun 1 16:47:02 slava-ubuntu gsd-media-
description: | updated |
description: | updated |
information type: | Private Security → Public Security |
summary: |
- Can't lock my screen at all after last update + Can't lock my screen after the latest update |
To post a comment you must log in.
Thanks for the video. That clearly shows gnome-shell is crashing, as hinted by your syslog output too...
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https:/ /errors. ubuntu. com/user/ ID where ID is the content of file /var/lib/ whoopsie/ whoopsie- id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.