While this bug is the top gnome-shell crasher by far, it's actually not what should be fixed first. What we should fix first are the top Xwayland crashes that are triggering this bug.
Upstream would like to make gnome-shell more independent of Xwayland so that Xwayland crashes don't also bring down gnome-shell. But that's longer term, and also would not help those applications using Xwayland when it crashes. So let's try to fix the Xwayland crashes first and then this bug then won't be such an issue. It appears the top xorg-server (Xwayland?) crasher that might be causing all this is still: https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530 (bug 1543192) Although that's based on the source package 'xorg-server'. If that's wrong and we should be looking at this instead (which is empty): https://errors.ubuntu.com/?package=xwayland&period=month then our top priority should be figuring out why Xwayland crashes aren't getting reported there (comment #31). Because our top priority should be finding out why Xwayland is crashing (or just failing to start? bug 1543192?) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
