I used Hyprland for a longer time now. I also was using tilling window managers for a few years now. But Hyprland had its issues again (most likly something I setup wrong). I reinstalled and switched to OpenSuse and tried KDE just a little and was blown away how good it now is!
I used Hyprland because of tilling and ultrawide Gaming. I use a PLP setup (2 Rotated 1080p screens and a 1440p bigger one in the middle). I open my games over gamescope in the resolution 4720x1440. And Hyprland worked with that most often the best. But not only has it a nasty left screen click bug where mouse inputs are misaligned, it also had many issues for me the last few weeks with coding, crashes and clipboard stuff.
I explain how I worked with it to show you all from were I came from. As soon as I tried out the newest KDE release 6.3.4 I noticed a big difference. THE PERFORMANCE. In the past KDE was always slow in edge cases but this time everything I threw at it worked. Giant gamescope window = no problem, weird setups of screens = easy, GPU intensive tasks and using the desktop at the same time, smooth without stutter! It sadly has no tilling (without scripts that work not all that well). But the Meta+LEFT,RIGHT,... works well enough and can be used to tile at least a little.
I only needed to set a few window rules to force windows of the class gamescope into position 0.0x50.0 and size it to 4720x1440 (and not forgetting to above all other windows) and that was it. I could game no issue with my gamescope config. I wanted my hotkey to reposition the window to work like Hyprland. My script I made in the past is incompatible with the newest Plasma 6 release. So... a lot of searching and a few changes later and it worked again too (the scripting, testing and documentation got a little better but is still really messy). I must say I really love KDE now. It works SO WELL.
I remember I read a few weeks back that HDR now """works""" on Linux with KDE. So I checked and YES it works! Hyprland could never manage my displays correctly with HDR but KDE JUST WORKED. Then I thought, can I use it to watch stuff and checked MPV (jellyfin-mpv-shim to be precise) and YES IT ALSO WORKS! Just like that. Then I needed to test one last thing, gaming. And well. It is MEGA JANKY (https://www.reddit.com/r/kde/comments/1ampxta/comment/mhw99h3/) but it works. Then I had a really REALLY cursed idea... .
As soon as I discovered for my self Linux can do HDR, like actually do it, I switched my living room PC to Bazzite (if you are wondering, Bazzite is nice but annoying because many things a broken when you need to fix stuff. It deviates from Fedora so far that it breaks layering of packages and similar stuff. I also needed to install jellyfin-mpv-shim over pip and copy my config from my PC because Bazzite dose not come with python3-tkinter (or it is incompatible)). It works. It even fixed some of the Color bending sh*t windows had. I thought to myself, Cyberpunk on this beast of a TV with such great support would be really nice... wait as sec...
The PC in the living room is far FAR too weak for 120FPS 4k (only 60hz works because HDMI and GTX1080). And my PC is a pain to move every time. So I came up with the idea of streaming Cyberpunk 2077 from my PC with AV1 or H265 to the living room with Sunshine WITH HDR. Sunshine supports it (but only tested it on windows).
This coursed setup works. I need to do the following things:
I tested a little more (I have bought myself a HDR QD-OLED Ultrawide Display) and to get HDR everywhere working I needed many different types of setup's. The setup above sometimes work. But sometimes if I want to play Cyberpunk 2077 for example I need native Proton-HDR (Only some builds have HDR enabled. "proton-cachyos-10.0-20250601-slr-x86_64_v3" works for me). Then the only option is either using Mesa 25.1 and newer and KDE 6.4 or newer. But both is are in Beta. For now I use a trick originally only needed for Nvidia and some AMD setups. It is a library called "vk_layer_hdr". A fork needs to be compiled on the system if not available in the repository with the installed MESA build at compile time. A good demonstration is this video by "LinuxNext" on Youtube: https://youtu.be/B_87kmAAlRw. The fork I used (From “Zamundaaa” forked from "Drakulix"): https://github.com/Zamundaaa/VK_hdr_layer. It works on OpenSuse Slowroll with the following start command (This one is for Cyberpunk 2077): PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 ENABLE_HDR_WSI=1 %command% --launcher-skip -skipStartScreen -modded
The Important part is the "ENABLE_HDR_WSI=1" that many guides are missing. It tells proton and/or Mesa to use the external HDR layer from the library.
I Heroic Launcher I could not get Control to work with HDR. It has a dose soemthing that causes a Bug in Protons Wayland/HDR part that breaks mouse movment. BUT I got it to work with gamescope with the arguments as followed: -W 5120 -H 1440 -w 5120 -h 1440 -f --hdr-debug-force-support --hdr-enabled --adaptive-sync --immediate-flips
From my testing gamescope is very sensitive with settings. No FSR (From gamescope), no scaling (Meaning W/w and H/h must be identical) and no special parameters except for the once above!. I also only got it to work with GE-Proton 10.4 and newer.
As you can see there currently no one way to always go on Linux for HDR. You need to try around until you get a setup just right and to work. This will change soon with KDE 6.4, Mesa 25.1, Proton 10.x (Most likely the unofficial once for longer, Valve will probably only enable general HDR in the compile when Wine's wayland port is done).
I tested some games by now and the following work beautiful with HDR (Locally and Remote, with or without UltraWide):
I noticed many issues with frame drops. It was WLAN. The only way to fix it was a LAN cable. The issue is that in my place I can not directly connect my router (believe me I f*cked it up trying once). BUT sunshine is peer 2 peer (P2P). This means after connecting the router can be ignored. Thankfully my office and living room are next to each other and with a little restructuring of my network-topology I now only need to connect on cable so the living room client has a wired connection. The switch gets its internet from a mesh node connected over WIFI. The connection start uses the router, the stream not. I even disconnected the mesh node once and everything keept streaming! Just a small tip for all not owning there home and don't have Ethernet in there walls... .
This is as much a cluster f*ck as it sounds like. And now the best part. It just works butterfly. The only issue I am unable to fix is that the priority of the KDE displays gets messed up on reset every time. That's it. Every time I do something like this I think to myself that this must be the most jank I ever did... and then I do something even worst xD. I am already exited to see what tops this level of jank.