This bug was fixed in the package mutter - 49~rc-0ubuntu2
---------------
mutter (49~rc-0ubuntu2) questing; urgency=medium
* debian/control:
- Break on gnome-shell versions prior to 49~rc only
- Set version on libglycin-2-dev dependency
- Add libglycin-2-dev dependency to libmutter-17-dev
* debian/libmutter-17-0.symbols: Drop ubuntu version from symbols file
mutter (49~rc-0ubuntu1) questing; urgency=medium
[ Daniel van Vugt ]
* New upstream release 49.rc (LP: #2079823, LP: #2120628, LP: #2121517, LP:
#2085423)
* Added new script 'gnome-service-client' to 'mutter-common'.
* Replaced 'libgdk-pixbuf-2.0-dev' dependency with 'libglycin-2-dev'.
* Added 'libadwaita-1-dev' dependency for the devkit.
* Updated 'libmutter-17-0.symbols' and 'libmutter-test-17.symbols' for 49.rc
* Refreshed debian/patches:
- workarounds/Mark-several-additional-tests-as-flaky.patch
- workarounds/tests-Install-stacking-tests-into-a-subdirectory.patch
-
workarounds/tests-Mark-view-verification-tests-as-incomplete-in-big-e.patch
- ubuntu/window-Add-ability-to-override-the-edge-constraints.patch
* Drop upstreamed debian/patches:
- ubuntu/clutter-stage-Allow-for-there-being-no-sprite-when-a-devi.patch
- ubuntu/core-place-Guarantee-we-never-get-work-area-for-a-NULL-lo.patch
- ubuntu/monitor-Calculate-fractional-scaling-factors-using-exact-.patch
* Add debian/patches for the current top crasher (LP: #2121195):
- ubuntu/clutter-Add-function-clutter_frame_clock_get_frame_count.patch
- ubuntu/compositor-Don-t-assume-there-s-an-active-ClutterFrame-du.patch
* debian/control: libmutter-17-0 now breaks gnome-shell<<49~rc due to
some clutter symbols being removed.
-- Marco Trevisan (Treviño) <[email protected]> Wed, 03 Sep 2025
08:04:09 +0200
** Also affects: mutter (Ubuntu Noble)
Importance: Undecided
Status: New
** Description changed:
+ [ Impact ]
+
There is something wrong in the logic of Privacy screen enabled /
disabled message, since it seems to be the wrong way around.
Initially when logging in, there is a popup is shown about it being
disabled. Then when one presses Fn+D for the first time, the privacy
screen (Lenovo PrivacyGuard) is correctly enabled, but without a popup
displayed. After that, it continues to show but the wrong way around -
second Fn+D disables the privacy screen but the popup states it was
enabled, and third Fn+D enables the privacy screen but the popup states
it was disabled, and so on.
+
+ [ Test case ]
+
+ In a laptop with privacy screen:
+ - Enable the privacy screen with the hotkey (Ctrl+D on thinkpads)
+ => The OSD should notify the user about the Enabled state
+ - Hit the privacy screen hotkey again
+ => The OSD should notify the user about the Disabled state
+
+ [ Regression potential ]
+
+ The privacy screen controlled by Settings may not respect the actual
+ state
** Changed in: mutter (Ubuntu)
Status: New => Fix Released
** Changed in: mutter (Ubuntu Noble)
Status: New => Fix Committed
** Tags added: fixed-in-mutter-49.rc
** Changed in: mutter (Ubuntu)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: mutter (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
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/2085423
Title:
"Privacy screen enabled" / "disabled" the wrong way on Ubuntu 24.04
LTS
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Noble:
Fix Committed
Bug description:
[ Impact ]
There is something wrong in the logic of Privacy screen enabled /
disabled message, since it seems to be the wrong way around.
Initially when logging in, there is a popup is shown about it being
disabled. Then when one presses Fn+D for the first time, the privacy
screen (Lenovo PrivacyGuard) is correctly enabled, but without a popup
displayed. After that, it continues to show but the wrong way around -
second Fn+D disables the privacy screen but the popup states it was
enabled, and third Fn+D enables the privacy screen but the popup
states it was disabled, and so on.
[ Test case ]
In a laptop with privacy screen:
- Enable the privacy screen with the hotkey (Ctrl+D on thinkpads)
=> The OSD should notify the user about the Enabled state
- Hit the privacy screen hotkey again
=> The OSD should notify the user about the Disabled state
[ Regression potential ]
The privacy screen controlled by Settings may not respect the actual
state
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2085423/+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
