https://bugs.kde.org/show_bug.cgi?id=503532
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from [email protected] --- OK, this is not a kcm issue, but I would appreciate if you could help it categorize this properly. TLDR: changing this property for me does something that kwin can't recover from. KCM probably does offer to back out, but it can't when the time comes. I've tested this this way: $ kscreen-doctor output.DP-2.colorPowerTradeoff.preferAccuracy This sends the KWin session in a death spiral (for me). There is no video output. The picture appears frozen, but it's just showing whatever was last on the screens, switching to a text console and back then shows it frozen with what was last displayed on the text console. The logs are littered with this output: May 01 12:44:05 druid kwin_wayland[337695]: kwin_wayland_drm: Atomic modeset commit failed! Invalid argument May 01 12:44:05 druid kernel: HDR SB:3a 3d 47 40 09 01 03 00 09 01 09 01 00 00 00 00 May 01 12:44:05 druid kernel: HDR SB:01 1a 02 00 84 85 82 3b af 2f 79 8a 0a 1c df 0a May 01 12:44:05 druid kernel: HDR SB:3a 3d 47 40 09 01 03 00 09 01 09 01 00 00 00 00 May 01 12:44:05 druid kernel: HDR SB:01 1a 02 00 84 85 82 3b af 2f 79 8a 0a 1c df 0a May 01 12:44:05 druid kernel: HDR SB:3a 3d 47 40 09 01 03 00 09 01 09 01 00 00 00 00 May 01 12:44:05 druid kernel: HDR SB:01 1a 02 00 84 85 82 3b af 2f 79 8a 0a 1c df 0a May 01 12:44:05 druid kernel: HDR SB:3a 3d 47 40 09 01 03 00 09 01 09 01 00 00 00 00 May 01 12:44:05 druid kernel: HDR SB:01 1a 02 00 84 85 82 3b af 2f 79 8a 0a 1c df 0a May 01 12:44:05 druid kwin_wayland[337695]: kwin_core: Applying output config failed! Just repeating over and over, nothing else there that I can see. Attempting to "back out" doesn't work from kscreen-doctor: $ kscreen-doctor output.DP-2.colorPowerTradeoff.preferEfficiency applying config failed! The driver rejected the output configuration May 01 13:03:58 druid kwin_wayland[343847]: kwin_core: Applying output config failed! May 01 13:03:57 druid kwin_wayland[343847]: kwin_wayland_drm: drmModeListLessees() failed: Permission denied At this point, the only way to "fix" the situation (that I found) is to stop kwin, edit ~/.config/kwinoutputconfig.json to restore the value, and restart kwin. The "drmModeListLessees() failed: Permission denied" happens when I try to change the color accuracy to any value, bad or good, whether kwin runs or not, as long as kwin session is not on screen. I.e., it changes if I type it from a terminal in a kwin session, but fails with this error if I do it from a console terminal. This sounds to me that kscreen-doctor is asking kwin to apply the output changes, whether it's actually running the outputs or not, instead of asking it to apply the changes once it regains controls of the output. But that doesn't explain why kcm can't back out then, because I certainly waited for >15sec after making that change from kcm, and kept my vterm on kwin session during that time. OK, so I did this: from a terminal window in a kwin session: $ kscreen-doctor output.DP-2.colorPowerTradeoff.preferAccuracy ; sleep 5; kscreen-doctor output.DP-2.colorPowerTradeoff.preferEfficiency It still didn't recover (OK, so kcm would not be able to either): kscreen-doctor outpu: applying config failed! The driver rejected the output configuration logs: kwin_core: Applying output config failed! This time just that, no permission denied, no other messages whatsoever. -- You are receiving this mail because: You are watching all bug changes.
