*** This bug is a duplicate of bug 1787512 ***
https://bugs.launchpad.net/bugs/1787512
** This bug has been marked a duplicate of bug 1787512
gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from
g_assertion_message() from g_assertion_message_expr() from
Daniel, yes, this is the same crash as in bug 1787512.
It's not a duplicate IMO, since I'd researched the exact repro steps.
Any developer can trigger the crash now, by following the repro steps.
That's why I didn't use ubuntu-bug either; just follow the repro steps
and trigger the crash
Isn't this a duplicate of bug 1787512?
If not then please follow these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Please NOTE: the report is against gnome-shell, NOT indicator-multiload!
It's not so important to fix the indicator app. Rather, gnome-shell
needs to become sturdier.
There's a change to be made to gnome-shell so that it perseveres
assertion failures and keeps running.
Lurking around, I've seen
