Timeout issue with edgy as server and feisty as client

Bug #91540 reported by Billy Kwong
14
Affects Status Importance Assigned to Milestone
synergy (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: synergy

Scenario: Have a desktop running edgy, acting as the synergy server, and laptop running feisty, connecting to the desktop.

When both was running edgy, synergy runs fine. After I've upgraded my laptop to feisty, synergy times out sporadically, despite that both versions of synergy from edgy and feisty are the same.

Note that I'm using 2.6.17-11 from edgy atm, due to another bug I'm having on my laptop (https://launchpad.net/bugs/89615)

Revision history for this message
werickson (werickson) wrote :

I can confirm that this problem occurs for me and many other feisty users. However, what is left out of this report is the fact that after the lag subsides, all the input sent to the synergy client is performed.

My server is running on XP and my client is running on Feisty.

Visit this thread for more information:
http://www.ubuntuforums.org/showthread.php?t=372513

Revision history for this message
stevenschlansker (stevenschlansker) wrote :

I have the same problem with a Mac OS X synergy server and feisty as the client.

Revision history for this message
stevenschlansker (stevenschlansker) wrote :

This also happens if you compile synergy from source.

Revision history for this message
lineymo (lineymo) wrote :

Following the thread linked above, it seems like it more an issue with X.org than synergy. Not sure if this bug should be listed there as well.

Revision history for this message
Billy Kwong (tuppa) wrote :

Since a dist-upgrade yesterday, it seems that this bug has been resolved with a newer package revision of xorg.

Revision history for this message
Mario Limonciello (superm1) wrote :

This was recently fixed by an update with xorg packages on Feisty.

Changed in synergy:
status: Unconfirmed → Fix Released
Revision history for this message
tokei (mail-stephan-mann) wrote :

I was running a synergy server on Feisty and two notebooks with Gutsy. Everything worked fine. Yesterday, I updated one of the notebooks to Hardy Beta and I'm experiencing the problems described above on this notebook now. Mouse/keyboard seem to freeze completely, but keyboard input gets through eventually, without any lost keystrokes.

Synergy is 1.3.1 on all three machines. Xorg is 7.3 on the client running Hardy. I've attached a log from synergyc with debug level DEBUG2.

Revision history for this message
werickson (werickson) wrote : Re: [Bug 91540] Re: Timeout issue with edgy as server and feisty as client

Hello Tokei,

May I suggest posting about this issue in the below forum thread in
addition to your description of the bug, to allow others experiencing
the same problem the opportunity to confirm or deny it. I believe
that helped to get the bug resolved in the previous release.

http://ubuntuforums.org/showthread.php?t=372513&page=3

-Will

On Sun, Apr 20, 2008 at 2:01 PM, tokei <email address hidden> wrote:
> I was running a synergy server on Feisty and two notebooks with Gutsy.
> Everything worked fine. Yesterday, I updated one of the notebooks to
> Hardy Beta and I'm experiencing the problems described above on this
> notebook now. Mouse/keyboard seem to freeze completely, but keyboard
> input gets through eventually, without any lost keystrokes.
>
> Synergy is 1.3.1 on all three machines. Xorg is 7.3 on the client
> running Hardy. I've attached a log from synergyc with debug level
> DEBUG2.
>
> ** Attachment added: "synergy.log"
> http://launchpadlibrarian.net/13590268/synergy.log
>
> --
> Timeout issue with edgy as server and feisty as client
> https://bugs.launchpad.net/bugs/91540
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
tokei (mail-stephan-mann) wrote :

Apparently, running the client as root solves the problem, but IMHO this is a workaround, not a solution.

Revision history for this message
helpdeskdan (helpdeskdan-gmail) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.