Barrier: Moving From Windows to Ubuntu doesn't work

[rainybreeze777]

Operating Systems

Server: Windows 10 version 1709 (OS build 16299.431)

Client: Ubuntu 18.04 LTS

Barrier Version

2.1.0-Release

Steps to reproduce bug

1. Establish server on Windows
2. Establish client on ubuntu
3. Set up server monitor configuration such that ubuntu is on the left of windows
4. Log reports connection is successful
5. Attempts to move cursor from windows to the left of the screen to ubuntu machine
6. Cursor disappears on Windows, cursor does not appear on Ubuntu
7. Ubuntu can accept keyboard strokes and mouse clicks, but cursor does not move
8. Cannot move cursor back to Windows, had to manually stop Ubuntu client for the cursor to return to windows

Other info

• When did the problem start to occur?
  When I just finished setting up Barrier and establish connection, first attempt at using
• Is there a way to work around it? No
• Does this bug prevent you from using Barrier entirely? Yes

[AurisAudentis]

I can attest to the same issue on Linux Mint Sylvia 18.3.
Is there any workaround/fix availiable or in the works?

UPDATE:
found a workaround: properties of the executable barrier -> compatibility -> all users -> High dpi options -> check all the boxes.
After this, the program seems to work as intended. This was a known problem in synergy.

[dayne]

Sounds like these issues from synergy-core:

• https://github.com/symless/synergy-core/issues/4041
• https://github.com/symless/synergy-core/issues/6070

[walker0643]

Can you try 075d4f4 and report back? If you're not comfortable building from source you could wait for the next release, 2.2. Thanks!

[walker0643]

Please reopen if you still have this issue after upgrading to 2.2. Thanks!

[xurongchen]

I can attest to the same issue on Linux Mint Sylvia 18.3.
Is there any workaround/fix availiable or in the works?

UPDATE:
found a workaround: properties of the executable barrier -> compatibility -> all users -> High dpi options -> check all the boxes.
After this, the program seems to work as intended. This was a known problem in synergy.

Thanks! However I solved the problem by setting the executable 'barrriers' but not the 'barrier'.

[ScriptingDad]

@AurisAudentis your workaround still worked in 2.3.1. Thanks! not sure why it worked but I've been playing with this for 4 hours now and this is the only thing that did the trick.

[stevesobol]

I'm having the same problem with macOS, as detailed in a bug that was marked as a dupe of this one. It existed in Synergy 1.8 and the workaround there was to turn off clipboard sharing, which I have done, but I'd rather have it enabled.