mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #660] Cursor gets stuck occasionally in either top or bottom corner on client. #522
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#522
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TheAlmightyThor on GitHub (May 8, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/660
It happens occasionally, when I move my cursor to my client(macOS Catalina) the cursor will jump to either the far top or far bottom corner and refuse to move. The only way to stop it is to restart barrier on both devices and it sometimes persists through that.
Another issue which does happen more frequently when moving the cursor from one machine to the other it'll jitter and will take a while to get through to the client.
Operating Systems
Server: Windows 10 1909(18363.778)
Client: macOS Catalina 10.15.4
Barrier Version
2.3.2
@gnr8shn commented on GitHub (May 16, 2020):
Same issue but moving from W10 to RPI cursor pops into top left corner. Keyboard is OK.
Server: W10 1803 (corporate so still supported)
RPi: Buster 10, latest updates as at 16 May 2020
@simons-public commented on GitHub (May 17, 2020):
Also having the same issue here occasionally, seems to happen especially when another application steals focus right as I'm at the edge of the screen. For me it only started happening when I turned on the "Switch after waiting" delay. I'm running it with debug logging for a while to see if I can capture the logs when it happens.
@gnr8shn commented on GitHub (May 17, 2020):
It was an OEM install of Raspberry Pi (Noobs). I installed Noobs off the web and it works fine now. Go figure.
@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.