iamtheratio Posted January 26, 2022 Share Posted January 26, 2022 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. Quote Link to comment Share on other sites More sharing options...
BullRiver Posted January 28, 2022 Share Posted January 28, 2022 I am also having the same issue, which requires me to drop from a VPN to re-establish communication with my remote PC. Quote Link to comment Share on other sites More sharing options...
iamtheratio Posted January 28, 2022 Author Share Posted January 28, 2022 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. Quote Link to comment Share on other sites More sharing options...
iamtheratio Posted February 2, 2022 Author Share Posted February 2, 2022 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 Quote Link to comment Share on other sites More sharing options...
anthonypants Posted February 18, 2022 Share Posted February 18, 2022 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 Quote Link to comment Share on other sites More sharing options...
jakejakejake Posted February 24, 2022 Share Posted February 24, 2022 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. Quote Link to comment Share on other sites More sharing options...
jakejakejake Posted February 25, 2022 Share Posted February 25, 2022 Just happened again. Quote Link to comment Share on other sites More sharing options...
jakejakejake Posted February 27, 2022 Share Posted February 27, 2022 [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. Quote Link to comment Share on other sites More sharing options...
Captain-Fracas Posted March 9, 2022 Share Posted March 9, 2022 I have the exact same issue with client and server in 1.14.2-stable-c6918b74... I have 2 Windows 10 pc. Quote Link to comment Share on other sites More sharing options...
Captain-Fracas Posted March 9, 2022 Share Posted March 9, 2022 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. Quote Link to comment Share on other sites More sharing options...
jakejakejake Posted March 11, 2022 Share Posted March 11, 2022 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. Quote Link to comment Share on other sites More sharing options...
SquishyBot01 Posted March 21, 2022 Share Posted March 21, 2022 (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, 2022 by SquishyBot01 adding more info Quote Link to comment Share on other sites More sharing options...
Creatable Polymer Posted September 16, 2022 Share Posted September 16, 2022 No solution for this? I'm having this issue between Windows and Ubuntu. Both on 1.14.5 stable. Quote Link to comment Share on other sites More sharing options...
mlabbe Posted September 21, 2022 Share Posted September 21, 2022 Seeing this on Synergy 1.14.5 with an up-to-date windows system on Sept 21st as well. This causes the dvorak keyboard to revert to qwerty when switching into a Mac and back. Mac is also running the same (most recent) version and OS. Warning only shows on Windows. This makes using Synergy unbearable in my experience. Quote Link to comment Share on other sites More sharing options...
Epoxian Posted October 24, 2022 Share Posted October 24, 2022 I have the same issue for 4 month now. Until now I just lived with it and thought it is the VM that is running on the client. But... itäs actuallz sznergz (there the problem is again). Damn, it switches the whole szstem from english to german kezboard lazout! Several times a daz! Today it happened after I used Crtl+C to copy paste something from server to client. Ctrl+C did not work and the keyboard layout/language setting on windows changed. Please don't touch synergy 1. It is/was just perfect, even without a full webbrowser with blinking UI. Please let the JavaScript guys migrate some other software, but not synergy :(. Quote Link to comment Share on other sites More sharing options...
jakejakejake Posted October 24, 2022 Share Posted October 24, 2022 @Epoxian Did you try "disable language Synchronization in the preferences menu"? I have not used synergy for a while now as I migrated to a different system so I am not sure if this would still happen to me. Good luck. Quote Link to comment Share on other sites More sharing options...
alansterger Posted July 7, 2023 Share Posted July 7, 2023 I receive "WARNING: Failed to determine current keyboard layout" message on Synergy server (Windows 10 - using PS/2 keyboard) at startup, before connecting to client. Any fix for this? Quote Link to comment Share on other sites More sharing options...
Epoxian Posted July 8, 2023 Share Posted July 8, 2023 I switched to Barrier, the Open Source continuation of the old Synergy. Quote Link to comment Share on other sites More sharing options...
mlabbe Posted July 8, 2023 Share Posted July 8, 2023 So did I. Quote Link to comment Share on other sites More sharing options...
alansterger Posted July 9, 2023 Share Posted July 9, 2023 Expoxian, mlabbe appreciate the clue. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.