Bug 455082 - Full RGB range resets to 'Automatic' after login to X11, logout and login to Wayland
Summary: Full RGB range resets to 'Automatic' after login to X11, logout and login to ...
Status: RESOLVED FIXED
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.27.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-09 13:52 UTC by Patrick Silva
Modified: 2023-10-07 01:53 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2022-06-09 13:52:20 UTC
STEPS TO REPRODUCE
1. use Wayland session
2. set RGB range to 'Full' in Display Configuration KCM
3. logout
4. login to Plasma X11 session
5. logout
6. login to Plasma Wayland session

OBSERVED RESULT
RGB range was reset to 'Automatic' in Display Configuration KCM

EXPECTED RESULT
RGB range setting should never be lost

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.90
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Graphics Platform: Wayland
Comment 1 Bug Janitor Service 2022-11-07 23:33:31 UTC
Thank you for the bug report!

Please note that Plasma 5.25.90 is not supported for much longer by KDE; supported versions are 5.24, and 5.26 or newer.

If at all possible please upgrade to a supported version and verify that the bug is still happening there.

If you're unsure how to do this, contact your distributor about it.
Comment 2 Nate Graham 2022-11-12 15:08:46 UTC
Is the setting itself changed? Or does the KCM simply display the wrong value?
Comment 3 Patrick Silva 2022-11-12 15:10:40 UTC
The setting itself changes.
Comment 4 Nate Graham 2022-11-12 15:23:27 UTC
Thanks.

Ohh... it resets when you switch between X11 and Wayland? Does it reset when you restart from X11 into X11, or from Wayland into Wayland?

If those work, can you please paste the output of `kcsreen-doctor -o` before and after reproducing the bug by rebooting into another session type?
Comment 5 Patrick Silva 2022-11-12 23:27:06 UTC
output before reproducing the bug:

[01;32mOutput: [0;0m1 LG Electronics HDMI-A-1-23MP55 [01;32menabled [01;32mconnected [01;32mprimary [01;33mHDMI[01;34m Modes: [0;0m0:[01;32m1920x1080@60*[0;0m! 1:1920x1080@60 2:1920x1080@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@60 6:1920x1080@50 7:1920x1080@50 8:1680x1050@60 9:1400x1050@60 10:1600x900@60 11:1280x1024@60 12:1440x900@60 13:1280x800@60 14:1280x720@60 15:1280x720@60 16:1280x720@60 17:1280x720@50 18:1024x768@60 19:800x600@60 20:720x576@50 21:720x480@60 22:720x480@60 23:720x480@60 24:720x480@60 25:640x480@60 26:640x480@60 27:640x480@60 [01;33mGeometry: [0;0m0,0 1920x1080 [01;33mScale: [0;0m1 [01;33mRotation: [0;0m1 [01;33mOverscan: [0;0m0 [01;33mVrr: [0;0mincapable [01;33mRgbRange: [0;0mFull [01;34mprimary[0;0m

output after reproducing the bug:

[01;32mOutput: [0;0m1 LG Electronics HDMI-A-1-23MP55 [01;32menabled [01;32mconnected [01;32mprimary [01;33mHDMI[01;34m Modes: [0;0m0:[01;32m1920x1080@60*[0;0m! 1:1920x1080@60 2:1920x1080@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@60 6:1920x1080@50 7:1920x1080@50 8:1680x1050@60 9:1400x1050@60 10:1600x900@60 11:1280x1024@60 12:1440x900@60 13:1280x800@60 14:1280x720@60 15:1280x720@60 16:1280x720@60 17:1280x720@50 18:1024x768@60 19:800x600@60 20:720x576@50 21:720x480@60 22:720x480@60 23:720x480@60 24:720x480@60 25:640x480@60 26:640x480@60 27:640x480@60 [01;33mGeometry: [0;0m0,0 1920x1080 [01;33mScale: [0;0m1 [01;33mRotation: [0;0m1 [01;33mOverscan: [0;0m0 [01;33mVrr: [0;0mincapable [01;33mRgbRange: [0;0mAutomatic [01;34mprimary[0;0m
Comment 6 Nate Graham 2022-11-14 19:07:21 UTC
Thanks! Does not look like this is an occurrence of Bug 429236, since the connector IDs are the same in both.
Comment 7 NW 2023-06-08 19:50:51 UTC
Hi,

Also noticed this issue.

(In reply to Nate Graham from comment #4)
> Ohh... it resets when you switch between X11 and Wayland?

Correct.

(In reply to Nate Graham from comment #4)
> Does it reset when
> you restart from X11 into X11, or from Wayland into Wayland?

No. When only using Wayland, the issue does not occur.

Which means it essentially would only be an issue for users which regularly switch between Wayland and X.

Regards
Comment 8 Zamundaaa 2023-10-05 19:41:58 UTC
Git commit ae84480fbfdc684b8ee4b0207d3ce679f6fb4cd7 by Xaver Hugl.
Committed on 05/10/2023 at 20:29.
Pushed by zamundaaa into branch 'master'.

outputconfigurationstore: add new config system

Instead of an external service (like KScreen) storing and restoring output configurations,
with this commit KWin takes over that responsibility. This allows it to, among other things,
generate appropriate configs for new sets of outputs immediately, and take KWin-internal information
about outputs into account when generating them.
Related: bug 466208, bug 457430, bug 474021, bug 469653, bug 466342, bug 470863, bug 466556

M  +1    -0    CMakeLists.txt
M  +1    -0    autotests/integration/kwin_wayland_test.cpp
M  +1    -0    src/CMakeLists.txt
M  +5    -0    src/backends/drm/drm_output.cpp
M  +9    -0    src/core/output.cpp
M  +11   -0    src/core/output.h
M  +1    -0    src/core/outputconfiguration.h
M  +7    -0    src/main.cpp
M  +1    -0    src/main.h
M  +0    -4    src/main_wayland.cpp
M  +709  -20   src/outputconfigurationstore.cpp
M  +68   -4    src/outputconfigurationstore.h
M  +1    -0    src/utils/CMakeLists.txt
M  +8    -0    src/utils/edid.cpp
M  +8    -0    src/utils/edid.h
A  +54   -0    src/utils/orientationsensor.cpp     [License: GPL(v2.0+)]
A  +38   -0    src/utils/orientationsensor.h     [License: GPL(v2.0+)]
M  +34   -1    src/wayland/outputdevice_v2.cpp
M  +1    -0    src/wayland/outputdevice_v2.h
M  +12   -1    src/wayland/outputmanagement_v2.cpp
M  +49   -6    src/workspace.cpp
M  +2    -0    src/workspace.h

https://invent.kde.org/plasma/kwin/-/commit/ae84480fbfdc684b8ee4b0207d3ce679f6fb4cd7