synergys assert failure: synergys: /build/buildd/synergy-1.3.6/lib/arch/CArchMultithreadPosix.cpp:289: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.

Bug #858817 reported by Bryan Paddock
0
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synergy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Synergy server was running in background. Had 1 client (XP with stable ver of synergy-c). Was not using the client PC at time of crash. Had to restart synergy to continue.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: synergy 1.3.6-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
AssertionMessage: synergys: /build/buildd/synergy-1.3.6/lib/arch/CArchMultithreadPosix.cpp:289: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
CrashCounter: 1
Date: Sun Sep 25 13:04:09 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/synergys
ProcCmdline: synergys -c /etc/synergy.cfg
Signal: 6
SourcePackage: synergy
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 CArchMultithreadPosix::closeMutex(CArchMutexImpl*) ()
Title: synergys assert failure: synergys: /build/buildd/synergy-1.3.6/lib/arch/CArchMultithreadPosix.cpp:289: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Bryan Paddock (bryanpaddock) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #732684, 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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