github-starred/barrier

Fork 0

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

[GH-ISSUE #333] Cursor stuk on the side of client but doesn't move beyond that #266

New issue

Open

opened 2026-05-05 05:52:40 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 05:52:40 -06:00

Owner

Originally created by @PAGuardado on GitHub (Jun 7, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/333

Operating Systems

Server: Windows 10 Version1809 (SO compilation 1776.503)

Client: Windows 10 Version1809 (SO compilation 17763.437)

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

I connect the client with the server using 'Auto config' and wait until the log reads that the computers are connected (I don't even know how to get the computers connected everytime)

After somehow achieving the connection I move the mouse from the server to the client, but on the first attempts the mouse bounces back when reaching the side of the screen.

After a few tries the log on both computers say "enter screen" and "leave sceen" respectively, but I don't see the mouse everywhere on the client screen.

I right click and get the menu right on the edge of the client's screen, but mouse is stuck there.

(Keyboard works alright on the client. I manage to test this using arrow keys)

I´m able to return the mouse to the server, but I'm unabe to use it on the client

Originally created by @PAGuardado on GitHub (Jun 7, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/333 ### Operating Systems ### Server: Windows 10 Version1809 (SO compilation 1776.503) Client: Windows 10 Version1809 (SO compilation 17763.437) ### Barrier Version ### 2.1.0-RELEASE-0b2dfd80 ### Steps to reproduce bug ### I connect the client with the server using 'Auto config' and wait until the log reads that the computers are connected (I don't even know how to get the computers connected everytime) After somehow achieving the connection I move the mouse from the server to the client, but on the first attempts the mouse bounces back when reaching the side of the screen. After a few tries the log on both computers say "enter screen" and "leave sceen" respectively, but I don't see the mouse everywhere on the client screen. I right click and get the menu right on the edge of the client's screen, but mouse is stuck there. (Keyboard works alright on the client. I manage to test this using arrow keys) I´m able to return the mouse to the server, but I'm unabe to use it on the client

gitea-mirror added the

bug

windows

labels 2026-05-05 05:52:40 -06:00

gitea-mirror commented

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

Author

Owner

@noisyshape commented on GitHub (Jun 8, 2019):

Unless I'm missing something, it sounds like the server has a high DPI setting which doesn't work correctly in 2.1.0. Try installing a more recent release.

@noisyshape commented on GitHub (Jun 8, 2019): Unless I'm missing something, it sounds like the server has a high DPI setting which doesn't work correctly in 2.1.0. Try installing a more recent release.

gitea-mirror commented

2026-05-05 05:52:45 -06:00

Author

Owner

@infinitempg commented on GitHub (Jun 9, 2019):

I'm having a similar issue here, but with a Windows/Mac server/client setup. When I connect my external display to my server and then try to move from the external display left to the client, the cursor gets stuck in the top left.

Not sure what to do since there's no 2.2.0 release for OSX.

@infinitempg commented on GitHub (Jun 9, 2019): I'm having a similar issue here, but with a Windows/Mac server/client setup. When I connect my external display to my server and then try to move from the external display left to the client, the cursor gets stuck in the top left. Not sure what to do since there's no 2.2.0 release for OSX.

gitea-mirror commented

2026-05-05 05:52:47 -06:00

Author

Owner

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

@infinitempg that's a different problem. Try restarting the server after connecting the new display. If that doesn't fix it, open a new issue.

@noisyshape commented on GitHub (Jun 10, 2019): @infinitempg that's a different problem. Try restarting the server after connecting the new display. If that doesn't fix it, open a new issue.

gitea-mirror commented

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

Author

Owner

@infinitempg commented on GitHub (Jun 10, 2019):

@noisyshape I managed to solve it by downgrading my Windows server down to 2.1.0.

@infinitempg commented on GitHub (Jun 10, 2019): @noisyshape I managed to solve it by downgrading my Windows server down to 2.1.0.

gitea-mirror commented

2026-05-05 05:52:50 -06:00

Author

Owner

@miguelangel-nubla commented on GitHub (Jun 10, 2019):

For me it was fixed by building and using the 2.2 linux client

@miguelangel-nubla commented on GitHub (Jun 10, 2019): For me it was fixed by building and using the 2.2 linux client

gitea-mirror commented

2026-05-05 05:52:51 -06:00

Author

Owner

@urugang commented on GitHub (Dec 19, 2022):

same to me. both 2.4.0-release on arch(server) and macbook(client).
when i ssh to arch(server), and kill barriers. it back to normal.

@urugang commented on GitHub (Dec 19, 2022): same to me. both 2.4.0-release on arch(server) and macbook(client). when i ssh to arch(server), and kill barriers. it back to normal.

No labels

Rows
Columns