Ubuntu
synergy package

synergys assert failure: synergys: CArchMultithreadPosix.cpp:286: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.

Bug #472715 reported by warelock on 2009-11-03

This bug report is a duplicate of: Bug #420088: synergys assert failure: synergys: CArchMultithreadPosix.cpp:286: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	synergy (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: synergy

Ubuntu release: 9.10
Package version: 1.3.1-6ubuntu1

It will not run.

ProblemType: Crash
Architecture: i386
AssertionMessage: synergys: CArchMultithreadPosix.cpp:286: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
Date: Tue Nov 3 05:33:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/synergys
NonfreeKernelModules: nvidia
Package: synergy 1.3.1-6ubuntu1
ProcCmdline: /usr/bin/synergys
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
Signal: 6
SourcePackage: synergy
StacktraceTop:
__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
*__GI___assert_fail (assertion=0x80bb329 "status == 0",
?? ()
Title: synergys assert failure: synergys: CArchMultithreadPosix.cpp:286: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Tags:

Revision history for this message

warelock (k36khqu02) wrote on 2009-11-03:

XsessionErrors.txt Edit (2.8 KiB, text/plain; charset="utf-8")

Revision history for this message

warelock (k36khqu02) wrote on 2009-11-05:

It's working now.

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-12: 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 #420088, 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.