Thanks Kees! It works perfectly again now!
--
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
This bug was fixed in the package synergy - 1.3.1-4ubuntu2
---
synergy (1.3.1-4ubuntu2) intrepid; urgency=low
* Revert fortify warning cleanups from prior upload.
* debian/control: Add missing XInput build dep (see LP 273386).
* debian/rules: disable FORTIFY, as this is the majo
It happens also in Intrepid(client) and windows server 2k8 (server). It
fails to connect and it forks a lot...
--
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 subscrib
** Changed in: synergy (Ubuntu)
Assignee: Conan (richard-connon) => (unassigned)
--
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
** Changed in: synergy (Ubuntu)
Assignee: (unassigned) => Conan (richard-connon)
--
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
One additional note: I'm running AMD64 version of Intrepid.
As with others the 1.3.1-5 package from debian unstable works for me
(debian AMD64 version).
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you ar
Just writing in to confirm that I've been experiencing this same problem
with Intrepid acting as the server and a Mac OS X Leopard client.
Everything worked fine with hardy.
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notifica
There are compiler differences[1] between Debian and Ubuntu as well. I
will try to isolate the root cause of the problems.
[1] https://wiki.ubuntu.com/CompilerFlags
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification be
Subscribed Kees Cook to this bug as he made the only changes present
between debian and ubuntu versions which seem to cause the bug.
** Tags added: regression-potential
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification
I am seeing this bug with an Intrepid client (synergy_1.3.1-4ubuntu1)
and XP server running synergy 1.3.1. Everything operates normally after
downgrading the Intrepid client to Hardy's synergy 1.3.1-2ubuntu2
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/25
I can also confirm that synergy server in the intrepid package seem to
be completely broken. debian unstable package works fine.
--
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,
I can also confirm that if you use the hardy package, it all works
again. Whatever changes happened between hardy and intrepid for this
package cause it to be completely busted.
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug not
I'm seeing this same issue with intrepid client / hardy server.
--
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
ubu
Have this issue too -- connection accepted, then timout.
Synergy is becoming more and more broken with each release ):
--
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
Confirming this bug with intrepid as a client. Attaching the DEBUG2
level log from synergyc.
** Attachment added: "synergylog.txt"
http://launchpadlibrarian.net/17240077/synergylog.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received t
** Changed in: synergy (Ubuntu)
Status: New => Confirmed
--
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
ubu
Confirming with WindowsXP as client and Intrepid as server.
Server notifies of client connection and that's it. Once after vey long time
(minutes) there was message about timeout.
Rolling back to hardy's version solves the problem.
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bu
hardy package on the client side (hardy server) fixes this as well
--
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
Installing the Debian unstable version on the server side fixes both the
connection issue and the performance issues from bug #194029.
--
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
Confirming this bug report although both client and server are Intrepid.
The connection attempt from the client seems to trigger high CPU usage
in the server.
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because y
...and I should have said hardy, not gutsy, in all instances above.
I'm walking away from the keyboard now. ;-)
--
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 subsc
Okay, it looks like the .pcap I attached doesn't include the last two
packets I described in the original report -- i.e. the last two packets
are from the connection timing out, and the two packets I once saw after
Ctrl-\'ing the client aren't in there. Maybe they weren't sent this
time (though I
** Attachment added: "strace of failed synergyc connect"
http://launchpadlibrarian.net/16237671/synergy_strace.txt
--
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
** Attachment added: "Output of `synergyc -f -d DEBUG2 {server.name}`"
http://launchpadlibrarian.net/16237663/synergy-debug2.txt
--
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
B
** Attachment added: ".pcap of failed connect of synergy client"
http://launchpadlibrarian.net/16237650/handshake_failed.pcap
--
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
25 matches
Mail list logo
