Public bug reported:
Binary package hint: synergy
A synergy_1.3.1-4ubuntu1 client (the current in intrepid) fails to
connect to a server running gutsy (synergy_1.3.1-2ubuntu2). Synergy
works fine if I install the gutsy package on the intrepid client. It
also works if I install the 1.3.1-4 package from Debian unstable -- and
in the case of the latter, it does not exhibit the lags described in bug
#194029 -- yay!
A dump with Wireshark shows that the -4ubuntu1 client fails to complete
the synergy handshake with the server. I'll attach a .pcap file showing
the failed connection attempt. I've looked at the traffic from both
sides, and it's identical, i.e. the server sees what the client sends,
and vice versa. The last two packets in the dump are sent after sending
the client SIGQUIT (with Ctrl-\) and the two before it are from occur
after the connection times out. Before hitting Ctrl-\, netstat(8) on
the client shows the connection in CLOSE_WAIT.
The Ubuntu-specific changes to the upstream 1.3.1-4 package seem pretty
innocuous, so this is strange. I tried to rebuild the Debian source
package against intrepid, but the build failed due to Werror stuff -- I
need to hunker down and try to make it build, but it's not gonna happen
today. If anyone can provide any information on why the same source
builds on Debian, and not on Ubuntu, that would be useful.
I'll also attach the output of `synergyc -f -d DEBUG2 {server.name} and
an strace of the client when it fails to connect. The strace and
top(1)'s WCHAN field agree that the client is stuck in futex_wait.
So, lots of info; hopefully some of it's useful. What can I do to help
get this fixed?
Thanks.
** Affects: synergy (Ubuntu)
Importance: Undecided
Status: New
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
