mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #102] problems controlling client after sleeping/resuming server, seems to be scrolllock issue #76
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#76
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 @snuq on GitHub (Jul 23, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/102
Operating Systems
Server: Windows 8.1
Client: Windows 8.1
Barrier Version
2.1.0-RELEASE-0b2dfd80
Steps to reproduce bug
Other info
I start up and connect barrier between the two computers and it works great, but when the server computer (my laptop) sleeps then wakes up, I no longer an able to control the client.
the log on the server displays: """
[
2018-07-23T1
3
:45:4
2]
W
ARNING: f
a
il
e
d to register
hotke
y
S
croll
Lock (
id=ef14
mask=0000)
"""
...yeah, its split up exactly like that...
Both computers say they are connected, but I cannot move the mouse off screen. Enabling and disabling scroll lock does not have any effect.
stopping and starting the server does not fix it, i have to go into the configure server settings, click ok, then click apply, THEN i can use the mouse connection again.
@Zackhardtoname commented on GitHub (Jan 25, 2021):
still having this problem...
@mirh commented on GitHub (Feb 25, 2022):
I can confirm this did the trick for me, after a hour of attempts.
For some reason
Scroll Lock is on, locking cursor to screenjust didn't seem to want to go away.https://github.com/debauchee/barrier/blob/v2.4.0/src/lib/platform/MSWindowsKeyState.cpp#L833
https://github.com/debauchee/barrier/blob/v2.4.0/src/lib/platform/MSWindowsScreen.cpp#L1140
I feel like those functions are some disaster waiting to happen
https://stackoverflow.com/questions/66510965/windows-c-getkeystate-caps-lock-detector-does-opposite
https://stackoverflow.com/questions/45719020/winapi-getkeyboardstate-behavior-modified-by-getkeystate-when-application-is-out