The crash history supports the theory that this was:
https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34
because that fix appeared in libx11 1.7.0 during the hirsute development
cycle. So usually at this point I would recommend trying that fix.
However, despite being the top gnome-shell crasher on errors.ubuntu.com
this bug page is so quiet that I'm not sure we have enough people
engaged to be able to test any potential fix.
** Also affects: libx11 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libx11 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: libx11 (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
** Changed in: mutter (Ubuntu)
Status: Incomplete => Invalid
** Also affects: libx11 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: libx11 (Ubuntu Focal)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: libx11 (Ubuntu Focal)
Status: New => Confirmed
** Changed in: libx11 (Ubuntu)
Importance: Undecided => High
** Changed in: libx11 (Ubuntu Focal)
Importance: Undecided => High
** No longer affects: gnome-shell (Ubuntu Focal)
** No longer affects: mutter (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1886059
Title:
gnome-shell crashed with assertion failure
"!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Invalid
Status in libx11 package in Ubuntu:
Fix Released
Status in mutter package in Ubuntu:
Invalid
Status in libx11 source package in Focal:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.36.3-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
Similar errors:
https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd
https://errors.ubuntu.com/problem/e3f9ab8232005403e935c6038edd99f13e609e01
https://errors.ubuntu.com/problem/9d421ecaba25357f5c3ef73f438313e40ac24e77
https://errors.ubuntu.com/problem/42cfd76250a81cca07f8c548ec27e245315b5e01
---
Anyone experiencing this crash reliably, please help us to find its
root cause by editing your /etc/environment and adding a line:
MUTTER_SYNC=1
and then reboot. Then next time a crash happens please tell us (here)
the bug ID or error URL of the new crash.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1886059/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
