[GH-ISSUE #256] Mouse Pointer Problem on Linux #207

Closed
opened 2026-05-05 05:40:56 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @xieve on GitHub (Feb 19, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/256

Operating Systems

Server: Windows 7 Professional (Version 6.1 Build 7601: SP1)

Client: Arch Linux (Kernel 4.20.8-arch1-1-ARCH)

  • gnome-shell 1:3.30.2-1
  • xorg-server 1.20.3-1
  • wayland 1.16.0-1

Barrier Version

2.2.0 on Linux, 2.1.0 on Windows (that's the latest pre-built version)

Steps to reproduce bug

  1. Start barrier on both machines
  2. Move mouse to Linux machine
  3. Mouse pointer on Linux stays where it is, but I can click buttons, mark text etc. with it.

Other info

  • This occurs with the latest version of Synergy, too
  • The keyboard feature works fine
  • No workaround
  • This, obviously, prevents me from using barrier entirely
  • Log output of the Linux instance
Originally created by @xieve on GitHub (Feb 19, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/256 ### Operating Systems ### Server: Windows 7 Professional (Version 6.1 Build 7601: SP1) Client: Arch Linux (Kernel 4.20.8-arch1-1-ARCH) ### Any software I'm using that could be related ### - gnome-shell 1:3.30.2-1 - xorg-server 1.20.3-1 - wayland 1.16.0-1 ### Barrier Version ### 2.2.0 on Linux, 2.1.0 on Windows (that's the latest pre-built version) ### Steps to reproduce bug ### 1. Start barrier on both machines 2. Move mouse to Linux machine 3. Mouse pointer on Linux stays where it is, but I can click buttons, mark text etc. with it. ### Other info ### - This occurs with the latest version of Synergy, too - The keyboard feature works fine - No workaround - This, obviously, prevents me from using barrier entirely - [Log output of the Linux instance](https://gist.github.com/xieve/699045b52b4a7bd1e1fabd7ba2346100)
Author
Owner

@xieve commented on GitHub (Feb 19, 2019):

Okay, I'm confused. I just read that Wayland isn't supported (but it works... almost?) but I have used this setup for months, and I'm pretty sure it ran Wayland back then, too. Maybe Wayland was updated, and that broke some connection to the Xserver. Just speculating.

<!-- gh-comment-id:465263740 --> @xieve commented on GitHub (Feb 19, 2019): Okay, I'm confused. I just read that Wayland isn't supported (but it works... almost?) but I have used this setup for months, and I'm pretty sure it ran Wayland back then, too. _Maybe_ Wayland was updated, and that broke some connection to the Xserver. Just speculating.
Author
Owner

@AdrianKoshka commented on GitHub (Feb 19, 2019):

We've never had purposeful wayland support to my knowledge, if it did work, that was an accident.

<!-- gh-comment-id:465361847 --> @AdrianKoshka commented on GitHub (Feb 19, 2019): We've never had purposeful wayland support to my knowledge, if it did work, that was an accident.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#207
No description provided.