Bug 450029 - Broadcast RGB setting gets reset to Automatic after reboot
Summary: Broadcast RGB setting gets reset to Automatic after reboot
Status: RESOLVED DUPLICATE of bug 442520
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.24.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-11 18:04 UTC by Kamil Sołtysik
Modified: 2022-02-11 19:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kamil Sołtysik 2022-02-11 18:04:24 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
I have i915 as a driver and hence having wide range of colors by default is definitely not for me. In KDE however there's a RGB range option in Display settings applet which, in my case should be manually set to Full (it's Automatic by default, which probably means "whatever driver decides in its wisdom"). The option can also be set by kscreen-doctor:
kscreen-doctor 'output.thescreenname.rgbrange.full

The option however keeps getting reset to Automatic after rebooting - it doesnt matter if I set it through the applet or kscreen-doctor.
Moreover, if I use libdrm's proptest to set properties of connectors so the option is set even in ttys, after starting KDE, I still get reverted to Automatic on it.

STEPS TO REPRODUCE
1. Have i915 & a screen connected with HDMI
2. Set RGB range to Full in Display settings
3. Reboot

OBSERVED RESULT
Washed colors.

EXPECTED RESULT
Colorful colors.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Arch, latest
KDE Plasma Version: 5.24.0-1
KDE Frameworks Version: 5.90.0-1
Qt Version: 5.15.2+kde+r297-2

ADDITIONAL INFORMATION
Comment 1 Patrick Silva 2022-02-11 19:46:04 UTC

*** This bug has been marked as a duplicate of bug 442520 ***