mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #962] Unable to move mouse beyond second screen of server #774
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#774
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 @mkostersitz on GitHub (Dec 1, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/962
My setup looks like this
From Server Screen 1 I can move the mouse up to the Mac OS Client and left to the Server's 2nd screen nut not to the Win 10 Client
When I move the Win 10 Client to the right of the Server's Screen 1 I can move the mouse to that screen successfully.
To Reproduce
Setup Server configuration as above
Try to move mouse to the left most client screen
Expected behavior
The mouse and keyboard to transition beyond a secondary screen.
Screenshots
If applicable, add screenshots to help explain your problem.
Please do not link to image hosting sites, as these can be ephemeral. Instead, attach them to the issue.
Desktop (please complete the following information):
Server: Windows 10X on ARM, Barrier Version 2.3.3
Client: Windows 10 x64, Barrier Version 2.3.3
Client: Mac OS Big Sur, Barrier Version 2.3.3
Additional context
Add any other context about the problem here.
@jacklawry commented on GitHub (Dec 2, 2020):
I also couldn't move into Win10 Client from Big Sur Server but I updated server to v2.3.3 and stopped and restarted Client (making sure the correct server is still selected) and it's working again now.
@DesignsWithDavid commented on GitHub (Jan 7, 2021):
If it works now, please close the issue.