Barrier: Cursor is stuck in bottom of client screen. Issue with high resolution displays?

[mcx808]

Operating Systems

Server: Windows 10 x64 1709

Client: macOS 10.13.5

Barrier Version

2.1.0

Steps to reproduce bug

I have a Surface book (3000x2000 scaled at 200%) with a 3840x2160 monitor above scaled at 150%.
My MacbookPro (1280x800) is to the right. Whenever I move the mouse to the mac, the cursor jumps straight to the bottom right screen and stays there. I can right click but not move it. I can use the mac trackpad to move the mouse but not the Windows mouse.

I disabled my laptop screen so I am only using the external display. Same issue.

I moved the orientation of the mbp to the right. Same issue.

The log shows the following warning when I move to the client screen: WARNING: cursor may not be visible

Other info

• When did the problem start to occur? Every time the above steps are followed
• Is there a way to work around it? No
• Does this bug prevent you from using Barrier entirely? Yes

Logs are attached
clienttlog.txt
serverlog.txt

[walker0643]

@mcx808 this should be fixed with 075d4f4758f86c49ef0b5257a2de076b1d7d4569. can you try it and report back? if you're not comfortable building barrier from source this fix will be included in the next release (2.2). thanks!

[walker0643]

Reopen if your issue isn't resolved after 2.2. Thank you :)

[CaptainJawZ]

Sorry for opening the issue again, but I am experimenting the same problem, with similar devices, here is my setup:
[Desktop] [Desktop}
[Surface pro]

When I use my desktop as a client it works seamlessly, just as I expect it.
However, when I try to run the surface as a client, the mouse just get's stuck on the bottom of the screen, top left corner.
I don't know if it's a DPI issue, or if it's a problem with multiple monitor setup, which I still havent figured out what's the right way to set, is it making two monitors with the same name?

[luckcolors]

Hello.
I'm having the same issue. I'm willing to help you debug this, feel free to ask me things to test.

[luckcolors]

So, as a test i've built the latest version of the code from the repo and the fix you have committed https://github.com/debauchee/barrier/commit/075d4f4758f86c49ef0b5257a2de076b1d7d4569.
And it's working correctly so yeah this issue should be already fixed.
Please make an ufficial build whenever you get the chance. 😄
Thanks for your help.

Also i've noticed that the setup build script points to a folder wich doesn't exist.

[AdrianKoshka]

Also i've noticed that the setup build script points to a folder wich doesn't exist.

What do you mean? Could you get me log output from the build script?

[luckcolors]

The line in the build_installer.bat tries to CD into build/setup wich isn't created by the build script.
Instead two folders wich are named similarly are present: setup-wix, setup-inno.
I guess it's just a broken reference?

Log:

C:\barrier>build_installer.bat
Cannot find the specified file.
To build a 64-bit Windows installer:
 - set Q_BUILD_TYPE=Release in build_env.bat
 - also set other environmental overrides necessary for your build environment
 - run clean_build.bat to build Barrier and verify that it succeeds
 - re-run this script to create the installation package

[luckcolors]

Also i've noticed that the error mentions to change the variable Q_BUILD_TYPE=Release, but in the clean_build.cmd the variable is called B_BUILD_TYPE=Release.
Setting Q_BUILD_TYPE=Release does nothing.
(Also i did build successfully barrier by setting the proper variables before so no idea about this).

[AdrianKoshka]

did you read this? https://github.com/debauchee/barrier/wiki/Building-on-Windows Pretty sure you don't need to run build_installer.bat.

[luckcolors]

I didn't so that's probably why 😄 .

[luckcolors]

Turned on barrier again today, it broke again. Restarting barrier on both machines doesn't fix it.

[AdrianKoshka]

Oh, huh.

[p12tic]

In my experience sometimes barrier breaks the input system of either or both the server and the client. Restarting the machines themselves helps.

[FredNass]

Hello,

This happens on my side too with the following setup:

• Server : Linux Fedora 31 with barrier 2.3.2-snapshot-9080ce45 installed with Snap
• Client : macOS Catalina 10.15.2 with barrier 2.3.2 downloaded from Github

I installed 2.3.1 on a brand new Mac Mini running Mojave. I can swear it worked once (I could see and move the client's cursor by moving server's mouse) then the client's cursor disappeared forever. Actually, it got stucked in the bottom right corner of the client's screen.

Restarting Barrier on both server and client doesn't help.
Restarting both machines does not help either.
Uninstalling and reinstalling did not help
Upgrading macOS to Catalina did not help.

When both barriers and barrierc are started and connected, as soon as the server's cursor crosses the right screen edge (I use 2 screens on the server machine), it jumps to the client's bottom right of the screen and get stucked there.

The only way I can get my mouse back on the server is by stopping barrierc on the client.

Regards,
Frédéric.

[emilpaw]

Hello,
I have the same problem.

• Server : Windows 10 in a Dual Display Setup with barrier 2.3.2
• Client : Arch Linux with barrier 2.3.2

The problem only occurs if I have my second display connected. If I connect it, the cursor will change to the client and get stuck in the top right corner.
When I don't use my second display, everything runs fine.

My first display is an HiDPI one, so I doubt the HiDPI display itself is the root of the bug.