[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Hello and thank you for following up.
Thank you for your suggestions. I will look into them.
I will be on the lookout for new crashes and report them here.
While uninstalling the unofficial desktop icon extension would seem like
a good idea in the context of this bug report, that would result
Thanks. Unfortunately that crash report doesn't contain enough info,
although it is from 17 December so that's good...
To avoid those earlier assertions (which I assume are not the crash
itself) please try deleting your monitor layout config:
rm ~/.config/monitors.xml
And to avoid confusion
Just a FYI, I'm a bit confused regarding the ID. The .uploaded file has
a timestamp earlier than the .crash file (about 12 hours earlier than
when I actually experienced the crash most recently) and the .uploaded
file doesn't change its contents after running ubuntu-bug, even as
superuser.
It
Thanks for taking a look.
I see. Found it - UUID from crash.uploaded: 362c2716-4051-11eb-
8be3-fa163ee63de6
Thank you for the suggestion. Did you spot any specific indication that
that extension was the source of the crash? Anyway, if you do, I can
reach out to them.
--
You received this bug
It may also help to try uninstalling these extensions:
'nightthemeswitc...@romainvigier.fr', 'd...@rastersoft.com'
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I don't think that assertion is fatal so it's not what's crashing. This
however is fatal:
dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with
signal 11
dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context
0x55db60db91a0 ==
If you have already
I also ran 'ubuntu-bug /var/crash/_my_crash_report.crash' for my crash
report, and was led to believe that a new bug would be created as a
result (in another issue I was there told to "tell us the ID of the
newly-created bug" after running that command), but I was given no
information by the time
When trying to mark this bug as private I get the message "The bug will
become invisible because there is no-one with permissions to see Private
bugs". Is that a mistake? Shouldn't someone be able to see it?
--
You received this bug notification because you are a member of Desktop
Packages,
9 matches
Mail list logo
