

Yes, it’s a bug that was fixed in 6.3.2
Yes, it’s a bug that was fixed in 6.3.2
You can’t. Apps need to support shortcuts in order to receive them…
For Discord, the X11 compatibility page has working options though.
Umm yes, they did take ages to support it. It took like 7 years…
It was implemented over two years ago.
Do motherboard/monitor/IC/etc manufactures need to submit their own kernel patches well in advance of product releases, like what AMD and Intel do for their CPUs and GPUs? Are we just waiting for them to give a shit?
Yes. There isn’t really any other good solution.
Why does Nvidia need to support night light?
They don’t, but they needed to support the KMS API for applying lookup tables to the image sent to the screen - desktops relied on that functionality without a fallback, so when it wasn’t available, you just didn’t get the feature.
Can’t someone from Wayland just write a simple shader in any shader language that does colour adjustments and apply it to the desktop?
There’s no such thing as “someone from Wayland”, just the developers of the DEs (well, the project is named after a town, but I’m sure that’s not what you meant).
But, yes, you can use a shader. We implemented that in KWin and we’re using it when the driver or hardware doesn’t support the functionality we need… but that has a noticeable performance impact, so it’s still necessary for the driver to support it natively.
why is Xwayland not just automatically shunting the actual directive to set the permission over to xdg-desktop-portal, which you say can correctly handle this, on kde.
It is doing that. It just doesn’t give the portal any information at all - neither that the request is coming from Xwayland, nor what X11 app is trying to emulate input.
Like I said, the feature has been really poorly thought out.
How can it be the case that XWayland can grant you an app temporary permission, but not permanent?
It keeps the handle around until the X11 app’s process exits, then it’s gone. It’s how all on-demand permissions work, unless you do special stuff to restore it later without user interaction.
that or Bazzite is doing some kind of special something that others are not.
Yes, they patch permission prompts out entirely. They do that on their KDE edition too.
xdg-desktop-portal-gnome has actually properly been updated to handle this, whereas xdg-desktop-portal-kde has not.
No, that’s completely wrong. Like I said, Xwayland doesn’t remember the permission, which xdg-desktop-portal-kde would very much support.
You get the exact same prompts every single time on Gnome too.
The problem has persisted for years
This feature hasn’t existed for years, it’s quite new.
This has absolutely nothing to do with GTK or system trays, and it is in no way or form specific to KDE Plasma or a bug in it. It’s an Xwayland feature that was poorly thought out and that’s challenging to work around.
kde on wayland issue is making it pop up over and over again
Unfortunately it’s an Xwayland issue. It doesn’t remember the permission, and it also doesn’t give the desktop any information to work around it. Because of how portals work, the desktop doesn’t even know the request is coming from Xwayland :/
That’s not right. Most monitors use 8 bits per color / 24 bits per pixel, though some are still using 6 bpc / 18bpp.
HDR doesn’t mean or really require more than 8bpc, it’s more complicated than that. To skip all the complicated details, it means more brightness, more contrast and better colors, and it makes a big difference for OLED displays especially.
You could also try using KDE Plasma instead of Gnome, which survives GPU resets.
Okay, then the driver doesn’t allow Plasma to turn it on for some reason. You can report that at https://gitlab.freedesktop.org/drm/i915/kernel/-/issues, maybe someone from Intel can help.
No I can’t move my mouse to the external monitor.
Do you mean that it stays on the internal display, or that it doesn’t show up on the external one?
Or to ask it differently, can you move a window where the monitor should be?
My laptop detects the monitor correctly so it shows up in the KDE plasma display configuration but the monitor is not getting any input.
So the system thinks it’s enabled? Can you move the mouse cursor to it?
Screen mirroring is kinda shitty rn, this might get fixed with future changes for Plasma 6.4 (which make it less shitty in general). It’s probably worth fixing this as a separate thing for 6.3 though, so please make a bug report about this for KWin at bugs.kde.org
It’s an Electron problem, yes. The API is there, just waiting to be used.
Ah, you’re on Xorg. This feature is only available in the Wayland session
Go into system settings > mouse > select your mouse > rebind buttons
To the same level that Wayland does - it doesn’t actively do anything for or against it. There are tools that happen to be built for X11, and which you can also use on Wayland (with a very small amount of additional manual steps vs. how it works on X11)