Thanks. It looks like a problem with errors.ubuntu.com itself, which is
not uncommon. The crash report exists but it failed to get a stack trace
and so errors.ubuntu.com can't categorise/group the crash reports.
This bug is still open at least, but it does mean we don't get a feel
for how common the crash is. It looks like it may only happen at logout
or during monitor config rearrangement.
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1969422
Title:
gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
meta_drm_buffer_gbm_finalize() from g_object_unref() from
g_object_unref() from g_set_object()
Status in mutter package in Ubuntu:
New
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
42.0-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4
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/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
