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.

  • flamingo_pinyata@sopuli.xyz
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    12 days ago

    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.

    • muhyb@programming.devOP
      link
      fedilink
      arrow-up
      1
      ·
      12 days ago

      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.

      • Ephera@lemmy.ml
        link
        fedilink
        arrow-up
        5
        ·
        12 days ago

        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…

        • muhyb@programming.devOP
          link
          fedilink
          arrow-up
          0
          arrow-down
          1
          ·
          12 days ago

          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.

          • Ephera@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            12 days ago

            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…

  • Zamundaaa@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    7
    ·
    12 days ago

    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.devOP
      link
      fedilink
      arrow-up
      1
      ·
      12 days ago

      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
        link
        fedilink
        English
        arrow-up
        2
        ·
        12 days ago

        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.devOP
          link
          fedilink
          arrow-up
          1
          ·
          12 days 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?

  • dinckel@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    12 days ago

    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

    • muhyb@programming.devOP
      link
      fedilink
      arrow-up
      0
      ·
      12 days ago

      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.

      • Akinzekeel@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        12 days ago

        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

        • muhyb@programming.devOP
          link
          fedilink
          arrow-up
          1
          ·
          11 days ago

          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.