Closed inducer closed 7 years ago
Hmm, it's hard to tell what's going on here.
The ERROR: assertion failed message is bad, it means that gnome-shell reports the current workspace is e.g. number 3
, but immediately asking for the workspace object number 3
returns nothing. This may be a race condition in gnome-shell (maybe the workspace only gets created shortly afterwards?).
This error could cause shellshape to stop functioning correctly, but the error is not fatal and is not responsible for crashing gnome-shell. Signal 11 is a segmentation violation, which is the real cause of death, and which should be impossible to trigger from Javascript (shellshape is entirely javascript). So I'm afraid just like #169, this is a gnome-shell bug. Unfortunately such bugs are hard to reproduce consistently / easily without running shellshape, so the gnome-shell developers have a hard time diagnosing them.
Hasn't been happening in a long time, closing.
Because of
https://bugzilla.gnome.org/show_bug.cgi?id=758302
I am currently restarting
gnome-shell
fairly often. Unfortunately, shellshape makes this a risky proposition, because upon that restart, some amount of the time, shellshape hits this assert and makes gnome-shell die:which then leads to the "Oh no, something has gone wrong" screen and a forced logout.