[GH-ISSUE #501] OSX 10.5.1 - Windows 10 mouse issue between client and server #393

New issue

Open

opened 2026-05-05 06:15:53 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:15:53 -06:00

Owner

Originally created by @adamsewell on GitHub (Nov 20, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/501

Operating Systems

Server: Windows 10 64 Tiara

Client: OSX 10.15.1

Barrier Version

2.3.2 on both

Steps to reproduce bug

Connect Client to Server
Mouse will not move between client and server though it does appear to connect to each other.

Other info

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

Also to note, I have a dual monitor setup on my Windows 10 server.

Originally created by @adamsewell on GitHub (Nov 20, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/501 ### Operating Systems ### Server: Windows 10 64 Tiara Client: OSX 10.15.1 ### Barrier Version ### 2.3.2 on both ### Steps to reproduce bug ### 1. Connect Client to Server 2. Mouse will not move between client and server though it does appear to connect to each other. ### Other info ### * When did the problem start to occur? When I upgraded to 10.15 * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? Yes Also to note, I have a dual monitor setup on my Windows 10 server.

gitea-mirror added the

macOS

bug

windows

labels 2026-05-05 06:15:53 -06:00

gitea-mirror commented

2026-05-05 06:15:57 -06:00

Author

Owner

@acecena commented on GitHub (Nov 21, 2019):

Same setup up here and same problem also. I can add that there is a message on the log that says that the cursor "may not be visible". Image attached.

@acecena commented on GitHub (Nov 21, 2019): Same setup up here and same problem also. I can add that there is a message on the log that says that the cursor "may not be visible". Image attached. ![Captura de Pantalla 2019-11-21 a la(s) 16 00 42](https://user-images.githubusercontent.com/18712953/69380629-78c4e580-0c78-11ea-8aa6-9cb8c6e72c11.png)

gitea-mirror commented

2026-05-05 06:16:02 -06:00

Author

Owner

@oristopo commented on GitHub (Nov 26, 2019):

FWIW, "cursor may not be visible" is logged on my macOS 10.13.6 client, but mouse DOES WORK from Windows 10 as barrier server. I >>guess<< that warning is about client mouse cursor being invisible
after server mouse moves away until pressing left button on client mouse (if any).

@oristopo commented on GitHub (Nov 26, 2019): FWIW, "cursor may not be visible" is logged on my macOS 10.13.6 client, but mouse DOES WORK from Windows 10 as barrier server. I >>guess<< that warning is about client mouse cursor being invisible after server mouse moves away until pressing left button on client mouse (if any).

gitea-mirror commented

2026-05-05 06:16:04 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 1, 2020):

Is this issue still an issue for you? Please do comment and let us know! Alternatively, you may close the issue yourself if it is no longer an problem

@github-actions[bot] commented on GitHub (Oct 1, 2020): Is this issue still an issue for you? Please do comment and let us know! Alternatively, you may close the issue yourself if it is no longer an problem

gitea-mirror referenced this issue

2026-05-05 07:59:01 -06:00

[PR #653] [MERGED] Fix TIS/TSM in logs #1668