I use posy but I'm watching this issue like a hawk before I recommend it https://github.com/simtrami/posy-improved-cursor-linux/issues/13
this post was submitted on 19 Oct 2024
54 points (96.6% liked)
Linux
47814 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
Cursor is not really anything that I feel a need to customize. It's a pointer that changes shape according to context, and the default implementations usually do it at least decently.
Sure, but my post isn't about customizing really. It's about Xorg vs Wayland cursors, which I don't know any Wayland cursor I can use.
Is the normal Breeze cursor not an option?
I'm also not quite sure what you mean with "Wayland cursor", but I'm using the default Breeze cursor under Wayland without problems...
I haven't tried it but I can try. Recently I learned about Hyprcursor in a post which was saying native Wayland cursor. However I couldn't really find anything about native Wayland cursors so I asked here.
Hmm, I read that the KDE devs changed the Breeze cursor to use SVG files, which allows scaling it for the shake-cursor-feature of Plasma 6.1. That feature's only available on Wayland, but yeah, no idea if this really couldn't be done on X11...
Apparently those cursors can be used on both Xorg and Wayland with their respective specs, and they are even located at ~/.icons or /usr/share/icons. Maybe this is some kind of a transition stage. However hyprcursor isn't located there.
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.
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.
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.
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?
I like the catppuccin cursors (along with the rest of catppuccin) https://github.com/catppuccin/cursors
I installed the Mocha pack and it seems fine so far. Thanks.
I love the vimix cursors
Adwaita cursor is the only good cursor.
I use Bibata however I don't really have a strong preference for any specific one.
Going to return to this thread a bit later, just to see if other people link something interesting
i use nordzy-hyprcursor via the hyprcursor application
Can we use it on outside of Hyprland? I installed it but doesn't show up on nwg-look. No idea if I can use it at all.
Sadly i don't know, as i am using hyprland.
I see. I checked its documents now and it seems it can be usable on Hyprland only, depending on hyprctl.
i use banana cursor because bananas are healthy
You misspelled curses
Eh, it's been generally fine for me so far. What curses do you use? Ncurses doesn't count. :)
No, I like Wayland a lot.
And I do use sway with mostly TUI programs, Elinks and Vimium-Browser.
So I hardly ever see the cursor.
I see. Well, I use TUI a lot too (even on display manager, ly rocks) but not everywhere so I still need my cursor. Also I'm using a WM doesn't mean I cannot get lazy. :)
I don’t know if these are wayland cursors or not, but I’m using Polarnight
They are Xcursor, same as Breeze-hacked. Honestly only native Wayland cursor I know of is Hyprcursor, but that only works with Hyprland it seems.
I actually use Hyprland and I also have Hyprcursor installed, but for some reason there are like 3-4 different cursors depending on which program I’m using
I think those are changing according to which sandbox environment you currently use. Probably one for root account (for programs you use with sudo), one for flatpaks and one for normal user.
Ah yes that makes sense. I do have a small number of flatpaks installed