Fix verified on Noble using mutter 46.2-1ubuntu0.24.04.2 and the test plan at the top of this page.
** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- 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/2025006 Title: Monitor colour profile is randomly not applied Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Committed Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] Colour profiles fail to apply at random times in Wayland sessions. Either when enabled in Settings>Color, or when logging into a new session. [ Workaround ] Switch VTs away and back to your login, usually with Ctrl+Alt+F3, Ctrl+Alt+F2. The correct colour profile is now more likely to be applied. [ Test Plan ] 1. Log into a Wayland session. 2. Open Settings > Color. 3. Select your primary monitor and 'Add profile'. 4. Add a whole-screen profile that will visibly change the screen like 'D50'. 5. Verify the new profile does not have the ⓘ icon next to it. 6. Repeatedly swap between enabling the new file, and enabling the old automatic profile. 7. Verify the screen colour temperature changes EVERY TIME that the ✓ check mark moves. [ Where problems could occur ] KMS property management in Wayland sessions has been redesigned for this fix, which includes colour management, night light, and hardware privacy screens. So there is a risk of unexpected behaviour in any of those features. Since KMS properties are applied atomically on most machines, this could also affect screen refresh performance. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2025006/+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
