Upstream says the fix was probably in Mutter:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4544
But we're not really sure.
** Tags added: fixed-in-mutter-49.0
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Fix Released
** Changed in: mutter (Ubuntu)
Importance: Undecided => Medium
** Also affects: mutter (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: at-spi2-core (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: at-spi2-core (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Stonking)
Importance: Medium
Status: Fix Released
** Also affects: at-spi2-core (Ubuntu Stonking)
Importance: Medium
Status: Fix Released
** Also affects: mutter (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: at-spi2-core (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu Resolute)
Status: New => Fix Released
** Changed in: mutter (Ubuntu Questing)
Status: New => Fix Released
** Changed in: at-spi2-core (Ubuntu Resolute)
Status: New => Fix Released
** Changed in: at-spi2-core (Ubuntu Questing)
Status: New => Fix Released
** Changed in: at-spi2-core (Ubuntu Noble)
Status: New => Confirmed
** No longer affects: at-spi2-core (Ubuntu Noble)
** No longer affects: mutter (Ubuntu Noble)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106796
Title:
gnome-shell crashed with SIGSEGV in
g_type_check_instance_is_fundamentally_a() from g_object_unref() from
expiry_func() from g_timeout_dispatch() from g_main_dispatch()
To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/2106796/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
