#222 - [GH-ISSUE #273] Pointer disappearing - HiDPI related? - github-starred/barrier

gitea-mirror commented

2026-05-05 05:42:57 -06:00

Owner

Originally created by @Mibo5354 on GitHub (Mar 27, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/273

Operating Systems

Server: Windows 10 1809 - 1920x1080 with 125% scaling

Client: Manjaro Linux - 1366x786

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

Turn on Barrier and connect the machines
On server
Move mouse around and try to move to the other machine
Pointer disappears and does not reappear
Disconnect from the client machine to restore pointer

Other info

When did the problem start to occur? Since I set it up
Is there a way to work around it? No, I tried tweaking the hidpi setting for barriers.exe but nothing worked. HiDPI settings has changed from 1709 hence workaround listed in #42 is not applicable. On a side note, is there binaries for 2.2 mentioned in the other issue so I can see if it is fixed?
Does this bug prevent you from using Barrier entirely? Yes

There seem to be a window of movement on the server machine that is equal to the resolution of the client. The window starts from the top left corner and I can move the pointer without it disappearing but when it moves out it disappears until I disconnect.
This occurs on synergy [1.4.12] as well, that's why I tried out barrier.

Originally created by @Mibo5354 on GitHub (Mar 27, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/273 ### Operating Systems ### Server: Windows 10 1809 - 1920x1080 with 125% scaling Client: Manjaro Linux - 1366x786 ### Barrier Version ### 2.1.0-RELEASE-0b2dfd80 ### Steps to reproduce bug ### 1. Turn on Barrier and connect the machines 2. On server 3. Move mouse around and try to move to the other machine 4. Pointer disappears and does not reappear 5. Disconnect from the client machine to restore pointer ### Other info ### * When did the problem start to occur? Since I set it up * Is there a way to work around it? No, I tried tweaking the hidpi setting for barriers.exe but nothing worked. HiDPI settings has changed from 1709 hence workaround listed in #42 is not applicable. On a side note, is there binaries for 2.2 mentioned in the other issue so I can see if it is fixed? * Does this bug prevent you from using Barrier entirely? Yes There seem to be a window of movement on the server machine that is equal to the resolution of the client. The window starts from the top left corner and I can move the pointer without it disappearing but when it moves out it disappears until I disconnect. This occurs on synergy [1.4.12] as well, that's why I tried out barrier.

gitea-mirror

2026-05-05 05:42:57 -06:00

closed this issue
added the
bug

HiDPI
labels

gitea-mirror commented

2026-05-05 05:43:03 -06:00

Author

Owner

@pgetsos commented on GitHub (Apr 6, 2019):

Have the same issue, workaround didn't work as well

@pgetsos commented on GitHub (Apr 6, 2019): Have the same issue, workaround didn't work as well

gitea-mirror commented

2026-05-05 05:43:04 -06:00

Author

Owner

@tungmeister commented on GitHub (Apr 8, 2019):

I've got the same issue, my mouse will disappear after moving ~75% over my main monitor and it's practically impossible to get it to appear again.

@tungmeister commented on GitHub (Apr 8, 2019): I've got the same issue, my mouse will disappear after moving ~75% over my main monitor and it's practically impossible to get it to appear again.

gitea-mirror commented

2026-05-05 05:43:05 -06:00

Author

Owner

@noisyshape commented on GitHub (Apr 9, 2019):

I suspect this is the same issue as #206, #194, and #94. The problem is resolved for me with a 2.2.0 build.

@noisyshape commented on GitHub (Apr 9, 2019): I suspect this is the same issue as #206, #194, and #94. The problem is resolved for me with a 2.2.0 build.

gitea-mirror commented

2026-05-05 05:43:06 -06:00

Author

Owner

@Mibo5354 commented on GitHub (Apr 10, 2019):

@noisyshape is there binaries for a 2.2.0 build?

@Mibo5354 commented on GitHub (Apr 10, 2019): @noisyshape is there binaries for a 2.2.0 build?

gitea-mirror commented

2026-05-05 05:43:07 -06:00

Author

Owner

@noisyshape commented on GitHub (Apr 10, 2019):

@Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough.

@noisyshape commented on GitHub (Apr 10, 2019): @Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough.

gitea-mirror commented

2026-05-05 05:43:09 -06:00

Author

Owner

@Mibo5354 commented on GitHub (Apr 10, 2019):

@noisyshape is the instructions on the wiki still good, or is there any changes I should know about?

@Mibo5354 commented on GitHub (Apr 10, 2019): @noisyshape is the instructions on the wiki still good, or is there any changes I should know about?

gitea-mirror commented

2026-05-05 05:43:11 -06:00

Author

Owner

@noisyshape commented on GitHub (Apr 10, 2019):

@Mibo5354 The instructions are good. Just follow them carefully. Once you have the binaries, stop all Barrier processes and copy everything into your existing installation folder. If you can't complete the build, start a new issue and I'll try to help.

Edit: There is one problem that I know of. ~~Qt doesn't support VS2019 yet, so you'll need VS2017 to follow the build guide.~~ If you use VS2019, you'll have to use the VS2017 Qt libraries and edit the clean_build.bat string Visual Studio 15 2017 Win64 to Visual Studio 16 2019. The resulting build seems to be fine.

@noisyshape commented on GitHub (Apr 10, 2019): @Mibo5354 The instructions are good. Just follow them carefully. Once you have the binaries, stop all Barrier processes and copy everything into your existing installation folder. If you can't complete the build, start a new issue and I'll try to help. Edit: There is one problem that I know of. ~~Qt doesn't support VS2019 yet, so you'll need VS2017 to follow the build guide.~~ If you use VS2019, you'll have to use the VS2017 Qt libraries and edit the clean_build.bat string ``Visual Studio 15 2017 Win64`` to ``Visual Studio 16 2019``. The resulting build seems to be fine.

gitea-mirror commented

2026-05-05 05:43:15 -06:00

Author

Owner

@sommoMicc commented on GitHub (Apr 12, 2019):

@Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough.

Plz can you upload somewhere (like in google drive) the 2.2.0 Windows build?

@sommoMicc commented on GitHub (Apr 12, 2019): > @Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough. Plz can you upload somewhere (like in google drive) the 2.2.0 Windows build?

gitea-mirror commented

2026-05-05 05:43:17 -06:00

Author

Owner

@Mibo5354 commented on GitHub (Apr 12, 2019):

@sommoMicc Here's the build that I compiled today https://drive.google.com/file/d/1S3Z5mLQT63ZTWIsjiTyzL9qdIjoE-MW1/view?usp=sharing

@Mibo5354 commented on GitHub (Apr 12, 2019): @sommoMicc Here's the build that I compiled today https://drive.google.com/file/d/1S3Z5mLQT63ZTWIsjiTyzL9qdIjoE-MW1/view?usp=sharing

gitea-mirror commented

2026-05-05 05:43:20 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Apr 12, 2019):

@Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough.

Plz can you upload somewhere (like in google drive) the 2.2.0 Windows build?

This should be happening soon-ish™¹? Waiting for a PR to fix something with the windows installer script. Then I'll be able to make a build and official release.

Soon means probably within the next week, going on a vacation, and most likely won't be bringing my laptop with me.

@AdrianKoshka commented on GitHub (Apr 12, 2019): > > @Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough. > > Plz can you upload somewhere (like in google drive) the 2.2.0 Windows build? This should be happening soon-ish™<sup>1</sup>? Waiting for a PR to fix something with the windows installer script. Then I'll be able to make a build and official release. 1. Soon means probably within the next week, going on a vacation, and most likely won't be bringing my laptop with me.

gitea-mirror commented

2026-05-05 05:43:22 -06:00

Author

Owner

@Mibo5354 commented on GitHub (Apr 14, 2019):

The issue is solved with the newer build, should I close this issue?

@Mibo5354 commented on GitHub (Apr 14, 2019): The issue is solved with the newer build, should I close this issue?

gitea-mirror commented

2026-05-05 05:43:24 -06:00

Author

Owner

@sommoMicc commented on GitHub (Apr 17, 2019):

The issue is solved with the newer build, should I close this issue?

Yes. Now it works

@sommoMicc commented on GitHub (Apr 17, 2019): > The issue is solved with the newer build, should I close this issue? Yes. Now it works

gitea-mirror commented

2026-05-05 05:43:25 -06:00

Author

Owner

@gerroon commented on GitHub (Jan 9, 2022):

Hi,

I just bought a 4k monitor and I am hitting this issue. I use 2.4.0 on all 3 Pcs. The servers is a Win10 x64 4K monitor. The cursor disappears around the edges of the 4K monitor, it looks like the cursor is somewhere on one of the clients but hard to tell, no logical or visual control is possible.

@gerroon commented on GitHub (Jan 9, 2022): Hi, I just bought a 4k monitor and I am hitting this issue. I use 2.4.0 on all 3 Pcs. The servers is a Win10 x64 4K monitor. The cursor disappears around the edges of the 4K monitor, it looks like the cursor is somewhere on one of the clients but hard to tell, no logical or visual control is possible.

gitea-mirror commented

2026-05-05 05:43:27 -06:00

Author

Owner

@gregors613 commented on GitHub (Jan 10, 2022):

I've just installed 2.4.0.1 on a Windows 10 machine with 2 monitors( 1K and 4K ) and on Linux with the mirrored ( 4K and 1K ). The win10 machine is configured as the server and the linux machine as the client. Monitors are arranged left to right Win10 1K Win10 4K Linux 4K Linux 1K. When I start the server and move my mouse around on the windows machine, it will suddenly disappear and if I press the menu key, the menu on the linux machine appears ( no mouse cursor ) and the following appears in the log

[2022-01-10T11:20:40] DEBUG2: clamp to right of "gregors-linux-pc"
[2022-01-10T11:20:40] DEBUG2: clamp to bottom of "gregors-linux-pc"

@gregors613 commented on GitHub (Jan 10, 2022): I've just installed 2.4.0.1 on a Windows 10 machine with 2 monitors( 1K and 4K ) and on Linux with the mirrored ( 4K and 1K ). The win10 machine is configured as the server and the linux machine as the client. Monitors are arranged left to right Win10 1K Win10 4K Linux 4K Linux 1K. When I start the server and move my mouse around on the windows machine, it will suddenly disappear and if I press the menu key, the menu on the linux machine appears ( no mouse cursor ) and the following appears in the log [2022-01-10T11:20:40] DEBUG2: clamp to right of "gregors-linux-pc" [2022-01-10T11:20:40] DEBUG2: clamp to bottom of "gregors-linux-pc"

gitea-mirror commented

2026-05-05 05:43:29 -06:00

Author

Owner

@gerroon commented on GitHub (Jan 10, 2022):

@gregors613 going back to 2.3.4 fixes my issue.

@gerroon commented on GitHub (Jan 10, 2022): @gregors613 going back to 2.3.4 fixes my issue.

gitea-mirror commented

2026-05-05 05:43:31 -06:00

Author

Owner

@gregors613 commented on GitHub (Jan 11, 2022):

@gerroon, thanks for the advice. downgrading to 2.3.4 on the windows machine worked.

@gregors613 commented on GitHub (Jan 11, 2022): @gerroon, thanks for the advice. downgrading to 2.3.4 on the windows machine worked.

gitea-mirror commented

2026-05-05 05:43:33 -06:00

Author

Owner

@qmdnls commented on GitHub (Jan 26, 2022):

Same issue here on 2.4.0 to provide another data point. Ubuntu server with Windows 10 client on a 4K monitor (with 150% fractional scaling). Monitors are arranged side by side and when moving the mouse over to the Windows client the cursor does not appear for a few seconds.

Going back to 2.3.4 solved the issue for me too.

@qmdnls commented on GitHub (Jan 26, 2022): Same issue here on 2.4.0 to provide another data point. Ubuntu server with Windows 10 client on a 4K monitor (with 150% fractional scaling). Monitors are arranged side by side and when moving the mouse over to the Windows client the cursor does not appear for a few seconds. Going back to 2.3.4 solved the issue for me too.

gitea-mirror commented

2026-05-05 05:43:36 -06:00

Author

Owner

@spacewalk01 commented on GitHub (Jan 13, 2026):

@gerroon same downgrade on windows works, finally ( - ⌓ - )

@spacewalk01 commented on GitHub (Jan 13, 2026): @gerroon same downgrade on windows works, finally ( - ⌓ - )

Rows
Columns

[GH-ISSUE #273] Pointer disappearing - HiDPI related? #222

Operating Systems

Barrier Version

Steps to reproduce bug

Other info