Oops. Seems I was tricked by (b) in comment #3 again. The current
crashes being reported can't be attributed to "freeze/thaw" accounting
because errors.ubuntu.com doesn't look at enough of the stack trace to
confirm that. We only know that some people are experiencing crashes in
g_log(), which is itself correct because error level and higher messages
are meant to cause an abort().
We would need more concrete evidence of a crash in a current Ubuntu
release to pursue this further.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1915681
Title:
Error in freeze/thaw accounting, GNOME Shell crashed with signal 5,
resource:///org/gnome/shell/ui/windowManager.js:1384
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915681/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
