[GH-ISSUE #1088] Host and client both lose mouse after host and client both wake from sleep #869

New issue

Open

opened 2026-05-05 07:14:05 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 07:14:05 -06:00

Owner

Originally created by @caitp on GitHub (Mar 3, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1088

Describe the bug
Host (Windows 10) and client (MacBook Pro on Big Sur) both lose access to host mouse after waking from sleep.

Presumably, the order of which machine fell asleep matters, as well as which machine currently is controlling the mouse, and if network connectivity is terminated by sleeping or not. I'm not positive which factors specifically were at play in this scenario, though.

To Reproduce

Steps to reproduce the behavior:

I'm not sure exactly.

Expected behavior
Ideally, the host would stop trying to pass on input messages to the client if the client is no longer ACK-ing, and a failsafe hotkey to shutdown the service could be provided by default.

Screenshots
N/A

Desktop (please complete the following information):
Host:

OS: Windows 10
Barrier version 2.2.3-release-3395cca9

Client:

OS: MacOS Big Sur 11.2.2
Barrier version 2.2.3-release-3395cca9

Additional context

N/A

Originally created by @caitp on GitHub (Mar 3, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1088 **Describe the bug** Host (Windows 10) and client (MacBook Pro on Big Sur) both lose access to host mouse after waking from sleep. Presumably, the order of which machine fell asleep matters, as well as which machine currently is controlling the mouse, and if network connectivity is terminated by sleeping or not. I'm not positive which factors specifically were at play in this scenario, though. **To Reproduce** Steps to reproduce the behavior: - I'm not sure exactly. **Expected behavior** Ideally, the host would stop trying to pass on input messages to the client if the client is no longer ACK-ing, and a failsafe hotkey to shutdown the service could be provided by default. **Screenshots** N/A **Desktop (please complete the following information):** Host: - OS: Windows 10 - Barrier version 2.2.3-release-3395cca9 Client: - OS: MacOS Big Sur 11.2.2 - Barrier version 2.2.3-release-3395cca9 **Additional context** N/A

gitea-mirror commented

2026-05-05 07:14:07 -06:00

Author

Owner

@RogerHall commented on GitHub (Mar 11, 2021):

I often experience this as well, or at least something very similar.

Monitor - Left - mDP input from windows 10 PC - Host
Monitor - Middle - mDP input from windows 10 PC
Monitor - Middle - hdmi input from MAC Book Pro
Monitor - Right - laptop monitor on MAC Book Pro - Client

The keyboard and mouse are attached to the windows 10 PC.

If I work on only the PC, then I never have any issues. I use DMM (Dell Display Manager) to switch middle monitor between the PC and the MAC, but I don't think that is related. I could use input selection button on monitor.

When I am logged into both and the have both gone to sleep, I often find that the mouse is stuck on the MAC.

What I do in this situation is to turn off the Left and Middle monitors which are attached to the PC and then turn them back on again. So long as I move the mouse to the left after this, the PC (Barrier Host) picks up the mouse and keyboard again. I suspect this works because the monitors are also connected to the PC's USB ports. Toggling the power on the monitors causes the sound to be made when new USB devices are connected. The mouse and keyboard do connect direct to the PC though and do not connect via the monitors.

@RogerHall commented on GitHub (Mar 11, 2021): I often experience this as well, or at least something very similar. Monitor - Left - mDP input from windows 10 PC - Host Monitor - Middle - mDP input from windows 10 PC Monitor - Middle - hdmi input from MAC Book Pro Monitor - Right - laptop monitor on MAC Book Pro - Client The keyboard and mouse are attached to the windows 10 PC. If I work on only the PC, then I never have any issues. I use DMM (Dell Display Manager) to switch middle monitor between the PC and the MAC, but I don't think that is related. I could use input selection button on monitor. When I am logged into both and the have both gone to sleep, I often find that the mouse is stuck on the MAC. What I do in this situation is to turn off the Left and Middle monitors which are attached to the PC and then turn them back on again. So long as I move the mouse to the left after this, the PC (Barrier Host) picks up the mouse and keyboard again. I suspect this works because the monitors are also connected to the PC's USB ports. Toggling the power on the monitors causes the sound to be made when new USB devices are connected. The mouse and keyboard do connect direct to the PC though and do not connect via the monitors.

gitea-mirror commented

2026-05-05 07:14:08 -06:00

Author

Owner

@myn commented on GitHub (Nov 16, 2021):

Can confirm this bug still exists. Validated tonight on windows 10 (server) and macOS 12(client) using 2.3.4.

@myn commented on GitHub (Nov 16, 2021): Can confirm this bug still exists. Validated tonight on windows 10 (server) and macOS 12(client) using 2.3.4.