synergy segfault at 08206344 eip b7dd00d2 esp bf8904a4 error 4

[Aaron C. de Bruyn]

Binary package hint: synergy

The synergy client crashes on my server 1-2 times per day with the following being logged into syslog:

segfault at 08206344 eip b7dd00d2 esp bf8904a4 error 4

I can not reproduce it every time--only 1-2 times per day, but it is always after the screensaver is on and I try to move my mouse over to that machine to do some work.

[mistermix (llinde)]

I see the same thing on 8.04 though I can't correlate it with screensaver activity.

[skwash (josh-skwash)]

I'm seeing the same thing on 8.04 except it is the synergy server (1.3.1) that is crashing. The client connected to it is SynergyKM (OS X) version 1.3.0.

I can pin most of it on clipboard activity. The segfault usually occurs as soon as I do a cmd+c (which is really alt+c on the keyboard) to copy (but not every time!).

synergys[6736]: segfault at 08206344 eip b7d9b0d2 esp bfcba574 error 4

I also have a windows client (1.3.1) connected which doesn't ever seem to cause the problem. I am going to try an updated version of the mac client and see if it behaves any better.

[Marcin Owsiany (marcin-owsiany-pl)]

My synergy server just died with the following message from the kernel:
synergys[10785]: segfault at 18 rip 7fbf072b1f04 rsp 7fff104aaf88 error 4

I noticed that when I tried to switch to a client's screen, but I don't know if that was the moment it died, or shortly before that. The only significant thing that happened between I last had my cursor on the client's screen was that the screen saver activated on the client.

This is the first time it's happened to me, I've been using synergy every day for 8 hours a day for the last half a year or so.
But maybe the people for whom it crashes more often could consider running with -d DEBUG2 and hope to get some context on what it does when it crashes?

This is synergy 1.3.1-2ubuntu2 on Ubuntu 8.04.1.
The client is also synergy 1.3.1-2ubuntu2 but on gutsy.

[Thomas Hotz (thotz-deactivatedaccount)]

Marking the bug as confirmed because it happens to several users.