mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1043] Cursor jumps to the exact middle of primary display on macOS #827
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#827
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 @LukasMojzis on GitHub (Jan 29, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1043
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Mouse cursor appears near the edge, as if it passed from screen to screen
Desktop (please complete the following information):
@hungerregnuh commented on GitHub (Feb 2, 2021):
Not a fix, but it works - i also found out that if you enable the double tap edge to switch, the mouse doesn't jump around anymore, not as convenient sure - but works.
@LukasMojzis commented on GitHub (Feb 9, 2021):
I did have that enabled at the time of filing this bug report. I believe this might have something to do when the macOS is used as a server. For now I am using duo of keyboards and mice again, until I buy a KVM switch that supports keyboard shortcut switching.
@stephensilber commented on GitHub (Mar 25, 2021):
I have noticed this on my setup as well although it's somewhat inconsistent. My best guess is that my Mac display (server) is a 1440p ultrawide and my Windows display is 1080p so maybe there's some weird coordinate translation happening? That wouldn't explain the inconsistent behavior though
@thedaneeffect commented on GitHub (Sep 18, 2021):
I've got the same issue except Win11 is the server and BigSur is the client. It seems to happen a lot more often when you quickly move the mouse.
@twizzayy commented on GitHub (Jan 28, 2022):
Also experiencing this bug between Mac OS Big Sur 11.6.2 and GNU/Linux Debian 10 "Buster"
Mac is the server.
Work Around for Mac Users
I had to set my primary screen to the far right on my Mac system because the cursor would jump to the middle of the primary display. Like below:
Here is the Barrier set up I have for reference:
So, if I had my primary display set to the far left monitor on my Mac, and I moved from my Debian screen to my Mac, then the cursor would jump all the way to the middle of the primary display on the Mac (The far left display). This means it would jump across two other screens.
Solution
The Workaround I am using for this currently is to have my Mac displays isolated to the left side of my desk, and then setting the primary display to the Mac monitor on the far right.
This stops it from jumping across screens, but the cursor will still jump to the middle of the screen on my Mac when switching from Debian.
So to remedy that with Barrier, on my Mac, I go to: Configure Server Advanced server settings and click the “Switch After waiting” Check Box and set the time to like 200ms. So when switching from Debian to Mac quickly, it feels more natural for the mouse to be in the middle of the screen after a .2-second delay. This does, however, also add a delay when switching from Mac to Debian. Which is a bit annoying. Pick your poison.
@derpuma commented on GitHub (Sep 23, 2022):
Is there a solution for this problem?
I have the same issue between MacOS Monterey (Server) and Windows 10 (Client).
Mouse jumps like crazy back to MacOS screen while using it on Windows 10 screen.
@helms-charity commented on GitHub (Dec 18, 2022):
Confirmed that the issue persists on Mac Monterey OR Ventura (server) + Windows 10 (Client).
Thanks all for your comments, I had assumed there was some micro disconnections that were happening between them.
The setting to "double tap to switch" is the only thing that 'fixes' it so far.
@tiredtofu commented on GitHub (Dec 24, 2022):
This is not just for when it's Mac OS as the server. I'm having this happen to me despite having a Windows 10 server + MacOS Ventura (13.1) client. It only happens when the mouse is being moved to the MacOS client, but not when I move the mouse back to the Windows server.
Things I've tried to fix this (that did not work):
@dinbtechit commented on GitHub (Feb 27, 2023):
Having the same issue here. Tried everything. Nothing seems to be working. :(
@bigH commented on GitHub (Mar 24, 2023):
I've noticed that:
when started for the first time, this issue doesn't occur,after sleeping (Cmd+Ctrl+Q on macos and screensaver on Windows) the issue occurs, andclicking "Reload" on the barrier server instance fixes this issue.EDIT: All of the above anecdotally worked, but wasn't consistent. Doing further experiments gives better clarity (see later comment).
@dinbtechit commented on GitHub (Mar 24, 2023):
@bigH interesting observation.. In my case, I use MacOS Ventura (server) and Windows 10 (client). Reloading the server does not fix the issue.. :(
@bigH commented on GitHub (Mar 27, 2023):
I've noticed that #2 is incorrect on my end. It'll intermittently work and not work and I can't explain why. I've tried a few experiments. No experiment repros/doesn't repro it 100% of the time.
@dinbtechit - I have the same setup macos server and Windows 10 client.
@coffnix commented on GitHub (Sep 20, 2023):
After connecting with either the Linux or Windows client, stop and start the server on the Mac. This action should resolve the bug. Tested with the openSUSE Tumbleweed Linux client, Windows 11 client, and macOS Sonoma 14.0 server.
@shitchell commented on GitHub (Dec 13, 2023):
@bigH This is what I'm seeing as well.
Server: Windows 10, barrier v2.4.0-release3e0d758b
Client: Debian 12, barrier v2.4.0-release00000000
@shitchell commented on GitHub (Dec 13, 2023):
@coffnix This does not resolve the issue for me using a Windows 10 server
Server: Windows 10, barrier v2.4.0-release3e0d758b
Client: Debian 12, barrier v2.4.0-release00000000
@dinbtechit commented on GitHub (Dec 19, 2023):
@bigH - I just noticed today this issue no longer happens on my setup (macos server and windows 10 client). I am not sure if that has to do with the recent upgrade of my macos from Ventura (macos13) to Sonama (macos 14). But that's the only that was changed in the last few days.
Can you confirm if upgrading macos solves this issue for you?
@tiagoslucas commented on GitHub (Mar 28, 2024):
@dinbtechit I can confirm I still have this behavior using MacOS Sonoma 14.4.1 so it's definitely not fixed by the update.
@mnunezpoggi commented on GitHub (Aug 30, 2024):
I had this exact same issue with Windows 11 + Windows 10 setup.
My configuration is:
Laptop screen 1 - External screen 1 ----barrier---- External screen 2 - Laptop screen 2
I originally had the issue when both laptop's screens were set as the main display (both at the edges).
I fixed it by making External screen 2 the main display of Laptop 2.
So make sure that at least one main display is next to the other device. And restart the service, of course.
@coffnix commented on GitHub (Aug 30, 2024):
fixed on macOS (server): https://github.com/coffnix/barrier-ng