This bug was fixed in the package mutter - 49~alpha.1-0ubuntu6
---------------
mutter (49~alpha.1-0ubuntu6) questing; urgency=medium
[ Daniel van Vugt ]
* debian/control: Restore mutter-17-tests Depends: umockdev
mutter (49~alpha.1-0ubuntu5) questing; urgency=medium
[ Daniel van Vugt ]
* debian/control: Drop new binary dependency on umockdev. It's very
weak (043efbb1831) and an unnecessary blocker being in universe.
* debian/libmutter-17-0.lintian-overrides: Fix outdated reference to
libmutter-16.
mutter (49~alpha.1-0ubuntu4) questing; urgency=medium
[ Marco Trevisan (Treviño) ]
* Merge with debian
* d/control: Add misisng ${misc:Depends} to mutter-dev-bin
* d/source/lintian-overrides: Drop unhandled and outdated line
* d/p/ubuntu: Enable window edge constraint override support again
* d/control: Add missing mutter-17-tests gio runtime dependencies
* d/control: Add new mutter-17-tests umockdev runtime dependency
mutter (49~alpha.1-0ubuntu3) questing; urgency=medium
* debian/patches: Mark more tests as flaky for 49.alpha. These issues
have been reported upstream.
mutter (49~alpha.1-0ubuntu2) questing; urgency=medium
* debian/control: Add umockdev build dep in addition to libumockdev-
dev.
mutter (49~alpha.1-0ubuntu1) questing; urgency=medium
* New upstream release 49.alpha.1 (LP: #1968901, LP: #2100243, LP: #2102063)
* Drop Xorg-specific patches:
- clutter-Repick-actors-when-touches-emulate-button-clicks.patch
- x11-Add-support-for-fractional-scaling-using-Randr.patch
* Drop upstreamed patches:
- wayland-xdg-shell-Check-popup-resource-for-parent-unmappe.patch
- wayland-xdg-shell-Check-for-NULL-xdg_popup-resource.patch
- cursor-drag-and-drop.patch
- cursor-sprite-xcursor-Reset-current_frame-only-if-xcursor.patch
- Use-access-instead-of-checking-permission-modes-for-tmp-..patch
* Refresh patches:
- tests-Do-not-run-screencast-tests.patch
- Mark-several-additional-tests-as-flaky.patch
- tests-Install-stacking-tests-into-a-subdirectory.patch
* Disable patch: window-Add-ability-to-override-the-edge-constraints.patch
because it doesn't apply anymore and its existence not fully explained.
It can't be Ubuntu-specific if in support of Tiling Assistant which is
not Ubuntu-specific. Needs to be proposed upstream if required at all.
* Added new binary package 'mutter-dev-bin' for the missing 'mutter-devkit'
binary. Four years late.
* Bump the Mutter API/ABI to 17.
mutter (48.4-1) experimental; urgency=medium
[ Jeremy Bícha ]
* New upstream bugfix release
- Unlink outputs from unused connectors in update_outputs
- Add speed limit to Visual alerts
- Fix behavior of windows that get activated before mapped
- Fix incorrect cursor over Xwayland clients (LP: #2111502)
- Fix hi-res scroll events getting converted to flip-flopping discrete
events
- Fixed crash
[ Simon McVittie ]
* d/gbp.conf: Use upstream/48.x branch for trixie
* d/watch: Only watch for 48.x releases
-- Daniel van Vugt <daniel.van.v...@canonical.com> Fri, 18 Jul 2025
12:41:33 +0800
** Changed in: mutter (Ubuntu Questing)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2102063
Title:
gnome-shell crashed with SIGSEGV in
_cogl_pipeline_layer_numbers_equal() from
compare_entry_layer_numbers()
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Plucky:
Fix Released
Status in mutter source package in Questing:
Fix Released
Bug description:
[ Impact ]
If many notifications have accumulated, GNOME Shell will crash and log
out the user when clicking the "Clear" button to dismiss all
notifications.
The root cause of the bug is a classic case of removing elements from
a linked-list while iterating over it unsafely, during the composition
rendering pass.
[ Test plan ]
1. Spawn many notifications:
$ for run in {1..20}; do notify-send foo; done
2. Open the calendar menu
3. Click "Clear"
4. Verify that all notifications were dismissed
5. Verify that GNOME Shell did not crash and log you out
[ Where problems could occur ]
mutter is the component of GNOME driving the screen and inputs, and
thus is a critical component of Ubuntu Desktop.
Problems would manifest with the desktop rendering incorrectly or
crashing.
The side-effects being very evident and the patch being trivial make
this upload a low risk for regressions.
[ Other information ]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
48~beta-3ubuntu1, the problem page at
https://errors.ubuntu.com/problem/c840a93998fc1f3edb39a0c0ed8682215c9e5f63
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2102063/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
