• 17 Posts
  • 268 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle













  • 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 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.