Monitor colour profile is randomly not applied

[Daniel van Vugt]

[ 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 ]

[Daniel van Vugt (vanvugt)]

I went back and tested lunar on the same machine and there is no bug there even though lunar has 44.2 now. Makes me think this might be a kernel issue since mantic has 6.3 now.

[Daniel van Vugt (vanvugt)]

The same problem exists in Settings>Color. Changing the selected profile in the GUI doesn't always change the applied profile on screen.

It's now fixed in Mutter 47.0:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3912

[Daniel van Vugt (vanvugt)]

In review: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3929

[Robie Basak (racb)]

I'm rejecting two uploads for Noble because they collide between bug 2077746 and bug 2025006 (amongst others). Please coordinate and re-upload just one SRU at once (possibly squashing multiple fixes together as you wish).

[Daniel van Vugt (vanvugt)]

https://launchpadlibrarian.net/746352003/mutter_46.2-1ubuntu0.24.04.2_source.changes

[Launchpad Janitor (janitor)]

This bug was fixed in the package mutter - 47~rc-4ubuntu1

---------------
mutter (47~rc-4ubuntu1) oracular; urgency=medium

  [ Jeremy Bícha ]
  * Merge with Debian. Remaining changes:
    - Add x11-Add-support-for-fractional-scaling-using-Randr.patch
    - Add window-Add-ability-to-override-the-edge-constraints.patch
      + Make possible for extensions (such as Tiling Assistant) to override
        window constraints
    - Remove debian/salsa-ci.yml: Not helpful for us currently
  * Remove the cogl color patches: applied in new release
  * Remove the mesa workaround patch: shouldn't be needed any more
  * Cherry-pick resizing fix for various Electron apps (LP: #2080073)

  [ Marco Trevisan (Treviño) ]
  * d/p/x11-randr-scaling: Update to work with latest upstream changes
  * debian/control: Update VCS references to ubuntu branch

mutter (47~rc-4) experimental; urgency=medium

  * Team upload
  * d/mutter-15-tests.postrm: Clean up gschemas.compiled created by postinst

mutter (47~rc-3) experimental; urgency=medium

  * Team upload
  * d/p/workarounds, d/tests: Treat all stacking tests as flaky.
    Unfortunately these don't seem to be stable enough to be used as a
    QA gate, and there are enough of them that at least one will often
    fail in any given buildd build or autopkgtest run
    (Mitigates: #1077800) (Closes: #1072512, #1078359)
  * d/tests: Also treat thread.test as flaky.
    This doesn't seem to be reliable in autopkgtest-virt-qemu or -lxc,
    although I can't reproduce the failure when running it separately.
  * d/rules, d/p/workarounds: Don't run the input-capture test at all.
    In my sbuild environment and on some buildds, it often hangs until it
    times out after 10 minutes, which is a waste of time. We were ignoring
    its result anyway.
  * d/mutter-15-tests.postinst: Compile required schemas for installed-tests
    (Closes: #1081016)
  * d/p/tests-Add-a-utility-function-to-delete-a-directory-recurs.patch,
    d/p/MetaContextTest-Optionally-create-and-destroy-a-temporary.patch,
    d/p/color-management-tests-Use-a-temporary-XDG_DATA_HOME.patch,
    d/p/color-management-profile-conflict-test-Use-a-temporary-XD.patch:
    Add patches to fix autopkgtests when not running as root
  * Correct bug number in previous changelog entry
  * Standards-Version: 4.7.0 (no changes required)
  * d/source/lintian-overrides: Update for use of ${env:deb_udevdir}

mutter (47~rc-2) experimental; urgency=medium

  * debian/*symbols: Update architectures for new cogl_trace symbols
  * Have mutter-15-tests depend on pipewire & libglib2.0-bin
    (Closes: #1081016)
  * autopkgtest: create the required /tmp/.X11-unix/

mutter (47~rc-1) experimental; urgency=medium

  [ Jeremy Bícha ]
  * New upstream release (LP: #2077216, LP: #2025006, LP: #2074253,
    LP: #2076318)
    - Fix screen freeze when using EGL Stream (Nvidia-470) (LP: #2074254)
    - Only warn once about cursor sizes (LP: #2076211)
  * debian/libmutter-15-0.symbols: Update
  * Mark as breaking gnome-shell << 47~rc
  * Only enable sysprof on architectures where sysprof is available
  * Refresh patches
  * Remove the kms deadline evasion patch: alternative fix is in new release
...