Synergy-core: Lock screen issues

Created on 21 Apr 2017  路  5Comments  路  Source: symless/synergy-core

All issues related to lock screen

bug epic stale

Most helpful comment

When the server is locked I have to be very careful not to accidentally move the mouse over to the Windows 7 client otherwise I won't be able to tpye my user/pass to unlock the Windows 10 server. Can be rather frustrating sometimes.

All 5 comments

When the server is locked I have to be very careful not to accidentally move the mouse over to the Windows 7 client otherwise I won't be able to tpye my user/pass to unlock the Windows 10 server. Can be rather frustrating sometimes.

@bupemko
I have a workaround for this until it is fixed:
Just disconnect the server or the client from your network or stop the synergy process on your client.
After a few seconds the mouse pointer will jump back to the screen of your server.

I have a (partially) automated workaround for this. YMMV. My particular situation is that if I mouse to a client screen while the server is locked the mouse pointer gets trapped in the bottom right corner. As @prikril says, restarting the client process will resolve the issue (until next time). Since both of my clients are linux boxes, I wrote a bash script that I can call from the terminal since the keyboard still works. You will need to have a keyboard shortcut for bringing up a terminal window just in case you didn't have one running when the issue started. The script will kill the active processes, then restart the client. Anyway, here's the code:

#!/usr/bin/env bash

###############################################################################
# Resets synergy in the event that a client machine abducts the mouse.
###############################################################################

lhost=$(hostname)
processes=$(ps -eo pid,command | grep synergy | cut -f 2 -d " " | tr "\n" " ")
kill $processes
sleep 4
synergyc --daemon --name $lhost <your server's IP address>:24800

Potential issue with this script: in case grep decides to misbehave and not insert a leading space as it does on my machine, you may need to change the field number fed to cut. You can insert echo $processes above the kill line to make sure that the pipeline is doing what I bloody well told it to. Another thing that might crop up is if your server is on a dynamically allocated IP address. Should your DHCP decide to change the IP of your server, this script will break until you edit it to the new address. Using a static IP on the server will prevent this. EDIT 7/12/17 I tweaked the last line as I had to run this script a few minutes ago and it didn't go as planned. It's now doing what I expected minus a system tray icon. At the moment I don't care enough to finish it; just letting you know.

Sorry, windows guys. This won't help you if you don't have cygwin or some other way to run bash scripts on your machine. I'd be interested to see an equivalent PS script, though!

EDIT: No solution

Win10 lock screen
https://forums.mydigitallife.net/threads/lockscreengone-v1-0.72193/
From build 15063.250 dll patching is no longer necessary to disable that annoying tablet lock screen, since creators update you should be able to disable by this reg value.

;Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization]
"NoLockScreen"=dword:00000001

Ubuntu 17.10 server (default Gnome desktop), macOS 10.13.2 client, both on Synergy 1.8.8. if I leave the cursor on the client, the server never goes to sleep, but when I bring the mouse back to the server, it goes to sleep after a fraction of a second, but there's enough time to type/paste in a command. This has been a problem for a looong time. https://github.com/symless/synergy-core/issues/4229

Was this page helpful?
0 / 5 - 0 ratings

Related issues

xmstspider picture xmstspider  路  4Comments

jenelcohen picture jenelcohen  路  4Comments

ColinCreamer picture ColinCreamer  路  5Comments

LeTink picture LeTink  路  4Comments

130s picture 130s  路  3Comments