this post was submitted on 11 Apr 2024
1 points (100.0% liked)

KDE

5313 readers
5 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
1
submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]
 

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

Thank you everyone for your help πŸŽ‰

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 7 months ago

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