It hasn’t operated at a loss anymore for years you mean?
It hasn’t operated at a loss anymore for years you mean?
misconfigured
Unless you did something really stupid and deleted system libraries or something like that, no configuration should cause crashes. Please make a bug report about it at bugs.kde.org. You might not be able to fix it yourself, but crashes are often relatively easy to diagnose and fix for a developer.
In the case of one project in paticular, that being the Sunshine game streaming project
That’s a terrible example, because they completely ignore the many many years old standardized APIs (screen casting and remote desktop portals) that they could use, in favor of doing hacky and broken things that require root access instead.
Xwayland doesn’t get input in some special way, it uses the exact same Wayland protocols to get input events as native Wayland apps. All claims about it being more complete or anything like that are nonsense.
Krita forces Xwayland because they have some X11 specific code they haven’t bothered porting away from, that’s all.
You don’t need to use steamtinkerlaunch, putting gamescope --hdr-enabled --fullscreen -W width -H height -- %command%
into the launch options is enough.
Will the Gnome version of Bazzite work for HDR on an Nvidia GPU, or for that matter any other OS as long as I’m using gamescope to run the game with HDR enabled?
Gamescope can’t make a different compositor support HDR. Until Gnome supports HDR and the protocol used by gamescope, it won’t work.
For Netflix there’s a browser extension that does it, but I don’t know of a solution for other streaming services
Quite the opposite, bigger grids are much more stable. When faults happen, tiny subsets of the grid get disconnected from the rest, it does not take the whole thing down at all…
Yeah, it gets more blown out the bigger the difference between the sdr brighrness setting and the highlights is.
Support for HDR screenshots is hopefully something I can add soon-ish
How are you taking the screenshots? Spectacle might not capture HDR highlights well, but it should look all proper on SDR content
That’s not really a Wayland thing, that’s an (apparently badly implemented) attempt to bridge X11 apps to a permission system they were never written for.
With appropriate sandboxing of apps so they can’t just LD_PRELOAD code into all other apps you run, yes.
Multi monitor VRR has never been problematic in Wayland, but the NVidia kernel driver doesn’t support it at all yet, Xorg or Wayland doesn’t matter.
enabling the built in color profile desaturates colors quite a bit and does some kind of perceived brightness to luminosity mapping that desaturates bright / dark hdr content even more
It maps the colors to be more correct, and it does use the brightness info from the EDID for HDR content, so that checks out.
I think there must be something wrong with my screen since the hdr reduces saturation more than anything else
It might enable some sort of gamut mapping on the display side… HDR on monitors is really weird sometimes.
Side note, when I turn off hdr only from kscreendoctor the display stays in hdr mode until it turns off and on again, that didn’t happen with nvidia
I think that’s a bug in amdgpu. It should force a modeset on hdr change, but it doesn’t.
That has pretty much nothing to do with the color profile, when colors look very desaturated on HDR screens, that’s the driver messing up the colorspace signaling.
What GPU do you have? Both Intel and NVidia still have major problems with this.
Many displays (but not all, which is why it’s not exposed in the GUI) also support doing HDR without additional colorspace signaling, you could try enabling only hdr and disabling wcg with kscreen-doctor
. IMO the color part is the more noticeable benefit of HDR, but you could at least have functional HDR until your GPU driver is fixed.
Of course apps can and do restore their window sizes. Don’t spread misinformation
There have been incidents involving malicious code downloaded through Plasma global themes.
No malicious code was involved, just buggy code.
KDE did bother, this does neither happen with KScreenlocker, nor do non-screenlocker windows show in another way, because the screen locker is integrated with the compositor.
If the compositor crashes or gets disabled somehow ofc though, that integration doesn’t help either and you have to rely on a mountain of bad hacks as well as the hope that the screen locker doesn’t also crash for nothing to happen in that case, but it’s as close to secure screen locking as you get on Xorg… in the end the solution for secure screen locking is still Wayland.
S3 is standby. Hibernate is S4
the fact that 1.8 was working tells me that it is possible for a window manager to work well for nvidia
Nope, it’s a race condition for which the visible effects can appear or disappear for plenty of reasons. The only fix is explicit sync, which is being worked on for wlroots
The github repo has tons of issues about the problems caused by the hacks (from the cursor not being recorded, to it not working in Flatpak, not working with virtual displays, to even preventing graphical sessions from starting!) with the suggested solution of just using the remote desktop portal… I don’t know what the problem is, but it’s not a lack of knowledge.