Cursor from Linux(Zorin OS 17) not following the mouse from Windows despite the mouse being clearly moving

[marcoramos17]

Describe the Bug/Issue

I managed to connect both screens from my windows laptop with the one from my linux laptop (Zorin OS 17 - based on Ubuntu) and it worked. However the cursor on my linux machine doesn't follow the mouse, it just stays in place. I can see the mouse is moving because I can see the hovering effects of the mouse on the applications I have open and the cursor icons change as well but the cursor itself remains in place and doesn't move at all. It works well from linux to windows but from windows to linux it has this issue.

I can plug my mouse on Linux and use it that way but the Windows machine is my main machine so I'd rather avoid the input lag on windows.

Your Environment

• OS details: Windows 10 x64 and Zorin OS 17 (Ubuntu-based)
• Cursr Version: 1.6.6
• License: Free

[ragauskl]

Is Zorin OS using X server/X11 or Wayland? If it's X11 then it's probably a bug, if it's wayland - then it's not supported yet, but it is in the Cursr backlog.

I have never used Zorin OS and Cursr is only fully tested on Ubuntu as currently my testing envrionments are Windows 10, Ubuntu on dual-boot and a macbook, additionally I borrow 3 more from partner but that does not include a Linux environment. So testing other Linux environments is tricky as I can't just run a VM.

I will be getting another laptop and will be able to repurpose older one to split into multil-boot of different Linux distributions but it might be at least 2 months until then. Another option would be to run it from external drive or USB if I set that up but that will also take some time.

If it's X11/X server could I ask you to enabled 'debug' mode in Cursr settings on Linux and Windows, replicate the issue and send 'compressed logs' to contact@cursr.app ?

[marcoramos17]

Oh I see that's probably the reason. It is using Wayland. I'm sort of new to linux but I've got the error message for Wayland from synergy when I tried using that. Thanks for letting me know

[ragauskl]

I've recently saw that there is a library written for handling mouse/key events on Wayland for apps like these so that might make it easier to add support for Wayland. Currently I already have a lot queued for 1.7 but as soon as it's out I'll have a look how much work will be to add Wayland support and if it's not too much I'll add it for 1.8 release, otherwise might be later release but in any case I will post an update on #29 . I'll mark this as duplicate because of wayland but will keep open until it's resolved.