mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #537] Barrier Stops working on Macbook High Sierra - 10.13.6 after machines goes to sleep or restart #420
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#420
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kumar-j on GitHub (Jan 3, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/537
Operating Systems
Server: macOS 10.13.6 High Sierra
Client: Windows 10 - Version 1809
Barrier Versions
Server is 2.3.2 - Release-210c2b70
Client - 2.3.2
Steps to reproduce the bug
The bug happens when the server machine goes to sleep or re-started. The same happens when I start both machines every morning.
Also, even if the mouse pointer gets connected to the MacBook server, the mouse pointer becomes jittery. Clicking on the MacBook touchpad does not make any difference.
What Solves the bug (temporarily) -
I have to delete the server machine on the client barrier software. Then I have to quit the MacBook barrier. After that, I have to restart the barrier on the MacBook. It then sends the availability popup on the client machine (windows) and after I add it as a server, it starts working again.
But, sometimes, this solution does not work at all. I have to repeat it several times to work.
@Hack5190 commented on GitHub (Jan 6, 2020):
Note: Sleep related issues exist when both the server and client are running macOS.
Current setup (for both server & client) is Barrier v2.3.2-Release-210c2b70 running on macOS Mojave v10.14.6 (18G2022).
@socketbox commented on GitHub (Jan 8, 2020):
I'll grant that this is inconvenient, but what exactly is expected/desired behavior here? Override the power management settings that the user themselves have configured?
I'm running a client on macOS 10.13.6 and a server on Linux Mint 19.3 (both v2.3.2-210c2b70). Here is an excerpt from the log on the client (at DEBUG level) showing that Barrier is aware of power management events:
@Hack5190 commented on GitHub (Jan 14, 2020):
@socketbox, The expected/desired behavior is that when both machines wake they reconnect without any user intervention.
More times than not - reconnecting requires the user to apply random work around's that work inconsistently. Examples of previous work around's I have had to use include:
restarting barrier (on one or both) machines
removing the server or client from barrier
disabling SSL on server
nuke all configuration files (both server & client)
@kumar-j commented on GitHub (Jan 21, 2020):
Exactly, I have to perform different work around's listed above and one of them works randomly. This is very annoying.
@KapitanOczywisty commented on GitHub (Mar 3, 2020):
I have also this issue: barrier no longer works after hibernation/sleep. In my case win 7 - win 10, but restarting server seems to fix issue.
@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
@kumar-j commented on GitHub (Oct 1, 2020):
I am still facing this issue whenever my mac goes to sleep or hibernate mode. I have to do some random solutions such as reloading the barrier on windows, reloading on mac. And, if nothing works, then restarting both barrier softwares and lastly I have to delete the mac client and have to add it all over again.
@shaunchurch commented on GitHub (Oct 11, 2020):
I am also seeing similar issues, on macOS 10.15.6. After sleep/hibernate, the mouse will move over to the client machine, but the keyboard remains active only on the server.
The only thing that consistently fixes it is a reboot of both machines.
Any combination of: stopping the server, stopping the client (including closing Barrier on both machines), deleting the client and readding the client results in the same behaviour: Mouse moves over to the second machine. Keyboard does not.
@gaztec22 commented on GitHub (Mar 31, 2021):
I'm also experiencing this issue. I have a macos client and a windows server. Whenever the macos wakes from sleep barrier doesn't work. Furthermore I can restart or quit the app at all as its unresponsive.. The only action that works is to restart the macbook.. After restart it connects again to the windows server just fine..
It's actually quite disruptive to have to restart the macbook each time it wakes from sleep. It actually makes it fairly pointless for it to go to sleep at all...