github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #42] Moving From Windows to Ubuntu doesn't work #33

New issue

Closed

opened 2026-05-05 04:48:40 -06:00 by gitea-mirror · 16 comments

gitea-mirror commented

2026-05-05 04:48:40 -06:00

Owner

Originally created by @rainybreeze777 on GitHub (May 22, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/42

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

Establish server on Windows
Establish client on ubuntu
Set up server monitor configuration such that ubuntu is on the left of windows
Log reports connection is successful
Attempts to move cursor from windows to the left of the screen to ubuntu machine
Cursor disappears on Windows, cursor does not appear on Ubuntu
Ubuntu can accept keyboard strokes and mouse clicks, but cursor does not move
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

Originally created by @rainybreeze777 on GitHub (May 22, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/42 ### 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

gitea-mirror

2026-05-05 04:48:40 -06:00

closed this issue
added the
bug

windows

linux
labels

gitea-mirror commented

2026-05-05 04:48:46 -06:00

Author

Owner

@AurisAudentis commented on GitHub (Jun 9, 2018):

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.

@AurisAudentis commented on GitHub (Jun 9, 2018): 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.

gitea-mirror commented

2026-05-05 04:48:49 -06:00

Author

Owner

@dayne commented on GitHub (Jun 10, 2018):

Sounds like these issues from synergy-core:

@dayne commented on GitHub (Jun 10, 2018): Sounds like these issues from synergy-core: * https://github.com/symless/synergy-core/issues/4041 * https://github.com/symless/synergy-core/issues/6070

gitea-mirror commented

2026-05-05 04:48:52 -06:00

Author

Owner

@walker0643 commented on GitHub (Sep 8, 2018):

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 commented on GitHub (Sep 8, 2018): 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!

gitea-mirror commented

2026-05-05 04:48:56 -06:00

Author

Owner

@walker0643 commented on GitHub (Sep 8, 2018):

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

@walker0643 commented on GitHub (Sep 8, 2018): Please reopen if you still have this issue after upgrading to 2.2. Thanks!

gitea-mirror commented

2026-05-05 04:48:58 -06:00

Author

Owner

@xurongchen commented on GitHub (Feb 24, 2019):

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'.

@xurongchen commented on GitHub (Feb 24, 2019): > 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'.

gitea-mirror commented

2026-05-05 04:49:01 -06:00

Author

Owner

@ScriptingDad commented on GitHub (Aug 10, 2019):

@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.

@ScriptingDad commented on GitHub (Aug 10, 2019): @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.

gitea-mirror commented

2026-05-05 04:49:04 -06:00

Author

Owner

@stevesobol commented on GitHub (Dec 23, 2019):

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.

@stevesobol commented on GitHub (Dec 23, 2019): 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.

gitea-mirror commented

2026-05-05 04:49:06 -06:00

Author

Owner

@rstacruz commented on GitHub (Feb 14, 2022):

executable barrier -> compatibility -> all users -> High dpi options -> check all the boxes.

I'm on barrier 2.4.0 in Windows 11, and what worked for me was this, but on the executable barriers.exe (not barrier.exe).

@rstacruz commented on GitHub (Feb 14, 2022): > executable barrier -> compatibility -> all users -> High dpi options -> check all the boxes. I'm on barrier 2.4.0 in Windows 11, and what worked for me was this, but on the executable `barriers.exe` (not `barrier.exe`).

gitea-mirror commented

2026-05-05 04:49:08 -06:00

Author

Owner

@liamjwang commented on GitHub (Apr 24, 2022):

@MyAlfisti Uninstalling v2.4.0 and installing v2.3.4 on Windows 11 (barrier server) fixed the problem for me.
I'm using the barrier client v2.4.0 on Ubuntu 18.04.

@liamjwang commented on GitHub (Apr 24, 2022): @MyAlfisti Uninstalling v2.4.0 and installing v2.3.4 on Windows 11 (barrier server) fixed the problem for me. I'm using the barrier client v2.4.0 on Ubuntu 18.04.

gitea-mirror commented

2026-05-05 04:49:09 -06:00

Author

Owner

@DarwinDemian commented on GitHub (Jun 21, 2022):

Found a fix, this was happening because of the screen scaling. I was using 100% with Linux, and 125% on Windows. After setting the scaling to 100% on Windows, the mouse started working on the other screen.

@DarwinDemian commented on GitHub (Jun 21, 2022): Found a fix, this was happening because of the screen scaling. I was using 100% with Linux, and 125% on Windows. After setting the scaling to 100% on Windows, the mouse started working on the other screen.

gitea-mirror commented

2026-05-05 04:49:11 -06:00

Author

Owner

@sexycode commented on GitHub (Jul 20, 2022):

Found a fix, this was happening because of the screen scaling. I was using 100% with Linux, and 125% on Windows. After setting the scaling to 100% on Windows, the mouse started working on the other screen.

thanks change to 100% on windows , mouse is OK

@sexycode commented on GitHub (Jul 20, 2022): > Found a fix, this was happening because of the screen scaling. I was using 100% with Linux, and 125% on Windows. After setting the scaling to 100% on Windows, the mouse started working on the other screen. thanks change to 100% on windows , mouse is OK

gitea-mirror commented

2026-05-05 04:49:13 -06:00

Author

Owner

@ultrageek commented on GitHub (Mar 24, 2023):

I'm not seeing any setting to change screen scaling. Where is this, please?

Server: Windows 10 (V2.4.0)
Client: MacOS (Ventura 13.0)

@ultrageek commented on GitHub (Mar 24, 2023): I'm not seeing any setting to change screen scaling. Where is this, please? Server: Windows 10 (V2.4.0) Client: MacOS (Ventura 13.0)

gitea-mirror commented

2026-05-05 04:49:14 -06:00

Author

Owner

@xyz1001 commented on GitHub (Mar 30, 2023):

Another resolution is change the barrier exe compability setting. Right click exe, select properties, Compability and click "Change high DPI settings" button, check "override high DPI scaling behavior" and select Application. Barrier will works ok after restart.

@xyz1001 commented on GitHub (Mar 30, 2023): Another resolution is change the barrier exe compability setting. Right click exe, select properties, Compability and click "Change high DPI settings" button, check "override high DPI scaling behavior" and select Application. Barrier will works ok after restart. ![image](https://user-images.githubusercontent.com/14332136/228723392-532b9629-3366-44a8-8a7e-32bc301b75af.png)

gitea-mirror commented

2026-05-05 04:49:17 -06:00

Author

Owner

@SteveClement commented on GitHub (Aug 11, 2023):

The DPI settings tweak still works ;)

@SteveClement commented on GitHub (Aug 11, 2023): The DPI settings tweak still works ;)

gitea-mirror commented

2026-05-05 04:49:21 -06:00

Author

Owner

@Migelo commented on GitHub (Nov 7, 2023):