[GH-ISSUE #636] Barrier ignores local cursor movement #502

New issue

Open

opened 2026-05-05 06:33:09 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:33:09 -06:00

Owner

Originally created by @bkqtnte10 on GitHub (Apr 24, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/636

Operating Systems

Server: Manjaro
Barrier 2.3.2-RELEASE-00000000

Client: Ubuntu 20
Barrier 2.3.2-snapshot-9080ce45

Steps to reproduce bug

Have a mouse on the client and one on the server.
Move cursor on client with server-mouse to point A
Move cursor on client with client-mouse to point B
Start moving cursor again with server-mouse.

Expected is that the cursor starts moving from point B. But the cursor jumps back to point A and moves from there.
It seems barrier ignores local mouse movement (on the client)

Other info

Doesn't prevent, its just a bit annoying

The setup I am using is:

Keyboard with trackpoint on server
Mouse directly on client (to have lower latency)

Originally created by @bkqtnte10 on GitHub (Apr 24, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/636 ### Operating Systems ### Server: Manjaro Barrier 2.3.2-RELEASE-00000000 Client: Ubuntu 20 Barrier 2.3.2-snapshot-9080ce45 ### Steps to reproduce bug ### 1. Have a mouse on the client and one on the server. 2. Move cursor on client with server-mouse to point A 3. Move cursor on client with client-mouse to point B 4. Start moving cursor again with server-mouse. Expected is that the cursor starts moving from point B. But the cursor jumps back to point A and moves from there. It seems barrier ignores local mouse movement (on the client) ### Other info ### Doesn't prevent, its just a bit annoying The setup I am using is: * Keyboard with trackpoint on server * Mouse directly on client (to have lower latency)

gitea-mirror added the

enhancement

label 2026-05-05 06:33:09 -06:00

gitea-mirror commented

2026-05-05 06:33:13 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 23, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:33:16 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

This is a valid feature request, let's not close this.

@p12tic commented on GitHub (Jan 10, 2021): This is a valid feature request, let's not close this.