[GH-ISSUE #115] Log out of windows (server side),the cursor gets stuck if you move it to client #90

New issue

Open

opened 2026-05-05 05:13:56 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 05:13:56 -06:00

Owner

Originally created by @uj on GitHub (Aug 20, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/115

Operating Systems

Server: Windows 10 1703 15063

Client: Windows 7 7601

Barrier Version

2.1.0 downloaded binary from github

Steps to reproduce bug

Setup Windows 10 as server, setup windows 7 as client. Make sure it seems to be working properly. Log out of Windows on the server, so that you are on the login screen. Do not log in. Move the mouse cursor over to the client screen. As soon as the mouse hits the client screen, it jumps to the right side of the client, and can no longer be moved at all (but you can right-click and bring up the right-click menu on the client). Now you can't get back to the server. The only way to fix it is to stop the Barrier service on client, and then the mouse goes back to the server.

Other info

When did the problem start to occur? Always
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? Yes

Put anything else you can think of here.

Originally created by @uj on GitHub (Aug 20, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/115 ### Operating Systems ### Server: Windows 10 1703 15063 Client: Windows 7 7601 ### Barrier Version ### 2.1.0 downloaded binary from github ### Steps to reproduce bug ### Setup Windows 10 as server, setup windows 7 as client. Make sure it seems to be working properly. Log out of Windows on the server, so that you are on the login screen. Do not log in. Move the mouse cursor over to the client screen. As soon as the mouse hits the client screen, it jumps to the right side of the client, and can no longer be moved at all (but you can right-click and bring up the right-click menu on the client). Now you can't get back to the server. The only way to fix it is to stop the Barrier service on client, and then the mouse goes back to the server. ### Other info ### * When did the problem start to occur? Always * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? Yes Put anything else you can think of here.

gitea-mirror added the

bug

windows

labels 2026-05-05 05:13:56 -06:00

gitea-mirror commented

2026-05-05 05:14:02 -06:00

Author

Owner

@bartekgn commented on GitHub (Sep 21, 2018):

Windows 7 as server locks too. Fingerprint sensor, keyboard, and mouse not working.

@bartekgn commented on GitHub (Sep 21, 2018): Windows 7 as server locks too. Fingerprint sensor, keyboard, and mouse not working.

gitea-mirror referenced this issue

2026-05-05 07:56:25 -06:00

[PR #90] [MERGED] merge travis CI patches (and others) #1562

gitea-mirror referenced this issue

2026-05-05 07:56:25 -06:00

[PR #91] [CLOSED] [TEST ME!] Smarter Zeroconf Address #1563

gitea-mirror referenced this issue

2026-05-05 07:57:46 -06:00

[PR #388] Smartzeroconf new PR #1617