https://bugs.kde.org/show_bug.cgi?id=442520
--- Comment #34 from Mrcuve0 <mrcuve0+...@posteo.net> --- I added "export QT_LOGGING_RULES="kwin_*.debug=true" as suggested, removed the log and rebooted to reach a clean state. I recorded 4 different logs for the 4 subsequent actions done: * 00a: shows the initial state of the log, the screen is on Automatic and no preference has been set yet * 00b: the log records the instant when I switch from Automatic to Full, before logout *** LOGOUT *** * 01a: shows the state after logout, the screen is back in Automatic mode * 01b: I switch again from Automatic to Full, the log records this action Points of Interest I noticed using diff: --> Comparison among 00b and 01a (logout happens in between): * Line 7: The properties of Crtc 60 change (why?) * Line 70: The properties of connector 77 change (why?) * Line 71: Connector 85 (crtc 60) goes from Automatic to Full * Line 74 and 75: The two hex addresses changes (IDs?) * Line 421 in 01a sets the RGB range to Automatic --> Comparison among 01a and 01b: * Line 522: the RGB range is set to Full ------- I didn't find any "kwin_wayland_drm: Atomic test for (0) failed! Invalid argument" string in these logs, however we can find on line 4: "kwin_wayland_drm: Using Atomic Mode Setting on gpu "/dev/dri/card0" So I guess the error does not produce in my case (?) -- You are receiving this mail because: You are watching all bug changes.
