[BUG] Lock the screen on Overview or Applications crashes Gnome
Closed this issue · 10 comments
Specs:
Debian Testing, Gnome-shell 47.0-3, libmutter-15-0 47.0-3, dash to dock v99
Problem reproduce:
- disable all extensions
- go to overview or applications and lock the screen, works just fine
- enable dash to dock
- go to overview or applications and lock the screen
- Gnome crashes and showing the 'Oh no! Something has gone wrong.' screen.
- crash screen reload once and then normally locked the screen.
- after unlock the crash screen persists but can access to overview and applications by super key
here's the log by journalctl --since '1 minutes ago' > ./crash.txt
crash.txt
I'm having this exact same issue. I also happen to use the Debian Testing, could it be something related to some recent update to gnome packages? As far as I can remember, this issue began happening after some gnome package update but I'm not 100% sure
These log messages might give an insight of what's happening
Code: 00 00 00 48 8b 44 24 10 49 83 ed 08 49 39 c5 0f 84 c9 02 00 00 48 8b 83 28 01 00 00 4c 89 e6 4a 8b 2c 28 48 8b 45 00 48 8b 00 <48> 8b 38 e8 a9 8b fd ff 41 89 c6 85 c0 75 ca 8b 05 3c 16 03 00 4c
gnome-shell[9571]: segfault at 55cb00000001 ip 00007fd698ee95cf sp 00007ffd26559c60 error 4 in libst-15.so[475cf,7fd698ebf000+54000] likely on CPU 2 (core 2, socket 0)
It seems that this crash used to happen to dash-2-panel as well and it got fixed by this merge request. As it appears, this must be a gnome-shell specific issue.
Is there anyone that can confirm that this error also happens on GNOME 47.1?
Surprisingly, the shell does not crash if I manually click the lock screen button in the overview. @EricwanAR, may you check on your system if that is also the case?
Demonstration
demo.mp4
Surprisingly, the shell does not crash if I manually click the lock screen button in the overview. @EricwanAR, may you check on your system if that is also the case?
It still crashes this way.
Is there anyone that can confirm that this error also happens on GNOME 47.1?
Debian recently pushed mutter 47.1 to testing but not gnome-shell, so i did a testing-ustable-mix to update then altogether to 47.1. Although the crash persists.
Duplicate of #2179.
The fix is proposed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3252
Duplicate of #2179.
The fix is proposed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3252
Just backported your patch into my system, it is all working well now. Thanks for your great work
Duplicate of #2179.
The fix is proposed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3252
@vanvugt Thank you for your great effort. By the way I checked Debian's repo history of gnome shell and found out that your commit for this patch seems got accidentally reverted in this commit. Is it possible to roll it back?
Duplicate of #2179.
The fix is proposed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3252@vanvugt Thank you for your great effort. By the way I checked Debian's repo history of gnome shell and found out that your commit for this patch seems got accidentally reverted in this commit. Is it possible to roll it back?
Not the person you were expecting an answer from, but I think the best course of action here is to report the issue to debian so they can get it fixed on the next update. Meanwhile, you could gather the gnome-shell's source code and patch it yourself while that doesn't happen
Not the person you were expecting an answer from, but I think the best course of action here is to report the issue to debian so they can get it fixed on the next update. Meanwhile, you could gather the gnome-shell's source code and patch it yourself while that doesn't happen
Thanks for the advice. I'm a newcomer to debian. Just had some time spent in wiki to learn to patching source and reporting bugs and already have them done by now. 😉
Thanks @EricwanAR, I have committed a fix and asked for a Debian developer to publish it.