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

Bug #745009 reported by Chow Loong Jin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synergy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: synergy

I'm not sure what happened or when it crashed -- I just happened to find the crash report in /var/crash, which I thought might be useful to file.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: synergy 1.3.1-6ubuntu1
Uname: Linux 2.6.38.2-ck2-hyper1 x86_64
Architecture: amd64
AssertionMessage: synergys: CArchMultithreadPosix.cpp:286: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
Date: Thu Mar 24 01:34:59 2011
ExecutablePath: /usr/bin/synergys
ProcCmdline: /usr/bin/synergys -f --config .quicksynergy/synergy.conf
ProcEnviron:
 LANGUAGE=en_SG:en
 PATH=(custom, user)
 LANG=en_SG.utf8
 SHELL=/bin/zsh
Signal: 6
SourcePackage: synergy
StacktraceTop:
 raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __assert_fail (assertion=0x477d7d "status == 0", file=<value optimized out>, line=286, function=0x478360 "virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*)") at assert.c:81
 CArchMultithreadPosix::closeMutex (this=<value optimized out>, mutex=0x1269830) at CArchMultithreadPosix.cpp:286
 CXWindowsEventQueueBuffer::~CXWindowsEventQueueBuffer (this=0x1269710, __in_chrg=<value optimized out>) at CXWindowsEventQueueBuffer.cpp:75
Title: synergys assert failure: synergys: CArchMultithreadPosix.cpp:286: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin mail netdev plugdev sambashare sbuild tape vboxusers video

Revision history for this message
Chow Loong Jin (hyperair) 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 #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.

visibility: private → public
tags: removed: need-amd64-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.