This bug was fixed in the package mutter - 46.2-1ubuntu0.24.04.1
---------------
mutter (46.2-1ubuntu0.24.04.1) noble; urgency=medium
[ Daniel van Vugt ]
* New upstream release 46.2 (LP: #2068598)
- Fixed mouse clicks falling through to the window behind (LP: #2026194)
- Fixed a crash in meta_wayland_transaction_commit (LP: #2061739)
- Fixed night light getting stuck on (LP: #2066902)
* New upstream release 46.1 (LP: #2064735):
- Fixed blank screen on hybrid GPU machines using nouveau (LP: #2066931)
- Fixed a monitor hotplug crash (LP: #2050865)
- Improved performance on secondary GPU monitors (LP: #2038801)
* Refreshed patches:
- Support-Dynamic-triple-double-buffering.patch (LP: #2070437, LP: #2070438)
- meson-Do-not-mark-CI-test-tools-as-required.patch
- Mark-several-additional-tests-as-flaky.patch
* Add clutter/conform gesture tests to the list of known flaky ones:
it's a new test in Mutter 46 and not yet reliable.
* Add build-Compile-schemas-locally-for-use-in-build-tests.patch to compile
gsettings schemas for use in build tests. Debian CI requires this now and
it makes rebuilds more resilient against infrastructure changes.
* Add wayland-Disable-linux-drm-syncobj-v1.patch to avoid enabling major
new features in Noble updates, as detailed in:
https://lists.ubuntu.com/archives/ubuntu-release/2024-May/006087.html
* Add backends-Handle-null-views-instead-of-creating-dummy-view.patch
to prevent "clutter_frame_clock_notify_presented: code should not be
reached" log spam in some Nvidia Wayland sessions (LP: #1967707)
* Add backends-Restore-support-for-X11-cursor-themes.patch to restore
support for X11 cursor themes, which was lost in Mutter 46.0
(LP: #2062377, LP: #2063869)
[ Jeremy Bícha ]
* Stop compiling gsettings schemas in debian/rules
* Opt into Salsa CI
* Drop packaging references to Hurd since this is Linux-only
* Update libmutter-14-0.symbols
* Update Breaks
* Refreshed patches:
- window-Add-ability-to-override-the-edge-constraints.patch
- x11-Add-support-for-fractional-scaling-using-Randr.patch
* Drop upstreamed patches:
- Nvidia-secondary-GPU-copy-acceleration.patch
- compositor-sync-ring-Allow-the-gpu_fence-to-be-moved.patch
[ Marco Trevisan ]
* Add place-Always-center-initial-setup.patch (LP: #2016013)
-- Daniel van Vugt <[email protected]> Fri, 28 Jun 2024
17:35:12 +0800
** Changed in: mutter (Ubuntu Noble)
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/2016013
Title:
gnome-initial-setup doesn't get centered if Desktop Icons NG is loaded
in a Wayland session
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
Won't Fix
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Noble:
Fix Released
Status in mutter source package in Oracular:
Fix Released
Bug description:
[ Impact ]
New windows don't get centered if Desktop Icons NG is loaded.
With vanilla GNOME, if an app window is too large for tiling (larger
than a quarter of the screen) then it will be centered by default. But
this doesn't happen when DING is loaded, probably because DING is
incorrectly treated as an app window.
The scope of this bug has now been reduced to only cover gnome-
initial-setup.
[ Test Plan ]
1. Log into a Wayland session.
2. Run: sudo apt install gnome-initial-setup
3. Run: /usr/libexec/gnome-initial-setup --existing-user
4. Verify: The window is centered.
[ Where problems could occur ]
Anywhere in window placement when a new window opens.
[ Other Info ]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+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
