VVE1505 Posted September 22, 2017 Share Posted September 22, 2017 Just installed 2. beta - server is a Linux (Ubuntu) system and client is a Windows 10 box. After installing on each system and following the Linux directions from the early access beta forum post, I started Synergy on each system. I did initially see the client connect to the server and both were green, but completely unresponsive; there was no interaction. I tried to copy the log from each, but it was looping - appeared that some connection state was trying to accomplish, and I couldn't copy it fast enough before a new entry would clear my highlight. Rebooted my Linux box and now there is no configuration / evidence of the two seeing each other. Output of log from server: [ Config ] [2017-09-22T07:32:37] INFO: log filename: /home/vve1505/.config/Symless/Synergy/synergy.log [ Config ] [2017-09-22T07:32:37] DEBUG: connecting to service [ Config ] [2017-09-22T07:32:38] DEBUG: new added screen pos: 257 161 [ Config ] [2017-09-22T07:32:38] DEBUG: Profile ID: 1677 name: default [ Config ] [2017-09-22T07:32:38] DEBUG: current version is update to date [ Config ] [2017-09-22T07:32:38] DEBUG: requesting profile snapshot [ Config ] [2017-09-22T07:33:13] DEBUG: forcing current computer to be server [ Config ] [2017-09-22T07:33:19] DEBUG: forcing current computer to be server [ Config ] [2017-09-22T07:35:18] ERROR: Reply status code: 400 [ Config ] [2017-09-22T07:35:18] ERROR: Reply error message: Invalid JSON request: bad numeric conversion: negative overflow [ Config ] [2017-09-22T07:35:21] ERROR: Reply status code: 400 [ Config ] [2017-09-22T07:35:21] ERROR: Reply error message: Invalid JSON request: bad numeric conversion: negative overflow [ Config ] [2017-09-22T07:36:19] INFO: Sending log file... [ Config ] [2017-09-22T07:36:21] INFO: Upload path: https://synergy-logs.symless.com/2017-09-22/1683-2017-09-22T07-36-19.log The error 400 happened when I repositioned the icon of the server. Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted September 23, 2017 Synergy Team Share Posted September 23, 2017 These issues will be fixed in beta5, which is due in about 4-5 weeks. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.