** This bug is no longer a duplicate of bug 1970917
gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor
|| g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager),
window->monitor)" in meta_window_update_for_monitors_changed()
--
You received this
*** This bug is a duplicate of bug 1970917 ***
https://bugs.launchpad.net/bugs/1970917
Since the release of jammy,
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
has either been showing bug 1970917 (if the last crash report was from
jammy), or no usable stack
Yes it has changed again. Back to having an unusable stack trace:
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
So this bug is invalid. It's going to keep jumping between different
stack traces due to issues with errors.ubuntu.com.
** This bug is no longer a
*** This bug is a duplicate of bug 1868293 ***
https://bugs.launchpad.net/bugs/1868293
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
is currently showing a stack trace that matches bug 1868293. Although if
it changes again (due to limitations/bugs in
This is the most common gnome-shell crash in jammy that has a partial
stack trace but it's still not enough information. We also can't read
any of the associated journal logs due to bug 1962454.
Judging by similar crashes like bug 1962817 I would say most instances
of this crash are going to be
