I wonder if it could be a bug related to the crash reporting software
instead. What looks strange (but maybe I'm not reading it correctly) is
that the publishing history indicates it was brought back to 0% even
before it was put at 10% : https://launchpad.net/ubuntu/groovy/amd64
/gnome-shell

It seems to me it should at least collect some data before phasing out,
so maybe the bug is somewhere else or it has been blocked manually...

The qemu package looks affected too, maybe it's not a coincidence that
it has been published only a few days before :
https://launchpad.net/ubuntu/groovy/amd64/qemu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1913672

Title:
  gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion
  failures in st_bin_get_preferred_width

Status in gnome-shell package in Ubuntu:
  Incomplete

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.38.2-1ubuntu1~20.10.1, the problem page at 
https://errors.ubuntu.com/problem/4f12318421d8c95c357e2db953aa75b2cdcacdfa 
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/gnome-shell/+bug/1913672/+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

Reply via email to