Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problems controlling client after sleeping/resuming server, seems to be scrolllock issue #102

Open
ghost opened this issue Nov 4, 2021 · 0 comments
Labels
barrier-import Imported from Barrier - likely outdated. bug Something isn't working platform/windows This issue is affecting at least one system running Windows

Comments

@ghost
Copy link

ghost commented Nov 4, 2021

This issue has been migrated from old Barrier Github repository debauchee/barrier#102

Issue created on: 2018-07-23 by @snuq
Issue last updated on: 2021-01-25

Operating Systems

Server: Windows 8.1

Client: Windows 8.1

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

  1. connect server and client
  2. sleep server computer
  3. wake server computer

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.


Commented on: 2021-01-25 by @Zackhardtoname

still having this problem...

@ghost ghost added bug Something isn't working platform/windows This issue is affecting at least one system running Windows labels Nov 10, 2021
@shymega shymega added the barrier-import Imported from Barrier - likely outdated. label Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
barrier-import Imported from Barrier - likely outdated. bug Something isn't working platform/windows This issue is affecting at least one system running Windows
Projects
None yet
Development

No branches or pull requests

1 participant