| Summary: | Black screen when turning HDR On in display settings for Samsung Q80T TV when TV Game Mode is Off, since plasma 6.4 | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | 0RF30 <n0v0x> |
| Component: | colour-management | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | n0v0x, nate, xaver.hugl |
| Priority: | NOR | Keywords: | regression |
| Version First Reported In: | 6.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/kwin/-/commit/7fc87b91dbc69bd9935211589ba3c84717269d58 | Version Fixed In: | 6.4.2 |
| Sentry Crash Report: | |||
| Attachments: |
drm_info tv game mode off
kscreen-doctor -o tv game mode off edid.bin tv game mode off drm_info tv game mode on kscreen doctor -o tv game mode on edid.bin tv game mode on |
||
|
Description
0RF30
2025-06-24 06:39:52 UTC
Please attach the output of > drm_info > kscreen-doctor -o and > cat /sys/class/drm/card1-HDMI-A-1/edid > edid.bin (connector name may need adjusting), once for when game mode is on, and once for when it's off. If you don't have a second screen and need to run it through ssh, you can prepend WAYLAND_DISPLAY=wayland-0 before kscreen-doctor to make it work. (In reply to Zamundaaa from comment #1) > Please attach the output of > > drm_info > > kscreen-doctor -o > and > > cat /sys/class/drm/card1-HDMI-A-1/edid > edid.bin > (connector name may need adjusting), once for when game mode is on, and once > for when it's off. > > If you don't have a second screen and need to run it through ssh, you can > prepend WAYLAND_DISPLAY=wayland-0 before kscreen-doctor to make it work. For game mode off, I assume that's without enabling HDR in plasma (since I can't), but what about game mode on ? Do you want these outputs with or without HDR enabled ? No, I need it with HDR on in both cases. Created attachment 182729 [details]
drm_info tv game mode off
Created attachment 182730 [details]
kscreen-doctor -o tv game mode off
Created attachment 182731 [details]
edid.bin tv game mode off
Created attachment 182732 [details]
drm_info tv game mode on
Created attachment 182733 [details]
kscreen doctor -o tv game mode on
Created attachment 182734 [details]
edid.bin tv game mode on
(In reply to Zamundaaa from comment #3) > No, I need it with HDR on in both cases. Done. Thanks for looking at it. A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/7838 Don't know how you managed to set the peak brightness override to zero, but that looks to be the problem, and the MR will guard against it. Until that's in, deleting the "maxPeakBrightnessOverride": 0 line from ~/.config/kwinoutputconfig.json should fix it. Note that KWin saves its cached config when quitting, so you'll need to either edit the file while not logged in, or kill kwin with "killall -9 kwin_wayland" after making the change Git commit a98fa02d91b40aeb7c7a5253625d93fb1ee705b2 by Xaver Hugl. Committed on 27/06/2025 at 16:02. Pushed by zamundaaa into branch 'master'. output management: add some safe guards for invalid brightness overrides Apparently it's somehow possible to set a max peak brightness override of zero, which makes it impossible to display anything. M +8 -0 src/outputconfigurationstore.cpp M +8 -0 src/wayland/outputmanagement_v2.cpp https://invent.kde.org/plasma/kwin/-/commit/a98fa02d91b40aeb7c7a5253625d93fb1ee705b2 (In reply to Zamundaaa from comment #12) > Don't know how you managed to set the peak brightness override to zero, but > that looks to be the problem, and the MR will guard against it. > > Until that's in, deleting the > "maxPeakBrightnessOverride": 0 > line from ~/.config/kwinoutputconfig.json should fix it. > > Note that KWin saves its cached config when quitting, so you'll need to > either edit the file while not logged in, or kill kwin with "killall -9 > kwin_wayland" after making the change That did the trick, thank you. No idea on how it happens though. It was fine before I update to plasma 6.4 (from 6.3.5), and I had the issue immediately after. Git commit a5515e1396fb0b459cab7416dbe70e91757f6f0b by Xaver Hugl, on behalf of Xaver Hugl. Committed on 27/06/2025 at 20:50. Pushed by zamundaaa into branch 'Plasma/6.4'. output management: add some safe guards for invalid brightness overrides Apparently it's somehow possible to set a max peak brightness override of zero, which makes it impossible to display anything. (cherry picked from commit a98fa02d91b40aeb7c7a5253625d93fb1ee705b2) Co-authored-by: Xaver Hugl <xaver.hugl@kde.org> M +8 -0 src/outputconfigurationstore.cpp M +8 -0 src/wayland/outputmanagement_v2.cpp https://invent.kde.org/plasma/kwin/-/commit/a5515e1396fb0b459cab7416dbe70e91757f6f0b Git commit 7fc87b91dbc69bd9935211589ba3c84717269d58 by Xaver Hugl, on behalf of Xaver Hugl. Committed on 27/06/2025 at 20:50. Pushed by zamundaaa into branch 'Plasma/6.3'. output management: add some safe guards for invalid brightness overrides Apparently it's somehow possible to set a max peak brightness override of zero, which makes it impossible to display anything. (cherry picked from commit a98fa02d91b40aeb7c7a5253625d93fb1ee705b2) Co-authored-by: Xaver Hugl <xaver.hugl@kde.org> M +8 -0 src/outputconfigurationstore.cpp M +8 -0 src/wayland/outputmanagement_v2.cpp https://invent.kde.org/plasma/kwin/-/commit/7fc87b91dbc69bd9935211589ba3c84717269d58 |