I use an rmm called level. The remote support function under Wayland doesn’t allow keystrokes or mouse input in Firefox.

Question : Is it that Firefox has not implemented the necessary features to allow input? Or is this more likely to be the rmm?

I reached out for a feature request to level, great company BTW.

UPDATE: So, it turns out that my RMM is working fine under Wayland. Level got back with me because they couldn’t reproduce the problem. So I tried to reproduce the problem. Only to find it is working just fine. Whatever was causing that problem, I have no idea. But it’s gone.

  • drwankingstein@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    4
    ·
    edit-2
    1 year ago

    this is probably actually the fault of wayland and it’s fragmentation issue. Various wayland compositors have different methods of interacting with them and this includes remote/virtual input. Because of this fragmentation a lot of developers have just started to kinda give up, on wayland.

    for this one specifically, I would assume any virtual input would work? there are a couple possible routes forwards, the easiest is probably using XDG’s RemoteDesktop. However not every compositor implements this, Sway will be getting it soon (or already has it using luminous). There are also numerous compositors that don’t support this.

    you have wlr-virtual-{pointer,keyboard} which works on sway and mir, and thats it. I believe there was a compositor that could do this over dbus too?

    the reality of wayland is, if it’s not in the core protocol, you aren’t guranteed to have support, and if it is in the core protocol, you still arent guranteed to have support, but the chances are better

    • TxTechnician@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      So, it turns out that my RMM is working fine under Wayland. Level got back with me because they couldn’t reproduce the problem. So I tried to reproduce the problem. Only to find it is working just fine. Whatever was causing that problem, I have no idea. But it’s gone.

      • drwankingstein@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        interesting, do you know what they were using for input? if they have an encompassing solution that could be great. if they just use xdg remotedesktop, well thats about what I have now anyways T.T

        • TxTechnician@lemmy.mlOP
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          No clue. But they are a pretty solid company. Small, responsive, and inexpensive.

          Each pc costs $1/month, Min $20/month.

          They have only terminal and file browsing for Linux now. But gui interface is on the road map.

          Hope they get that soon.