Linux

48328 readers

617 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

What cursors do you use on Wayland? (programming.dev)

submitted 1 month ago by muhyb@programming.dev to c/linux@lemmy.ml

33 comments fedilink hide all child comments

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 13 points 1 month ago (3 children)

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.

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

I see. So nothing really changed? I was starting to think that it might be related to permissions in Wayland, apparently not.

That’s either a compositor or driver bug, please report it (as I’ve never seen that on Plasma, to your compositor first).

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.

That’s because it moves the X11 pointer but not the real one. A cursor theme can’t change that.

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.

[–] 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?