55
What cursors do you use on Wayland?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Oct 2024
55 points (96.6% liked)
Linux
48335 readers
516 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
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.
That's either a compositor or driver bug, please report it (as I've never seen that on Plasma, to your compositor first).
That's because it moves the X11 pointer but not the real one. A cursor theme can't change that.
I see. So nothing really changed? I was starting to think that it might be related to permissions in Wayland, apparently not.
Hmm, in that case it could be a Hyprland issue. I would say wlroots but they stopped using wlroots and I switched to River recently. Haven't happened on River yet but it's been only a week so I cannot say for now.
The real one? It was fine on Xorg though. I tried to put my user into input group, thinking could be related to a permission issue but it didn't change anything.
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.
So even if there was a native Wayland cursor, that wouldn't fix it too unless everything is native Wayland?
Then this shouldn't happen with native Wayland apps I assume. I guess some problems could occur since it's a transition layer. Though I don't know the working mechanism of Xwayland. I'm kinda confused. So this is a pointer issue but not input issue?