The real one? It was fine on Xorg though
When an app (in your case, Steam) uses X11 APIs to move the cursor, that of course works on Xorg, but Xwayland merely emulates it - so it moves the X11 pointer for X11 apps, but not the pointer from the Wayland compositor.
Some compositors allow Xwayland to request moving the real pointer instead of doing emulation, but River apparently doesn’t.
I have some problems with X11 cursors and that’s quite normal with Wayland obviously
It’s not. There is no Wayland specific cursor format, it’s all just images on disk, and the most widely used format hasn’t changed away from Xcursors yet.
For example, my cursor can become invisible if my screen sleeps
That’s either a compositor or driver bug, please report it (as I’ve never seen that on Plasma, to your compositor first).
Additional controllers that control mouse cursor don’t control X11 cursor, however they still work, I just don’t know where the cursor is unless it highlights something.
That’s because it moves the X11 pointer but not the real one. A cursor theme can’t change that.
Then you’re using Xorg, not Wayland.
What problems do you have with per screen scaling on Wayland?
Stop using Xorg and your scaling problems are gone.
Debian
… is not something you should ever use on a desktop PC. Due to its eternally very outdated nature and not even shipping bugfix updates**** it is not a good fit for anything but servers.
Wayland, for some reason, couldn’t handle 4 monitors, with one above the other three.
“Wayland” doesn’t handle monitors at all. What (because of Debian, wildly outdated) desktop did you use?
Oh, and the biggest issue I had with Windows was copied straight into Linux. I want my (single) taskbar on a monitor that isn’t my primary.
Not a Linux issue, but a problem with the desktop environment you chose. KDE Plasma allows you to configure panels in any way you want.
This is about dragging a tab out of or into a browser window, and letting the compositor know about it, so it can move and place the window accordingly. Apps don’t get to place windows themselves.
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.
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.
What kind of flickering? Does the display support adaptive sync? If so, try turning that off
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
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
Also, your blog is fantastic, I’m always happy when there’s a new post =)
Thank you, I’m glad you like it!
I feel like in SDR mode, the OLED is pushing brighter images. I almost feel like it’s underselling the capabilities at 270, but does so to give pixels a rest every now and then, in the hope that the bright spots don’t stay stationary on the screen. It’s a wild guess, I have no idea.
It’s certainly possible, displays do whacky stuff sometimes. For example, if the maximum brightness in the HDR metadata matches exactly what the display says would be ideal to use, my (LCD!) HDR monitor dims down a lot, making everything far, far less bright than it actually should be.
KWin has a workaround for that, but it might be that your display does the same thing with the reported average brightness.
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.
That day was years ago. Many banking apps refuse to start if you even just have your bootloader unlocked, and some banking websites only support Chrome, some really crappy ones even only Chrome or Edge on Windows specifically.