this post was submitted on 11 Apr 2024

78 points (98.8% liked)

KDE

5331 readers

237 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago

MODERATORS

carlschwan@lemmy.kde.social

Bro666@lemmy.kde.social

herzenschein@pawb.social

Aniqakhokhar@lemmy.kde.social

How do I disable HDR? (lemmy.ml)

submitted 7 months ago* (last edited 7 months ago) by ByteBovine@lemmy.ml to c/kde@lemmy.kde.social

20 comments fedilink hide all child comments

So today I clicked 'enable HDR' on one of my monitors and something broke. The whole system froze up and the HDR monitor went black. If I reboot it freezes right after I login.

If I unplug that monitor or start in X11 instead of Wayland then everything is fine. Plugging the HDR monitor in while I'm logged into a Wayland session also freezes everything.

How can I disable the HDR setting? The monitor doesn't show in System Settings whilst its unplugged so I'm hoping theirs some way to fix it on the CLI. The only place I've found HDR referenced is .config/kwinoutputconfig.json. I set HDR to false but after reboot it's set to true again. I also tried deleting .config/kwinrc and .local/share/kscreen but no luck.

I'm fine with just resetting all Display settings if that's required.

----- UPDATE ------

Bug report filed here: https://bugs.kde.org/show_bug.cgi?id=485403

Fixed by

Ctrl + Alt + F3 to go into terminal
Set HighDynamicRange and WideColorGamut to false in ~/.config/kwinoutputconfig.json
Execute plasmashell --replace
Reboot, Login, Reattach HDR Monitor

------ UPDATE ------

After updating and trying again today the steps above no longer worked. You still need to change ~/.config/kwinoutputconfig.json but plasmashell --replace no longer works for me.

Running killall kwin_wayland also just bumps me from my terminal back into the desktop. kwin can't be running when you change that file or it will be overridden.

I booted into a separate Linux Live USB and change the files that way.

Thank you everyone for your help 🎉

all 21 comments

sorted by: hot top controversial new old

[–] Rustmilian@lemmy.world 32 points 7 months ago* (last edited 7 months ago) (1 children)

kscreen-doctor -o
Then adjust the below command accordingly :
kscreen-doctor output.1.hdr.disable

Make sure you go open a bug report.
When you do, you can use hw-probe and run :
sudo -E hw-probe -all -upload -dump-acpi -decode-acpi
And use the given link in your BR.

[–] ByteBovine@lemmy.ml 2 points 7 months ago (1 children)

The monitor does not display with kscreen-doctor -o as it's disconnected.

I will create a bug report.

[–] Rustmilian@lemmy.world 3 points 7 months ago* (last edited 7 months ago) (2 children)

I see you got it fixed.
When you run hw-prope make sure your offending monitor is connected. hw-prope will help identify the monitor by hardware ID which is used in various areas like kernel space and will help with identifying the exact model of the problem monitor hopefully allowing for devs to reproduce the bug in a lab environment.

[–] ByteBovine@lemmy.ml 2 points 7 months ago (2 children)

Added the hw-probe link

[–] Rustmilian@lemmy.world 3 points 7 months ago* (last edited 7 months ago)

Which one of these is the problem monitor? benq or gigabyte ?

Edit : nvm, I see you already said Gigabyte.

[–] Rustmilian@lemmy.world 3 points 7 months ago

Looking through the probe logs, and seeing that your monitor is using EISA bus and works fine without HDR, there doesn't appear to be any issues on the Linux side of things. My guess is that they didn't implement HDR on the monitors side exactly to spec and that's where the problem resides. So, in this sense some monitor specific quirk fixup code is needed on the Linux side of things to get it working properly. If the devs ask any additional steps from you, be sure to do it and provide feedback.

[–] Zamundaaa@discuss.tchncs.de 7 points 7 months ago* (last edited 7 months ago) (1 children)

Changing the output config file should work, as long as KWin isn't running while you make the change (in which case the change will just be overridden)

Edit: Also, please make a bug report about this for KWin. It's probably not a KWin issue, but we can usually figure out where it's coming from

[–] ByteBovine@lemmy.ml 4 points 7 months ago

This worked 👍 Thank you I also filed a bug report https://bugs.kde.org/show_bug.cgi?id=485403

[–] UnfortunateShort@lemmy.world 5 points 7 months ago* (last edited 7 months ago) (2 children)

Not an answer, but maybe the KDE folks should add "and may seriously break things" to the "is experimental" warning next to HDR :D

[–] Zamundaaa@discuss.tchncs.de 1 points 7 months ago

Almost every output setting "may seriously break things" in my experience. Display drivers are sadly quite fragile

[–] isVeryLoud@lemmy.ca 0 points 7 months ago

This is why GNOME hasn't implemented it yet, they want to wait until it's perfect and not experimental before adding the feature.

[–] possiblylinux127@lemmy.zip 1 points 7 months ago (1 children)

Wait, since when does KDE support HDR? Can you have HDR wallpapers?

[–] russjr08@bitforged.space 1 points 7 months ago (1 children)

Since Plasma 6. Not sure about HDR wallpapers (never even heard of an "HDR Wallpaper", so I've not looked into support for it), it should work with fullscreen videos though, and Steam games work if you run it through a nested gamescope session with a special HDR Vulkan layer installed.

[–] possiblylinux127@lemmy.zip 2 points 7 months ago (1 children)

I assume it will work for a live system? When Fedora 40 eventually comes out I'll give it a try. I can't stand to daily drive plasma unfortunately. (Gnome works better for me)

Maybe if it works well I'll run plasma on a media machine.

[–] russjr08@bitforged.space 1 points 7 months ago

It should, yep! It'll be in the Display Configuration if Plasma is properly detecting an HDR display.

[–] stuckgum@lemmy.ml 0 points 7 months ago (1 children)

Can’t you turn it off on the monitor?

[–] Codilingus@sh.itjust.works 1 points 7 months ago* (last edited 7 months ago) (3 children)

I don't think that is something any HDR monitor can do, unfortunately. They just let you know it's in HDR mode.

Edit: I stand corrected.

[–] SpacetimeMachine@lemmy.world 5 points 7 months ago

My monitor AW2432DWF does allow you to turn off HDR, although it is a relatively recent monitor and my first HDR one, so I don't know how common that is.

[–] Dudewitbow@lemmy.zip 4 points 7 months ago

HDR for the most part, is a two way feature. must be enabled by driver/de as well as enabled on the monitor for it to in work, because its not always ideal to have local dimming enabled on monitor (one of the key components required for HDR)

[–] Zamundaaa@discuss.tchncs.de 3 points 7 months ago

Many monitors allow you to turn off HDR, they just claim they don't support it to the computer when you do that