this post was submitted on 19 Oct 2024
53 points (96.5% liked)

Linux

48287 readers
613 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

I like my Breeze-hacked cursor but I think it's time to find a native Wayland replacement.

I have some problems with X11 cursors and that's quite normal with Wayland obviously. For example, my cursor can become invisible if my screen sleeps. 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. Things like this.

It's becoming kinda inconvenient so I'm asking for a replacement. Currently I don't really care how it looks.

I'm on River by the way.

you are viewing a single comment's thread
view the rest of the comments
[–] Zamundaaa@discuss.tchncs.de 4 points 1 month ago (1 children)

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.

[–] muhyb@programming.dev 2 points 1 month ago

So even if there was a native Wayland cursor, that wouldn't fix it too unless everything is native Wayland?

Some compositors allow Xwayland to request moving the real pointer instead of doing emulation, but River apparently doesn’t.

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?