rabec

Crash while installing Synergy after Win10 Reset

8 posts in this topic

Hi there,
 
there used to be [email protected], nowadays "the email account that you tried to reach does not exist". Why?
Anyway, if there is someone here who can help me, please do!

Windows 10 informed me that my laptop (i.e. client "TabletNotebook") had slowed down so much that it needed to reset and reinstall Windows 10.

Since then I cannot install my 'Synergy 1.8.8 stable' for this client properly:
When I click 'Auto config' it fails to install Bonjour, displaying the message "Keine Rückmeldung" (German for something like "No feedback" or possibly "No connection"). At this point Synergy freezes and can only be stopped by Windows.

The client ("TabletNotebook") does not allow the mouse pointer into its screen, but whenever Synergy is running on it, the other clients ("i7" and "Home-PC") disrupt mouse movements as soon as I move the mouse pointer into their screens (until I stop Synergy on the "TabletNotebook").
Only the server ("i5") works properly as long as I keep the mouse pointer within its display.

This is the log copied from the client "TabletNotebook" with the failed Bonjour installation:

[2017-07-30T09:47:23] INFO: using last known command: "C:/Program Files/Synergy/synergyc.exe" -f --no-tray --debug INFO --name TabletNotebook --ipc --stop-on-desk-switch --enable-drag-drop --profile-dir "C:\Users\Ralf\AppData\Local" i5:24800
[2017-07-30T09:47:23] INFO: service command updated
[2017-07-30T09:47:23] INFO: starting new process
[2017-07-30T09:47:24] INFO: activeDesktop:Winlogon
[2017-07-30T09:47:24] INFO: starting new process
[2017-07-30T09:47:24] INFO: drag and drop enabled
[2017-07-30T09:47:25] ERROR: failed to get desktop path, no drop target available, error=2
[2017-07-30T09:47:25] NOTE: started client
[2017-07-30T09:47:25] INFO: watchdog status: ok
[2017-07-30T09:47:25] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:47:40] WARNING: failed to connect to server: Timed out
[2017-07-30T09:47:41] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:47:56] WARNING: failed to connect to server: Timed out
[2017-07-30T09:47:57] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:48:12] WARNING: failed to connect to server: Timed out
[2017-07-30T09:48:13] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:48:28] WARNING: failed to connect to server: Timed out
[2017-07-30T09:48:29] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:48:44] WARNING: failed to connect to server: Timed out
[2017-07-30T09:48:45] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:49:00] WARNING: failed to connect to server: Timed out
[2017-07-30T09:49:01] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:49:16] WARNING: failed to connect to server: Timed out
[2017-07-30T09:49:17] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:49:32] WARNING: failed to connect to server: Timed out
[2017-07-30T09:49:33] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:49:48] WARNING: failed to connect to server: Timed out
[2017-07-30T09:49:49] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:50:04] WARNING: failed to connect to server: Timed out
[2017-07-30T09:50:05] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:50:20] WARNING: failed to connect to server: Timed out
[2017-07-30T09:50:21] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:50:36] WARNING: failed to connect to server: Timed out
[2017-07-30T09:50:37] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:50:52] WARNING: failed to connect to server: Timed out
[2017-07-30T09:50:53] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:51:08] WARNING: failed to connect to server: Timed out
[2017-07-30T09:51:09] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:51:24] WARNING: failed to connect to server: Timed out
[2017-07-30T09:51:25] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:51:30] INFO: watchdog status: ok
[2017-07-30T09:51:40] WARNING: failed to connect to server: Timed out
[2017-07-30T09:51:41] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:51:56] WARNING: failed to connect to server: Timed out
[2017-07-30T09:51:57] NOTE: connecting to 'i5': 192.168.178.22:24800
[2017-07-30T09:52:12] WARNING: failed to connect to server: Timed out
[2017-07-30T09:52:13] NOTE: connecting to 'i5': 192.168.178.22:24800


This is the log copied from the server ("i5"):

[2017-07-30T08:30:10] NOTE: client "Home-PC" has disconnected

[2017-07-30T08:30:21] NOTE: accepted client connection

[2017-07-30T08:30:21] NOTE: client "Home-PC" has connected

[2017-07-30T08:30:32] NOTE: client "i7" has disconnected

[2017-07-30T08:30:37] NOTE: accepted client connection

[2017-07-30T08:30:37] NOTE: client "i7" has connected

[2017-07-30T08:33:12] NOTE: client "Home-PC" has disconnected

[2017-07-30T08:33:18] NOTE: accepted client connection

[2017-07-30T08:33:18] NOTE: client "Home-PC" has connected

[2017-07-30T08:33:42] WARNING: error writing to client "Home-PC"

[2017-07-30T08:33:43] NOTE: accepted client connection

[2017-07-30T08:33:43] NOTE: client "Home-PC" has connected

[2017-07-30T08:35:12] NOTE: client "i7" has disconnected

[2017-07-30T08:35:24] NOTE: accepted client connection

[2017-07-30T08:35:24] NOTE: client "i7" has connected

[2017-07-30T09:45:11] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:45:11] ERROR: eof violates ssl protocol

[2017-07-30T09:45:11] ERROR: failed to accept secure socket

[2017-07-30T09:45:27] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:45:27] ERROR: eof violates ssl protocol

[2017-07-30T09:45:27] ERROR: failed to accept secure socket

[2017-07-30T09:45:43] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:45:43] ERROR: eof violates ssl protocol

[2017-07-30T09:45:43] ERROR: failed to accept secure socket

[2017-07-30T09:45:59] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:45:59] ERROR: eof violates ssl protocol

[2017-07-30T09:45:59] ERROR: failed to accept secure socket

[2017-07-30T09:46:15] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:46:15] ERROR: eof violates ssl protocol

[2017-07-30T09:46:15] ERROR: failed to accept secure socket

[2017-07-30T09:46:31] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:46:31] ERROR: eof violates ssl protocol

[2017-07-30T09:46:31] ERROR: failed to accept secure socket

[2017-07-30T09:46:36] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:46:36] ERROR: failed to accept secure socket

[2017-07-30T09:47:31] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:47:31] ERROR: eof violates ssl protocol

[2017-07-30T09:47:31] ERROR: failed to accept secure socket

[2017-07-30T09:47:47] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:47:47] ERROR: eof violates ssl protocol

[2017-07-30T09:47:47] ERROR: failed to accept secure socket

[2017-07-30T09:48:03] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:48:03] ERROR: eof violates ssl protocol

[2017-07-30T09:48:03] ERROR: failed to accept secure socket

[2017-07-30T09:48:19] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:48:19] ERROR: eof violates ssl protocol

[2017-07-30T09:48:19] ERROR: failed to accept secure socket

[2017-07-30T09:48:35] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:48:35] ERROR: eof violates ssl protocol

[2017-07-30T09:48:35] ERROR: failed to accept secure socket

[2017-07-30T09:48:51] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:48:51] ERROR: eof violates ssl protocol

[2017-07-30T09:48:51] ERROR: failed to accept secure socket

[2017-07-30T09:49:07] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:49:07] ERROR: eof violates ssl protocol

[2017-07-30T09:49:07] ERROR: failed to accept secure socket

[2017-07-30T09:49:23] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:49:23] ERROR: eof violates ssl protocol

[2017-07-30T09:49:23] ERROR: failed to accept secure socket

[2017-07-30T09:49:39] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:49:39] ERROR: eof violates ssl protocol

[2017-07-30T09:49:39] ERROR: failed to accept secure socket

[2017-07-30T09:49:55] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:49:55] ERROR: eof violates ssl protocol

[2017-07-30T09:49:55] ERROR: failed to accept secure socket

[2017-07-30T09:50:11] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:50:11] ERROR: eof violates ssl protocol

[2017-07-30T09:50:11] ERROR: failed to accept secure socket

[2017-07-30T09:50:27] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:50:27] ERROR: eof violates ssl protocol

[2017-07-30T09:50:27] ERROR: failed to accept secure socket

[2017-07-30T09:50:43] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:50:43] ERROR: eof violates ssl protocol

[2017-07-30T09:50:43] ERROR: failed to accept secure socket

[2017-07-30T09:50:59] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:50:59] ERROR: eof violates ssl protocol

[2017-07-30T09:50:59] ERROR: failed to accept secure socket

[2017-07-30T09:51:15] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:51:15] ERROR: eof violates ssl protocol

[2017-07-30T09:51:15] ERROR: failed to accept secure socket

[2017-07-30T09:51:31] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:51:31] ERROR: eof violates ssl protocol

[2017-07-30T09:51:31] ERROR: failed to accept secure socket

[2017-07-30T09:51:47] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:51:47] ERROR: eof violates ssl protocol

[2017-07-30T09:51:47] ERROR: failed to accept secure socket

[2017-07-30T09:52:03] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:52:03] ERROR: eof violates ssl protocol

[2017-07-30T09:52:03] ERROR: failed to accept secure socket

[2017-07-30T09:52:19] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:52:19] ERROR: eof violates ssl protocol

[2017-07-30T09:52:19] ERROR: failed to accept secure socket

[2017-07-30T09:52:35] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:52:35] ERROR: eof violates ssl protocol

[2017-07-30T09:52:35] ERROR: failed to accept secure socket

[2017-07-30T09:52:51] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:52:51] ERROR: eof violates ssl protocol

[2017-07-30T09:52:51] ERROR: failed to accept secure socket

[2017-07-30T09:53:07] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:53:07] ERROR: eof violates ssl protocol

[2017-07-30T09:53:07] ERROR: failed to accept secure socket

[2017-07-30T09:53:23] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:53:23] ERROR: eof violates ssl protocol

[2017-07-30T09:53:23] ERROR: failed to accept secure socket

[2017-07-30T09:53:39] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:53:39] ERROR: eof violates ssl protocol

[2017-07-30T09:53:39] ERROR: failed to accept secure socket

[2017-07-30T09:53:45] ERROR: ssl error occurred (system call failure)

[2017-07-30T09:53:45] ERROR: eof violates ssl protocol

[2017-07-30T09:53:45] ERROR: failed to accept secure socket


I would be very grateful if you could help me solve this problem soon.

Bye for now

rabec
Edited by rabec

Share this post


Link to post
Share on other sites

Hi again,

no changes here: Synergy keeps crashing whenever I try the same procedure that worked for the other clients.

As apparently nobody here seems to have an idea of how I could try to solve the problem, can anybody tell me how to get official support for paying customers?
Perhaps I am missing something obvious, but even after customer login I cannot find anything of the kind.
The help page only refers to this user forum, but does not mention how to get official support.

Having seen that one official Synergy Team Support Engineer (Paul Suarez) does help sometimes in this community forum, I wonder if this is supposed to be the official support. If so, then please, Mr Suarez, look into my problem - the software I bought has been causing me trouble for more than a week now.

Bye for now

rabec

Share this post


Link to post
Share on other sites

Hi @rabec. Sorry for the late reply on this. Please try version v1.9.0rc3 from the tagged thread below.

 

Share this post


Link to post
Share on other sites

Thank you for the thread.

There is a little progress: Synergy v1.9.0rc3 has succeeded in installing Bonjour.

Nevertheless, this is still true:

On 30.7.2017 at 4:23 PM, rabec said:

The client ("TabletNotebook") does not allow the mouse pointer into its screen, but whenever Synergy is running on it, the other clients ("i7" and "Home-PC") disrupt mouse movements as soon as I move the mouse pointer into their screens (until I stop Synergy on the "TabletNotebook").
Only the server ("i5") works properly as long as I keep the mouse pointer within its display.

As soon as I stop Synergy on the client "TabletNotebook", all other clients work properly again.

This is the log copied from the client "TabletNotebook":
[2017-08-09T15:27:00] INFO: connecting to service...
[2017-08-09T15:27:02] INFO: zeroconf server detected: 192.168.178.22
[2017-08-09T15:27:02] INFO: starting client
[2017-08-09T15:27:02] INFO: config file: C:/Users/Ralf/AppData/Local/Temp/Synergy.em6396
[2017-08-09T15:27:02] INFO: log level: INFO
[2017-08-09T15:27:02] INFO: connection established
[2017-08-09T15:27:02] INFO: service command updated
[2017-08-09T15:27:02] INFO: service command updated
[2017-08-09T15:27:02] INFO: watchdog status: error
[2017-08-09T15:27:03] INFO: starting new process
[2017-08-09T15:27:03] INFO: activeDesktop:Default
[2017-08-09T15:27:03] INFO: starting new process
[2017-08-09T15:27:03] INFO: drag and drop enabled
[2017-08-09T15:27:03] NOTE: started client
[2017-08-09T15:27:03] NOTE: connecting to '192.168.178.22': 192.168.178.22:24800
[2017-08-09T15:27:03] INFO: watchdog status: ok
[2017-08-09T15:27:18] WARNING: failed to connect to server: Timed out
[2017-08-09T15:27:19] NOTE: connecting to '192.168.178.22': 192.168.178.22:24800
[2017-08-09T15:27:34] WARNING: failed to connect to server: Timed out
[2017-08-09T15:27:35] NOTE: connecting to '192.168.178.22': 192.168.178.22:24800
[2017-08-09T15:27:50] WARNING: failed to connect to server: Timed out

This is the log copied from the server ("i5"):
[2017-08-09T15:27:02] INFO: zeroconf client detected: TabletNotebook
[2017-08-09T15:27:17] ERROR: ssl error occurred (system call failure)
[2017-08-09T15:27:17] ERROR: eof violates ssl protocol
[2017-08-09T15:27:17] ERROR: failed to accept secure socket
[2017-08-09T15:27:33] ERROR: ssl error occurred (system call failure)
[2017-08-09T15:27:33] ERROR: eof violates ssl protocol
[2017-08-09T15:27:33] ERROR: failed to accept secure socket
[2017-08-09T15:27:49] ERROR: ssl error occurred (system call failure)
[2017-08-09T15:27:49] ERROR: eof violates ssl protocol
[2017-08-09T15:27:49] ERROR: failed to accept secure socket

Server and all clients have been updated to Synergy v1.9.0rc3 except my Win7-PC, which seems to be incompatible (installation fails), but works fine with Synergy v1.8.8-stable.
All Windows firewalls have been set to grant Synergy "Zugriff" (German for something like "access") in private networks.

I hope this helps you help me, and I am looking forward to hearing from you again.

Share this post


Link to post
Share on other sites

By any chance, do you have that "TabletNotebook" set as a tablet while you try to connect them through Synergy?

Share this post


Link to post
Share on other sites

No, definitely not.
Actually, this TabletNotebook has not been used as a tablet in a long time because I am using another tablet.

The problems definitely started after this:

On 30.7.2017 at 4:23 PM, rabec said:

Windows 10 informed me that my laptop (i.e. client "TabletNotebook") had slowed down so much that it needed to reset and reinstall Windows 10.
Since then I cannot install my 'Synergy 1.8.8 stable' for this client properly.

 

Share this post


Link to post
Share on other sites

I have a feeling that the Windows reinstallation causes the problem, but I am no expert and my feeling may be wrong.

Share this post


Link to post
Share on other sites

Even if the Windows reinstallation has perhaps changed a system setting:
Synergy should work with a newly installed Windows 10!

If this is the official support forum, please don't leave me waiting any longer!

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now