synergys crashed with SIGSEGV in std::_Rb_tree_increment()

[komputes]

Binary package hint: synergy

Cannot attribute crash to any particular action.

synergy is going through an ssh tunnel. ssh connection on client seems to have disconnected and could not reconnect unless I did it manually.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Jan 25 12:43:57 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: 0x1707a2 <_ZSt18_Rb_tree_incrementPSt18_Rb_tree_node_base+18>: mov 0x8(%edx),%edx
 PC (0x001707a2) ok
 source "0x8(%edx)" (0x00b9e3a0) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown 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 vboxusers

[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.