GNOME Bugzilla – Bug 791389
Gnome shell dump core when pressing "Super"
Last modified: 2017-12-08 12:11:36 UTC
After this morning reboot (first in a long time) I have a major issue with gnome-shell. Everythime I press super (win key) I get a crash that sends me back to le login screen. Due to muscle memory this happens A LOT! Journalctl tells me: déc. 08 12:47:43 Stardust systemd-coredump[1843]: Process 1741 (gnome-shell) of user 1000 dumped core. Stack trace of thread 1741: #0 0x00007f320be6cce0 n/a (libst-1.0.so) #1 0x00007f320be73c3b n/a (libst-1.0.so) #2 0x00007f320be79651 st_theme_node_paint (libst-1.0.so) #3 0x00007f320be7a792 st_widget_paint_background (libst-1.0.so) #4 0x00007f320be7a7bf n/a (libst-1.0.so) #5 0x00007f320ca9be54 clutter_actor_continue_paint (libmutter-clutter-1.so) #6 0x00007f320caa2485 n/a (libmutter-clutter-1.so) #7 0x00007f320caa2721 n/a (libmutter-clutter-1.so) #8 0x00007f320ca9be54 clutter_actor_continue_paint (libmutter-clutter-1.so) #9 0x00007f320caa2485 n/a (libmutter-clutter-1.so) #10 0x00007f320caa2721 n/a (libmutter-clutter-1.so) #11 0x00007f320ca9be54 clutter_actor_continue_paint (libmutter-clutter-1.so) #12 0x00007f320caa2485 n/a (libmutter-clutter-1.so) #13 0x00007f320be5c679 n/a (libst-1.0.so) #14 0x00007f320ca9be54 clutter_actor_continue_paint (libmutter-clutter-1.so) #15 0x00007f320caa2485 n/a (libmutter-clutter-1.so) #16 0x00007f320caa2721 n/a (libmutter-clutter-1.so) #17 0x00007f320ca9be54 clutter_actor_continue_paint (libmutter-clutter-1.so) #18 0x00007f320caa2485 n/a (libmutter-clutter-1.so) #19 0x00007f320e71890f n/a (libgnome-shell.so) #20 0x00007f320ca9be54 clutter_actor_continue_paint (libmutter-clutter-1.so) #21 0x00007f320caa2485 n/a (libmutter-clutter-1.so) #22 0x00007f320caf73db n/a (libmutter-clutter-1.so) #23 0x00007f320c303316 n/a (libmutter-1.so.0) #24 0x00007f320ca9be54 clutter_actor_continue_paint (libmutter-clutter-1.so) #25 0x00007f320caa2485 n/a (libmutter-clutter-1.so) #26 0x00007f320cafb722 n/a (libmutter-clutter-1.so) #27 0x00007f320cafba23 n/a (libmutter-clutter-1.so) #28 0x00007f320ca8bda6 n/a (libmutter-clutter-1.so) #29 0x00007f320ca8bf4c n/a (libmutter-clutter-1.so) #30 0x00007f320ca8d16b n/a (libmutter-clutter-1.so) #31 0x00007f320caf8409 n/a (libmutter-clutter-1.so) #32 0x00007f320cae3642 n/a (libmutter-clutter-1.so) #33 0x00007f320de4b270 g_main_context_dispatch (libglib-2.0.so.0) #34 0x00007f320de4cf69 n/a (libglib-2.0.so.0) #35 0x00007f320de4df42 g_main_loop_run (libglib-2.0.so.0) #36 0x00007f320c334030 meta_run (libmutter-1.so.0) #37 0x0000556a243ed011 n/a (gnome-shell) #38 0x00007f320eb6bf6a __libc_start_main (libc.so.6) #39 0x0000556a243ed16a n/a (gnome-shell) I tried downgrading gnome-shell - from 3.26.2+5+g3b4be770a-3 - to 3.26.2-1-x86_64.pkg.tar.xz - then again to 3.26.1+9+g49c144a64-1-x86_64.pkg.tar.xz I also tried downgrading glibc as it was also updated reccently This is VERY inconvenient. I can provide config files / other info upon request
The backtrace is fairly useless due to missing debug symbols, but I'll take a guess: Does downgrading gjs to the last stable release (that is, *no* commits from git master on top) help?
I just downgradded gjs gjs-1.50.2+8+gb65c785-1 → gjs-1.50.2-1 After a rebbot everything looks to be working correctly again! Thanks for the fix. If you ever need more info to try reproducing/fixing the issue please let me know.
Well, that's not a fix of course. It's just that gjs introduced a new error, and we'll need some time to fix the fallout. *** This bug has been marked as a duplicate of bug 791233 ***