[GH-ISSUE #731] Mouse cannot leave client #572

New issue

Open

opened 2026-05-05 06:42:10 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 06:42:10 -06:00

Owner

Originally created by @sstanojevic on GitHub (Jun 3, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/731

Operating Systems

Server: macOS 10.14.6
Client: Windows 10 1903 Build 18362.836

Barrier Version

Server: 2.3.2-Release-210c2b70
Client: 2.3.2-snapshot-210c2b70

Steps to reproduce bug

Mac screen is on the left, and PC screen is on the right, so going over Mac screen right edge, mouse goes to the PC.
On Mac open browser and load some page so browser has right scrollbar and make browser maximized so scroll bar is next to the right screen edge.
Grab right scrollbar with mouse, and move it up or down, and while moving scrollbar, make mouse cross right screen edge so it ends up on PC.
Mouse (and keyboard) is now on PC, and it cannot go back to the Mac side by going on PC screen left edge.

Other info

When did the problem start to occur?
Since I installed Barrier
Is there a way to work around it?
No, I restart Barrier service on client side so mouse/keyboard can be used back on the Mac side
Edit: Yes I found the workaround, I disabled option "Enable drag and drop file transfers", and mouse will not cross to PC when mouse button is pressed.
Does this bug prevent you from using Barrier entirely? Yes/No
No, it is just annoying

Originally created by @sstanojevic on GitHub (Jun 3, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/731 ### Operating Systems ### Server: macOS 10.14.6 Client: Windows 10 1903 Build 18362.836 ### Barrier Version ### Server: 2.3.2-Release-210c2b70 Client: 2.3.2-snapshot-210c2b70 ### Steps to reproduce bug ### 1. Mac screen is on the left, and PC screen is on the right, so going over Mac screen right edge, mouse goes to the PC. 2. On Mac open browser and load some page so browser has right scrollbar and make browser maximized so scroll bar is next to the right screen edge. 3. Grab right scrollbar with mouse, and move it up or down, and while moving scrollbar, make mouse cross right screen edge so it ends up on PC. 4. Mouse (and keyboard) is now on PC, and it cannot go back to the Mac side by going on PC screen left edge. ### Other info ### * When did the problem start to occur? Since I installed Barrier * Is there a way to work around it? No, I restart Barrier service on client side so mouse/keyboard can be used back on the Mac side **Edit:** Yes I found the workaround, I disabled option "Enable drag and drop file transfers", and mouse will not cross to PC when mouse button is pressed. * Does this bug prevent you from using Barrier entirely? Yes/No No, it is just annoying

gitea-mirror commented

2026-05-05 06:42:14 -06:00

Author

Owner

@isahann commented on GitHub (Jun 3, 2020):

Did you tried checking the logs (press F2)?

@isahann commented on GitHub (Jun 3, 2020): Did you tried checking the logs (press F2)?

gitea-mirror commented

2026-05-05 06:42:17 -06:00

Author

Owner

@sstanojevic commented on GitHub (Jun 3, 2020):

Yes, this is from the log:

[2020-06-03T19:43:29] INFO: switch from "TrlaBabaLan-2.local" to "SasaPC" at 0,1268
[2020-06-03T19:43:29] INFO: leaving screen
[2020-06-03T19:43:29] WARNING: cursor may not be visible
2020-06-03 19:43:29.970 barriers[42688:2339103] pid(42688)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2020-06-03 19:43:29.970 barriers[42688:2339103] pid(42688)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
[2020-06-03T19:43:52] NOTE: client "SasaPC" has disconnected

Last line where it said disconnected is me restarting client Barrier to get back mouse and keyboard to the server.
In general it is not strictly related to moving scrollbar, same thing happens when I cross screen edge with mouse button pressed.

@sstanojevic commented on GitHub (Jun 3, 2020): Yes, this is from the log: ``` [2020-06-03T19:43:29] INFO: switch from "TrlaBabaLan-2.local" to "SasaPC" at 0,1268 [2020-06-03T19:43:29] INFO: leaving screen [2020-06-03T19:43:29] WARNING: cursor may not be visible 2020-06-03 19:43:29.970 barriers[42688:2339103] pid(42688)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2020-06-03 19:43:29.970 barriers[42688:2339103] pid(42688)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! [2020-06-03T19:43:52] NOTE: client "SasaPC" has disconnected ``` Last line where it said disconnected is me restarting client Barrier to get back mouse and keyboard to the server. In general it is not strictly related to moving scrollbar, same thing happens when I cross screen edge with mouse button pressed.

gitea-mirror commented

2026-05-05 06:42:20 -06:00

Author

Owner

@sstanojevic commented on GitHub (Jun 3, 2020):

Actually I found the workaround, I disabled option "Enable drag and drop file transfers", and mouse will not cross to the PC when mouse button is pressed.

@sstanojevic commented on GitHub (Jun 3, 2020): Actually I found the workaround, I disabled option "Enable drag and drop file transfers", and mouse will not cross to the PC when mouse button is pressed.

gitea-mirror commented

2026-05-05 06:42:22 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 20, 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 20, 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:42:24 -06:00

Author

Owner

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

Let's not close valid bug reports for no reason.

@p12tic commented on GitHub (Jan 10, 2021): Let's not close valid bug reports for no reason.