iamtheratio 1 Posted January 26 Share Posted January 26 I have a Desktop PC at home that is the server and my work laptop which is a client. If I'm working on the work laptop and hold down backspace, left arrow key, or basically any key longer than a second Synergy drops the connection. I have to then move my mouse that was teleported to my Desktop PC back over to my work screen, click, and resume typing. This is incredibly annoying and I'm not sure if the new 1.14.2 application started the issue or upgrading to Windows 11. Synergy logs: [2022-01-26T08:19:04] WARNING: Failed to determine current keyboard layout [2022-01-26T08:19:04] WARNING: Failed to determine current keyboard layout [2022-01-26T08:19:05] NOTE: client "WORK-LAPTOP" has disconnected Any help would be greatly appreciated. Link to post Share on other sites
BullRiver 0 Posted January 28 Share Posted January 28 I am also having the same issue, which requires me to drop from a VPN to re-establish communication with my remote PC. Link to post Share on other sites
iamtheratio 1 Posted January 28 Author Share Posted January 28 3 hours ago, BullRiver said: I am also having the same issue, which requires me to drop from a VPN to re-establish communication with my remote PC. Oof, that's even worse. I tried to download the previous version of Synergy 1 but the downloads page only shows Synergy 2 in the "Version" drop down at the bottom of the page. Sigh... maybe google will provide this for me. Link to post Share on other sites
iamtheratio 1 Posted February 2 Author Share Posted February 2 I opened up a service ticket and this was resolved for me.Resolution: Make sure ALL versions of Synergy on each client/server are upgraded to 1.14.2 and it will resolve this issue. 1 Link to post Share on other sites
anthonypants 1 Posted February 18 Share Posted February 18 Using 1.14.2, just typing normally on a macOS client will produce the "Failed to determine current keyboard layout" error on a Windows 10 server. 1 Link to post Share on other sites
jakejakejake 0 Posted February 24 Share Posted February 24 I have this same issue. Windows 10 as the Server and Ubuntu 20.04 as the client. It works for a little bit, then I get this error. Then I have to restart the Service under windows task manager to reconnect. Both versions are 1.14.2-stable-c6918b74. Link to post Share on other sites
jakejakejake 0 Posted February 25 Share Posted February 25 Just happened again. Link to post Share on other sites
jakejakejake 0 Posted February 27 Share Posted February 27 [2022-02-27T11:22:06] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:18] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:20] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:24] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:25] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:25] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:25] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:26] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:26] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:27] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:27] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:40] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:40] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:40] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:41] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:42] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:42] WARNING: Failed to determine current keyboard layout [2022-02-27T11:23:43] WARNING: Failed to determine current keyboard layout Same thing. Happened again. Link to post Share on other sites
Captain-Fracas 0 Posted March 9 Share Posted March 9 I have the exact same issue with client and server in 1.14.2-stable-c6918b74... I have 2 Windows 10 pc. Link to post Share on other sites
Captain-Fracas 0 Posted March 9 Share Posted March 9 With the old free version of Synergy, I didn't have this issue. This is a shame that the the payed version is less functioning that the free old one. Link to post Share on other sites
jakejakejake 0 Posted March 11 Share Posted March 11 I have an email thread opened with Symless support. This is from the email and maybe worth a try. I still have the issue but this is the only thing they have asked me to try so far:What happens when you disable language Synchronization in the preferences menu. To do this go to preferences and uncheck The check box that is labeled "Use servers keyboard language on this machine". If it is already unchecked then re-check it, click save then go back and uncheck it, and then save again. Link to post Share on other sites
SquishyBot01 0 Posted March 21 Share Posted March 21 (edited) From Server: Edit > Preferences > Advanced (bottom) > Set 'Elevate Privileges' to Always (default is prompt) > Save This cleared up the log "Failed to determine current keyboard layout" Doing this does not prompt UAC on the server or client. Nor does it interfere when you run a UAC (admin rights) for an app on a client machine - eventually the server will reconnect to the client allowing to interact with the admin prompt. Edited March 21 by SquishyBot01 adding more info Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now