| 2 Dec 2025 |
 Sean | so maybe mangohud broke or something idk | 07:41:32 |
| Sean | I removed MANGOHUD=1 PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command% | 07:43:57 |
 K900 | Yeah out of those three I doubt mangohud is the issue | 07:44:23 |
| K900 | And HDR should be on by default now | 07:44:53 |
| K900 | (where appropriate) | 07:44:55 |
| Sean | it was. I just started the game with the other 2 enabled | 07:45:00 |
| Sean | unless it's just a fluke and now it works completely | 07:45:22 |
| Sean | no it doesn't start with MANGOHUD=1 | 07:45:59 |
| Sean | testing with the game: control | 07:46:13 |
 niklaskorz | huh, TIL | 11:15:52 |
| niklaskorz | I'm not on KDE anymore but on my wife's KDE system proton-ge with wayland enabled also suddenly refuses to show any windows, as of last week | 11:17:58 |
| K900 | My money would definitely be on wine-wayland tbh | 11:18:43 |
| K900 | There's a reason it's VERY EXPERIMENTAL DO NOT USE | 11:18:54 |
| niklaskorz | it worked pretty well for the past two months but I'm also back on gamescope for now for HDR | 11:21:38 |
| K900 | You shouldn't need any of that, Plasma should just do HDR natively with Proton | 11:25:17 |
| niklaskorz | that'd be news to me, afaik kwin6 does not support HDR for Xwayland | 11:37:05 |
| niklaskorz | only explicit mention I can find is from 2023 though: https://zamundaaa.github.io/wayland/2023/12/18/update-on-hdr-and-colormanagement-in-plasma.html | 11:40:15 |
| niklaskorz |
Apps running through Xwayland are strictly limited to sRGB too, even if they have the ability to work with ICC profiles, as they have the same problem as Wayland native apps: Outside of manual overrides with application settings there’s now way to tell them to use a specific ICC profile or colorspace, and there’s also no way for KWin to know which profile or colorspace the application is using. Even if you set an ICC profile with an application setting, KWin still doesn’t know about that, so the colors will be wrong.1
It would be possible to introduce an “API” using X11 atoms to make at least the basic arbitrary primaries + sRGB EOTF case work though, so if any developers of apps that are still stuck with X11 for the foreseeable future would be interested in that, please contact me about it!
| 11:40:26 |
| niklaskorz |
While I already mentioned that Xwayland apps are restricted to sRGB, gamescope uses a Vulkan layer together with a custom Wayland protocol to bypass Xwayland almost entirely.
| 11:41:30 |
| K900 | Oh wait no I'm wrong actually | 11:42:39 |
| K900 | Kwin doesn't ship the cursed WSI | 11:42:42 |
| K900 | So yes you either need nested gamescope <- gamescope WSI <- xwayland game | 11:43:16 |
| K900 | Or wine-wayland which just does normal Wayland things | 11:43:35 |
| niklaskorz | yup | 11:43:40 |
| niklaskorz | and realistically speaking I don't see a need to change that, Proton Wayland worked well enough for the past few months that I'm sure it'll be ready for wider use in 2026 | 11:44:22 |
 Sandro 🐧 | I had some issues with gamescope before. Depending on how you use it, it uses LD_PRELOAD which sometimes causes issues | 14:49:11 |
| K900 | It doesn't anymore | 14:50:02 |
| K900 | It used to leak it from steamrt sometimes but now it doesn't | 14:50:10 |
| Sandro 🐧 | Mixing up gamescope with gamemode | 14:51:28 |
| K900 | Oh, don't use gamemode, it's garbage | 14:51:49 |
