Note to self: One possible explanation here is that we're setting this twice in the same commit, which some drivers might reject(?):
Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting connector 79 (/dev/dri/card0) property 'CRTC_ID' (20) to 0 Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting connector 79 (/dev/dri/card0) property 'CRTC_ID' (20) to 45 Another possible cause might be a bad size in: Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting CRTC (45, /dev/dri/card0) gamma, size: 256 Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting CRTC 45 (/dev/dri/card0) property 'GAMMA_LUT' (28) to 97 Although that doesn't explain all instances of the error. Also curious that I don't see any confirmed cases of this bug in 22.10 and later. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
