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.
To maybe prevent a catastrophe: The system is not able to restore virtual desktop assignments yet, it only starts the apps you had open before.
There have been incidents involving malicious code downloaded through Plasma global themes.
No malicious code was involved, just buggy code.
That's just a law of computers, the default arrangement of monitors must always be wrong.
You can just sync your Plasma settings to SDDM though, and it'll use the same output settings as your session
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.
Fedora just has
polkit.addRule(function(action, subject) {
if ((action.id == "org.freedesktop.packagekit.package-install" ||
action.id == "org.freedesktop.packagekit.package-remove") &&
subject.active == true && subject.local == true &&
subject.isInGroup("wheel")) {
return polkit.Result.YES;
}
});
in /usr/share/polkit-1/rules.d/org.freedesktop.packagekit.rules
. If you put the same file in there, it should work.
@Zamundaaa
@discuss.tchncs.de