mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #146] screensaver/lock screen cannot be exited on client, mouse works but does nothing #117
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#117
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 @pradavich on GitHub (Oct 8, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/146
Operating Systems
Server: OSX 10.13.6
Client: OSX 10.14
Barrier Version
2.1.0-RELEASE
Steps to reproduce bug
Allow screensaver+lockscreen to activate on both client and server, unlock after 12-48 hours.
server (where the physical HID are attached) unlocks just fine
client remains connected, mouse cursor is visible and can be moved. password prompt never appears.
sshing into the client machine, I discovered that the screensaverengine is called over and over, like so:
Functionality returns 100% when you run
pkill ScreenSaverEngineon the client.Other info
I've only ever run barrier with this setup, so cannot isolate OS or binary versions
Workaround described above. You need to enable remote access to the machine, or a reboot is your only option. Both work.
While this bug is annoying, I finally figured it out and will continue to use barrier. Thanks for the work on it!
@baens commented on GitHub (Aug 13, 2019):
I too have this problem. However, for me to get around it, I hit the "esc" key a few times, hit the lock key on my touch bar, then this returns me to a normal password prompt, which I can then login. Annoying because I have to manually do this every time the screen saver activates.
If anyone would like to point out where I could help out, I'd love to submit a patch!
@NuclearMonster commented on GitHub (Aug 10, 2020):
I have a similar issue, Barrier 2.3.2 here. I enter my password to unlock my mac client successfully, from my windows host, but the screensaver never goes away and escape does nothing. I have to ssh in and randomly kill various ScreenSaverEngine processes until i finally get out of it. No good.
@NuclearMonster commented on GitHub (Apr 25, 2021):
Issue is still present with 2.3.3 and whatever the latest non-beta version of Mac OS Big Sur is.
@markrickert commented on GitHub (May 11, 2021):
Having this same issue on my Mac client with Barrier
2.3.3-release-3395cca9.Server: Mac OS 10.15.6
Client: Mac OS 11.1
@skinlayers commented on GitHub (Sep 29, 2021):
FYI, I've found that (at least on macOS 10.15.7) if I ssh into the client, and run:
pmset displaysleepnowI can then wake and unlock it by attempting to move the cursor to the now-sleeping client's screen.
That might be a more graceful workaround until the issue is resolved.
@qn1213 commented on GitHub (Nov 1, 2021):
I have the same issue.
The temporary solution didn't work and I had to restart device.
2.3.3-release-3395cca9, Big sur, Win 10 19042.1288
@juanmartin commented on GitHub (Jan 18, 2022):
I also experience this. It's not consistent but happens, haven't figured the pattern out yet.
My workaround is (since I'm using a macbook pro) to close the lid enforcing a sleep (you also need to disconnect external displays or it won't sleep). Wait a few seconds and open it again. It's important to wait for a bit or the mac won't go to sleep yet.
At least I don't have to reboot 🤷
@eugeneniemand commented on GitHub (May 9, 2023):
I have the same problem and the use the same solution as @juanmartin mentioned. I cant figure out a pattern and some days it happens a few times and other days not at all
@fernandorych commented on GitHub (May 21, 2023):
This is really very annoying, I have a main PC with Win11 and a Macbook Pro that is owned and managed by my employer, I can't change the time that it takes to show the screensaver (10 minutes), so every 10 minutes I have to reset the mac, making this app completely useless!