I recently reported the issue to jetbrains https://youtrack.jetbrains.com/issue/IDEA-233737 (with a screencast)
All packages: mutter, mutter-common, gir1.2-mutter-5 and libmutter-5-50 are at version 3.34.1+git20191107-1ubuntu1~19.10.1 journalctl log ------------------------------- feb 25 12:20:29 delphy gnome-shell[9183]: ** feb 25 12:20:29 delphy gnome-shell[9183]: mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should not be reached feb 25 12:20:29 delphy gnome-shell[9183]: Bail out! mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should not be reached feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 0x55de5b4f1540 == feb 25 12:20:29 delphy gnome-shell[9183]: GNOME Shell crashed with signal 6 feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 0x55de5b4f1540 == -------------------------------------------- Also attached the gdb.txt file produced with these instructions https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-shell Hope it helps ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845281/+attachment/5330843/+files/gdb.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
