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 Desktop
Packages, 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
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
Feb 12 09:10:29 thinkpad gnome-shell[85476]: Error in freeze/thaw accounting
Feb 12 09:10:29 thinkpad gnome-shell[85476]: GNOME Shell crashed with signal 5
Feb 12 09:10:29 thinkpad gnome-shell[85476]: == Stack trace for context
0x561dd4480270 ==
Feb 12 09:10:29 thinkpad gnome-shell[85476]: #0 561dd96ccf18 i
resource:///org/gnome/shell/ui/windowManager.js:1384 (1c61e18d03d0 @ 589)
Feb 12 09:10:29 thinkpad gnome-shell[85476]: #1 7ffc72c53090 b
self-hosted:850 (22fd89d4e5b0 @ 454)
Taken from https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1897765/comments/38
This crash will also show up in the existing error buckets from bug
1897765:
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915681/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
