Below seems to be the only gnome-shell crash and it's an odd one. Even
though it's a Wayland session the cause was some unhandled X11 error
coming from the X server (Xwayland). This isn't totally surprising if
Teams is another Electron client and Electron (Chromium) defaults to X11
instead of native Wayland.
To debug this further please add MUTTER_SYNC=1 to /etc/environment,
reboot, and then report new crashes when they happen.
avril 01 13:34:24 LH33976 gnome-shell[4799]: Received an X Window System error.
This probably reflects a bug in
the program.
The error was 'BadWindow (invalid
Window parameter)'.
(Details: serial 7457903
error_code 3 request_code 7 (core protocol) minor_code 0)
(Note to programmers: normally,
X errors are reported asynchronously;
that is, you will receive the
error a while after causing it.
To debug your program, run it
with the MUTTER_SYNC environment
variable to change this
behavior. You can then get a meaningful
backtrace from your debugger if
you break on the mtk_x_error() function.)
avril 01 13:34:24 LH33976 gnome-shell[4799]: GNOME Shell crashed with signal 5
avril 01 13:34:24 LH33976 gnome-shell[5458]: (EE) failed to read Wayland
events: Connection reset by peer
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106656
Title:
Shell crash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2106656/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
