[GH-ISSUE #612] Mouse will not move back to old screen #482

New issue

Open

opened 2026-05-05 06:30:49 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:30:49 -06:00

Owner

Originally created by @tp199314 on GitHub (Apr 6, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/612

Operating Systems

Server: Windows 10

Client: Windows 10

Barrier Version

Steps to reproduce bug

Moved with the mouse the other screen
Tried to move back to the old screen
The mouse does not switch to the old screen and bounced back to the active screen

Other info

When did the problem start to occur? When I try to switch screen Screen1 to Screen2 is ok, back the way back is not possible.
Is there a way to work around it? Yes, you can stop and start Barrier on the client
Does this bug prevent you from using Barrier entirely? Not entierly, but its a huge disadvantage.

[2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3186,784
[2020-04-06T08:26:26] INFO: entering screen
[2020-04-06T08:26:26] INFO: switch from "Screen1" to "Screen2" at 0,1090
[2020-04-06T08:26:26] INFO: leaving screen
[2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3179,1079
[2020-04-06T08:26:26] INFO: entering screen
[2020-04-06T08:26:26] INFO: switch from "Screen1" to "Screen2" at 0,1090
[2020-04-06T08:26:26] INFO: leaving screen
[2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3162,1079
[2020-04-06T08:26:26] INFO: entering screen
[2020-04-06T08:26:26] INFO: switch from "Screen1" to "Screen2" at 0,1090
[2020-04-06T08:26:26] INFO: leaving screen
[2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3173,1079
[2020-04-06T08:26:26] INFO: entering screen
[2020-04-06T08:26:26] INFO: switch from "Screen1" to "Screen2" at 0,1090
[2020-04-06T08:26:26] INFO: leaving screen
[2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3182,1079
[2020-04-06T08:26:26] INFO: entering screen

Originally created by @tp199314 on GitHub (Apr 6, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/612 ### Operating Systems ### Server: Windows 10 Client: Windows 10 ### Barrier Version ### ### Steps to reproduce bug ### 1. Moved with the mouse the other screen 2. Tried to move back to the old screen 3. The mouse does not switch to the old screen and bounced back to the active screen ### Other info ### When did the problem start to occur? When I try to switch screen Screen1 to Screen2 is ok, back the way back is not possible. Is there a way to work around it? Yes, you can stop and start Barrier on the client Does this bug prevent you from using Barrier entirely? Not entierly, but its a huge disadvantage. [2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3186,784 [2020-04-06T08:26:26] INFO: entering screen [2020-04-06T08:26:26] INFO: switch from "Screen1" to "Screen2" at 0,1090 [2020-04-06T08:26:26] INFO: leaving screen [2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3179,1079 [2020-04-06T08:26:26] INFO: entering screen [2020-04-06T08:26:26] INFO: switch from "Screen1" to "Screen2" at 0,1090 [2020-04-06T08:26:26] INFO: leaving screen [2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3162,1079 [2020-04-06T08:26:26] INFO: entering screen [2020-04-06T08:26:26] INFO: switch from "Screen1" to "Screen2" at 0,1090 [2020-04-06T08:26:26] INFO: leaving screen [2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3173,1079 [2020-04-06T08:26:26] INFO: entering screen [2020-04-06T08:26:26] INFO: switch from "Screen1" to "Screen2" at 0,1090 [2020-04-06T08:26:26] INFO: leaving screen [2020-04-06T08:26:26] INFO: switch from "Screen2" to "Screen1" at 3182,1079 [2020-04-06T08:26:26] INFO: entering screen

gitea-mirror added the

bug

label 2026-05-05 06:30:49 -06:00

gitea-mirror commented

2026-05-05 06:30:53 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 25, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 25, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:30:55 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

@steve9164 @dired @okke-formsma @tp199314 Could it be that the screen dimensions in pixels are different and mouse hits the edge at a location where there's no screen on the other side? One way to check this is to more the mouse along whole edge trying to move it to the other screen. At some point it should move.

It would be great if this could be checked because if it's not possible to move mouse to another screen at all then it's a serious bug.

@p12tic commented on GitHub (Jan 10, 2021): @steve9164 @dired @okke-formsma @tp199314 Could it be that the screen dimensions in pixels are different and mouse hits the edge at a location where there's no screen on the other side? One way to check this is to more the mouse along whole edge trying to move it to the other screen. At some point it should move. It would be great if this could be checked because if it's not possible to move mouse to another screen at all then it's a serious bug.

gitea-mirror referenced this issue

2026-05-05 06:35:23 -06:00

[GH-ISSUE #657] Suggestion: provide visual feedback in main barrier window if scroll lock is on (cursor locked to screen) #517