HDR Toggle vanished from system settings

Since Plasma 6.2, the HDR toggle has disappeared from the system settings page for my monitor. It was there under 6.1.

kscreeen-doctor shows HDR: disabled on this monitor (I know my second monitor is incapable of HDR).

[solarisfire@solaris-arion udpSender]$ kscreen-doctor -o
Output: 1 DP-1
       enabled
       connected
       priority 1
       DisplayPort
       Modes:  1:3840x1080@120!  2:5120x1440@120*  3:5120x1440@100  4:5120x1440@60  5:3840x1080@100  6:3840x1080@60  7:2560x1440@60  8:2560x1080@120  9:2560x1080@100  10:2560x1080@60  11:2560x1080@60  12:1920x1080@120  13:1920x1080@100  14:1920x1080@60  15:1920x1080@60  16:1680x1050@60  17:1600x900@60  18:1280x1024@75  19:1280x1024@60  20:1440x900@60  21:1280x800@60  22:1152x864@75  23:1280x720@60  24:1024x768@75  25:1024x768@70  26:1024x768@60  27:800x600@75  28:800x600@72  29:800x600@60  30:800x600@56  31:640x480@75  32:640x480@73  33:640x480@60 
       Geometry: 0,1011 5120x1440
       Scale: 1
       Rotation: 1
       Overscan: 0
       Vrr: Automatic
       RgbRange: unknown
       HDR: disabled
       Wide Color Gamut: incapable
       ICC profile: none
       Color profile source: EDID
       Brightness control: supported, set to 30%
Output: 2 DP-2
       enabled
       connected
       priority 2
       DisplayPort
       Modes:  34:2560x1440@60!  35:2560x1440@144*  36:2560x1440@120  37:2560x1440@100  38:2560x1440@85  39:2560x1440@24  40:1024x768@60  41:800x600@60  42:640x480@60 
       Geometry: 5120,0 1440x2560
       Scale: 1
       Rotation: 2
       Overscan: 0
       Vrr: Automatic
       RgbRange: unknown
       HDR: incapable
       Wide Color Gamut: incapable
       ICC profile: none
       Color profile source: EDID
       Brightness control: supported, set to 30%

Same thing for me, but I haven’t updated since 6.2 was available on Arch, and just noticed it is missing.

Holy…
And I thought it is because it is still worked on the brightness control that the appearance slightly changed, but in reality it is HDR that is off.

kscreen-doctor reports in my case HDR: enabled for the particular Monitor that I had it enabled in the past, but just checked my monitors OSD and that tells me otherwise (HDR: OFF)

Same issue here on Manjaro running plasma-desktop 6.2.1-1. No HDR toggle in settings anymore and kscreen-doctor -o initially said disabled. I ran kscreen-doctor output.DP-2.hdr.enable from the docs and it now says enabled but the option is still not visible in the Settings app after a reboot.

Output: 1 DP-2
        enabled
        connected
        priority 1
        DisplayPort
        Modes:  1:3440x1440@60!  2:3440x1440@175*  3:3440x1440@144  4:3440x1440@120  5:3440x1440@100  6:1024x768@60  7:800x600@60  8:640x480@60 
        Geometry: 0,0 3440x1440
        Scale: 1
        Rotation: 1
        Overscan: 0
        Vrr: Automatic
        RgbRange: unknown
        HDR: enabled
                SDR brightness: 200 nits
                SDR gamut wideness: 0%
                Peak brightness: 1060 nits
                Max average brightness: 254 nits
                Min brightness: 0 nits
        Wide Color Gamut: incapable
        ICC profile: none
        Color profile source: sRGB
        Brightness control: supported, set to 100%

Monitor OSD still reports HDR being off however as noticed by M.Karrde.

The toggle was intentionally removed for NVidia users, because of a very severe driver bug that reportedly blocked a lot of people from even logging in after they enabled HDR. You can enable it again by putting KWIN_DRM_ALLOW_NVIDIA_COLORSPACE=1 into /etc/environment and rebooting

Note that you may experience that driver bug as well; if you do, removing that environment variable and rebooting should allow you to log in again.

4 Likes

Would it not have been better to leave the HDR toggle in place, but leave it greyed out to show it’s disabled, and had a tool-tip explaining the reasoning behind it?

1 Like

Sure, but this is a driver bug we quickly worked around. I didn’t intend to spend any more time on driver bugs than necessary; hopefully NVidia fixes it soon and we can just remove the workaround again.

1 Like

I dare say the 555/560 linux drivers are so broken (still, after nearly a year), particularly with KDE/Wayland, you might as well just warn users up front it simply won’t work right if they have Nvidia.

Nvidia 560.35.03 (With a GTX 3090) with KDE Plasma & Wayland have been working pretty darn perfectly for me the last few months actually :sweat_smile:

I thought Nvidia users were going to be stuck on X11 forever, but explicit sync really fixed things.

1 Like

Well that’s literally what I was hoping for, working Wayland for gaming, upgrading to Plasma 6.0 back in Jan/Feb time, and with 550 drivers it was still a hot mess of flickering for a large amount of apps let alone gaming with Steam Proton. I learned about the explicit sync mess and just stayed on x11, which I still am today.

I had hope for 555 fixing this, but watching the nvidia linux driver threads it seemed to break more than it fixed, particularly related to KDE and Proton/Wine games, and before even fixing that full 560 got dumped out to much of the same with all the old broken things plus more new. The threads here and here are still full of lots of broken users and few nvidia answers.

I suppose it’s probably different for everyone, and every distribution but using Arch, Plasma6/6.1, proton/wine, complaints seemed to match my general use case to simply avoid like the plague until I see some actual positive feedback. Now I’m just looking for a new laptop (with AMD).

Yours is I think the first I’ve seen of anything positive for 560 in linux. What distribution are you using?

All arch.

I install the drivers manually with the nvidia-all tool (GitHub - Frogging-Family/nvidia-all: Nvidia driver latest to 396 series AIO installer).

DKMS - Using the Open source kernel modules.

I have both the mainline and lts kernels and it works on both. I sit on mainline until I find something broken.

I have:

GRUB_CMDLINE_LINUX_DEFAULT=“loglevel=3 nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nowatchdog quiet splash” in my /etc/default/grub config.

Plasma 6.2.1

And I play steam games using proton all day long just as well as I would on Windows.

It also works fine for me using the same kernel parameters(nvidia_drm.modeset=1 nvidia_drm.fbdev=1) and manjaro with the 560 driver.

I have a 4090

Operating System: Manjaro Linux
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.4-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 32 Ă— AMD Ryzen 9 7950X3D 16-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670E AORUS PRO X
System Version: -CF

Before the update I was able to use HDR no problem.

6.2.1 has actually made things worse for me by disabling HDR and the stupid akonadi_migration_agent notfication that never goes away.

KWIN_DRM_ALLOW_NVIDIA_COLORSPACE=1 added to /etc/environment does nothing

Hey there, this solution worked to show the toggle again on my system.
However there’s a bug with it that may have been overlooked.

My HDR was enabled Prior to the update to KDE 6.2, and then the toggle was removed afterwards, but HDR was still enabled. You may want to ensure HDR get’s disabled afterwards if there are bugs with it.

Thanks!

Are you sure?
While KDE/kscreen-doctor claimed enabled, my Monitor (OSD) and the screen appearance told me disabled for sure.

Not to mention that if that bug is potentially triggered by enabling HDR, people that have already successful enabled HDR without triggering the bug would be fine, as shown by my now working HDR, I guess.

yes, this was fixed in 6.2.1.1

worked for me. toggle enables and disables HDR.

cat /proc/version
Linux version 6.11.5-200.fsync.fc40.x86_64 (mockbuild@3e74f1e93d7d4007b1a3acc031f555d1) (gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3), GNU ld version 2.41-37.fc40) #1 SMP PREEMPT_DYNAMIC TKG Tue Oct 29 17:53:22 UTC 2024