github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 22:01:23 -06:00

[GH-ISSUE #941] Resume on Windows with Sign-in off #751

New issue

Open

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

gitea-mirror commented

2026-05-05 07:02:00 -06:00

Owner

Originally created by @igordovgaluk on GitHub (Nov 10, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/941

After Windows 10 resume with Sign-in option is turned off, the mouse cannot be moved to the client's screen.
Requires server restart to workaround the problem.

Steps to reproduce the behavior:

Go to Windows Sign-in options
Select Never for Require sign-in
Suspend computer
Resume and wait some time so the client is connected to the server.
Move the mouse cursor to leave the server screen

After restart of barrier on the server the problem is resolved - can move the mouse to the client's screen.

Expected behavior
The mouse cursor should be able to leave the server screen and move to the client's screen

Screenshots

Additional details

Windows 10 (server), Ubuntu 18.04 (client)
Barrier version 2.3.3

In both logs I can see the client is connected.

Originally created by @igordovgaluk on GitHub (Nov 10, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/941 After Windows 10 resume with Sign-in option is turned off, the mouse cannot be moved to the client's screen. Requires server restart to workaround the problem. **Steps to reproduce the behavior:** 1. Go to Windows Sign-in options 2. Select Never for Require sign-in 3. Suspend computer 4. Resume and wait some time so the client is connected to the server. 5. Move the mouse cursor to leave the server screen After restart of barrier on the server the problem is resolved - can move the mouse to the client's screen. **Expected behavior** The mouse cursor should be able to leave the server screen and move to the client's screen **Screenshots** ![image](https://user-images.githubusercontent.com/4215041/98681433-63563900-236b-11eb-9ee4-7ac8f3d2bbc5.png) **Additional details** - Windows 10 (server), Ubuntu 18.04 (client) - Barrier version 2.3.3 In both logs I can see the client is connected.

gitea-mirror commented

2026-05-05 07:02:04 -06:00

Author

Owner

@gbronner commented on GitHub (Nov 25, 2020):

I've seen this regularly -- when I go away from my computer for a few hours, the last item in the server log is 'Suspend' It never resumes. When I hit the stop / start button on the server, I get the following:

Looks like maybe it needs to register for some event?

[2020-11-25T05:33:00] INFO: service command updated
[2020-11-25T05:33:01] INFO: process started but command is empty, shutting down
[2020-11-25T08:33:01] INFO: resume

@gbronner commented on GitHub (Nov 25, 2020): I've seen this regularly -- when I go away from my computer for a few hours, the last item in the server log is 'Suspend' It never resumes. When I hit the stop / start button on the server, I get the following: Looks like maybe it needs to register for some event? [2020-11-25T05:33:00] INFO: service command updated [2020-11-25T05:33:01] INFO: process started but command is empty, shutting down [2020-11-25T08:33:01] INFO: resume

gitea-mirror commented

2026-05-05 07:02:05 -06:00

Author

Owner

@dev-101 commented on GitHub (Feb 13, 2021):

Hi, I have also reported similar #997 issue. This is why I decided to revert back to original Synergy 1.88 which does not seem to suffer from this bug.

@dev-101 commented on GitHub (Feb 13, 2021): Hi, I have also reported similar #997 issue. This is why I decided to revert back to original Synergy 1.88 which does not seem to suffer from this bug.

No labels

Rows
Columns