synergys crashed with SIGSEGV in std::_Rb_tree_increment()

[komputes]

Binary package hint: synergy

I have two computers. "cool" which was sharing synergy (though QuickSynergy) which crashed when the client computer "karma" connected to cool via sftp (through gnome). Synergy is running through an ssh tunnel.

Steps to reproduce:
Computer 1 Shares
Computer 1 has openssh server
Computer 2 creates a tunnel for port 24800
Computer 2 lonnects to localhost in synergy (QuickSynergy)
(30 minutes of use goes by)
Computer 2 uses Gnome's Connect to server SSH (SFTP) to connect to Computer 1

Result:
Synergy crashes on Computer 1

Expected:
Synergy and sftp should work in harmony

ProblemType: Crash
Architecture: i386
Date: Thu Jan 21 09:35:32 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/synergys
Package: synergy 1.3.1-6ubuntu1
ProcCmdline: /usr/bin/synergys -f --config .quicksynergy/synergy.conf
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
SegvAnalysis:
 Segfault happened at: 0xdb87b5 <_ZSt18_Rb_tree_incrementPSt18_Rb_tree_node_base+37>: cmp 0xc(%edx),%eax
 PC (0x00db87b5) ok
 source "0xc(%edx)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: synergy
StacktraceTop:
 std::_Rb_tree_increment(std::_Rb_tree_node_base*) ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synergys crashed with SIGSEGV in std::_Rb_tree_increment()
Uname: Linux 2.6.32-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #501239, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.