FireFrenzy Posted August 1, 2017 Share Posted August 1, 2017 So is it just me or does the new version 3 beta not actually connect keyboards and mice? After some fiddling and a reboot or two i have gotten the shiny green connected state but my mouse cannot be dragged to my laptop, something that DID work for me in beta-2... Link to comment Share on other sites More sharing options...
FireFrenzy Posted August 1, 2017 Author Share Posted August 1, 2017 [ UI ] [2017-08-01T17:46:30] WARNNIG: no font file: Raleway.otf [ UI ] [2017-08-01T17:46:30] INFO: log filename: C:/Users/FireFrenzy/AppData/Local/Symless/Synergy/synergy.log [ UI ] [2017-08-01T17:46:35] DEBUG: new added screen pos: 257 161 [ UI ] [2017-08-01T17:46:36] DEBUG: current version is update to date [ UI ] [2017-08-01T17:46:36] INFO: write configuration file complete [ UI ] [2017-08-01T17:46:37] DEBUG: Profile ID: 735 name: default [Core] [2017-08-01T17:46:37] INFO: drag and drop enabled [Core] [2017-08-01T17:46:37] DEBUG: opening configuration "C:/Users/FireFrenzy/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-01T17:46:37] DEBUG: configuration read successfully [Core] [2017-08-01T17:46:37] DEBUG: screen shape: -1920,0 5760x1080 (multi-monitor) [Core] [2017-08-01T17:46:37] DEBUG: window is 0x002a0da6 [Core] [2017-08-01T17:46:37] DEBUG: using desktop for drop target: C:\Users\FireFrenzy\Desktop [Core] [2017-08-01T17:46:37] DEBUG: adopting new buffer [Core] [2017-08-01T17:46:37] DEBUG: opened display [Core] [2017-08-01T17:46:37] DEBUG: active sides: 10 [Core] [2017-08-01T17:46:37] DEBUG: active sides: 10 [Core] [2017-08-01T17:46:37] DEBUG: clipboard changed: synergy owned [Core] [2017-08-01T17:46:37] DEBUG: desk Default window is 0x00481612 [Core] [2017-08-01T17:46:37] DEBUG: switched to desk "Default" [Core] [2017-08-01T17:46:37] DEBUG: desktop is now accessible [Core] [2017-08-01T17:46:37] NOTE: Scroll Lock is on, locking cursor to screen [Core] [2017-08-01T17:46:37] NOTE: started server, waiting for clients [Core] [2017-08-01T17:46:37] DEBUG: event queue is ready [Core] [2017-08-01T17:46:37] DEBUG: add pending events to buffer [Core] [2017-08-01T17:46:37] DEBUG: screen "Yggdrasil" shape changed [ UI ] [2017-08-01T17:46:37] ERROR: [2017-08-01T17:46:37] WARNING: failed to register hotkey ScrollLock (id=ef14 mask=0000) [ UI ] [2017-08-01T17:46:39] DEBUG: connectivity test pass: 192.168.2.5 [ UI ] [2017-08-01T17:46:39] DEBUG: report to cloud: destId 1609 successfulIp 192.168.2.5 failedIp Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 Could you send your client log? Link to comment Share on other sites More sharing options...
FireFrenzy Posted August 4, 2017 Author Share Posted August 4, 2017 [ UI ] [2017-08-04T17:47:58] WARNNIG: no font file: Raleway.otf [ UI ] [2017-08-04T17:47:58] INFO: log filename: C:/Users/FireFrenzy/AppData/Local/Symless/Synergy/synergy.log [ UI ] [2017-08-04T17:48:03] DEBUG: new added screen pos: 257 161 [ UI ] [2017-08-04T17:48:05] DEBUG: Profile ID: 735 name: default [ UI ] [2017-08-04T17:48:05] DEBUG: current version is update to date [ UI ] [2017-08-04T17:48:07] INFO: write configuration file complete [Core] [2017-08-04T17:48:07] INFO: drag and drop enabled [Core] [2017-08-04T17:48:07] DEBUG: opening configuration "C:/Users/FireFrenzy/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-04T17:48:07] DEBUG: configuration read successfully [Core] [2017-08-04T17:48:07] DEBUG: screen shape: -1920,0 5760x1080 (multi-monitor) [Core] [2017-08-04T17:48:07] DEBUG: window is 0x00080afc [Core] [2017-08-04T17:48:07] DEBUG: using desktop for drop target: C:\Users\FireFrenzy\Desktop [Core] [2017-08-04T17:48:07] DEBUG: adopting new buffer [Core] [2017-08-04T17:48:07] DEBUG: opened display [Core] [2017-08-04T17:48:07] DEBUG: active sides: 10 [Core] [2017-08-04T17:48:07] DEBUG: active sides: 10 [Core] [2017-08-04T17:48:07] DEBUG: desk Default window is 0x00230abe [Core] [2017-08-04T17:48:07] DEBUG: switched to desk "Default" [Core] [2017-08-04T17:48:07] DEBUG: desktop is now accessible [Core] [2017-08-04T17:48:07] NOTE: started server, waiting for clients [Core] [2017-08-04T17:48:07] DEBUG: event queue is ready [Core] [2017-08-04T17:48:07] DEBUG: add pending events to buffer [Core] [2017-08-04T17:48:07] DEBUG: screen "Yggdrasil" shape changed [ UI ] [2017-08-04T17:48:07] ERROR: [2017-08-04T17:48:07] WARNING: failed to register hotkey ScrollLock (id=ef14 mask=0000) [ UI ] [2017-08-04T17:48:57] INFO: Sending log file... [ UI ] [2017-08-04T17:48:59] INFO: Upload path: https://synergy-logs.symless.com/2017-08-04/736-2017-08-04T17-48-57.log Link to comment Share on other sites More sharing options...
FireFrenzy Posted August 4, 2017 Author Share Posted August 4, 2017 [ UI ] [2017-08-04T17:49:20] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:23] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:23] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:26] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:26] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:29] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:29] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:32] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:32] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:35] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:35] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:38] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:38] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:41] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:41] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:44] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:44] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:47] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:47] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:50] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:50] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:53] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:53] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:56] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:56] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:49:59] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:49:59] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:02] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:02] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:06] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:06] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:09] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:09] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:12] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:12] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:15] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:15] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:18] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:18] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:21] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:21] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:24] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:24] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:27] ERROR: Reply status code: 504 [ UI ] [2017-08-04T17:50:27] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:27] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:29] ERROR: Reply status code: 504 [ UI ] [2017-08-04T17:50:30] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:30] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:33] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:33] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:36] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:36] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:39] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:39] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:42] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:42] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:45] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:45] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:48] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:48] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:51] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:51] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:54] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:54] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:50:57] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:50:57] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:00] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:00] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:03] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:03] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:06] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:06] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:09] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:09] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:12] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:12] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:15] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:16] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:19] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:19] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:22] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:22] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:25] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:25] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:28] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:28] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:31] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:31] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:31] INFO: Sending log file... [ UI ] [2017-08-04T17:51:34] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:34] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:34] INFO: Upload path: https://synergy-logs.symless.com/2017-08-04/736-2017-08-04T17-51-32.log [ UI ] [2017-08-04T17:51:37] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:37] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:40] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:40] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:43] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:43] DEBUG: retry in 3 seconds [ UI ] [2017-08-04T17:51:46] DEBUG: can not find any successful connectivity result for the server screen: 1606 [ UI ] [2017-08-04T17:51:46] DEBUG: retry in 3 seconds Link to comment Share on other sites More sharing options...
FireFrenzy Posted August 4, 2017 Author Share Posted August 4, 2017 The second log is from my laptop (client side) Oh now that i have someone's attention who's smart in the ways of this awesome program, Is it possible to somehow make it so that synergy knows how many monitors any PC has? So you could have a bit more granular control, Awesome if yes, definitely no major problems if not... Also is the ability to add "lock to screen" hotkeys on the roadmap? And if yes, could we make it so you can go "move my mouse to PC1 and then lock" I tried to get that to work in Version 1 and never got it to work on a single hotkey there, even with "push: move mouse. Release: lock to screen" Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 Quote [ UI ] [2017-08-04T17:51:19] DEBUG: retry in 3 seconds Could you try restarting Synergy on both computers? We're having some scalability issues with our servers right now that could be causing issues. Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 18 minutes ago, FireFrenzy said: The second log is from my laptop (client side) Oh now that i have someone's attention who's smart in the ways of this awesome program, Is it possible to somehow make it so that synergy knows how many monitors any PC has? So you could have a bit more granular control, Awesome if yes, definitely no major problems if not... Also is the ability to add "lock to screen" hotkeys on the roadmap? And if yes, could we make it so you can go "move my mouse to PC1 and then lock" I tried to get that to work in Version 1 and never got it to work on a single hotkey there, even with "push: move mouse. Release: lock to screen" Both are on the roadmap Link to comment Share on other sites More sharing options...
FireFrenzy Posted August 4, 2017 Author Share Posted August 4, 2017 Already uninstalled it on both PCs and reinstalled Syn 1... That said i have tried it the last time, and then it didnt change after ~30 reboots of both the soft and hardware.... EDIT: to bad i cant keep both the programs installed at the same time, but it seems you cannot Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 I think maybe it'll be best to wait for beta4 (due in about 3 weeks). Really sorry about the delay! Link to comment Share on other sites More sharing options...
FireFrenzy Posted August 4, 2017 Author Share Posted August 4, 2017 No worries, i bought the beta knowing shit like this could (and in all probability WOULD) happen... Link to comment Share on other sites More sharing options...
Nenad Posted August 4, 2017 Share Posted August 4, 2017 At least what you could do is to just cram a bunch of options in the config file, then at least we can debug when things go sour. Link to comment Share on other sites More sharing options...
FireFrenzy Posted August 4, 2017 Author Share Posted August 4, 2017 For what its worth v2 worked for me... Barring the hotkey thing... Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 26 minutes ago, Nenad said: At least what you could do is to just cram a bunch of options in the config file, then at least we can debug when things go sour. That would defeat the purpose of Synergy 2. Link to comment Share on other sites More sharing options...
Nenad Posted August 4, 2017 Share Posted August 4, 2017 OK, I get it... it's supposed to be seamless. Still, if I want to disable Synergy from listening on a different Ethernet interface, perhaps I should be able to do that, even via the config file. Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 We won't be implementing a config file. We will, however, add a settings screen to the final stable release in November. Link to comment Share on other sites More sharing options...
Nenad Posted August 4, 2017 Share Posted August 4, 2017 Sorry for being nosey, but where will the settings be stored? In a binary file, the registry, the cloud, or..? Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 Settings will be stored both on your machine and in the cloud (encrypted) so you can edit settings from any machine. Link to comment Share on other sites More sharing options...
Nenad Posted August 4, 2017 Share Posted August 4, 2017 That sounds very reasonable, kudos. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.