synergys assert failure: synergys: /build/buildd/synergy-1.3.6/lib/arch/CArchMultithreadPosix.cpp:289: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
synergy (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When I use ("share") synergy on the desktop (controlling the notebook beside), then turn off the notebook and log out of the desktop, next time I log in the desktop (gnome-session), login takes longer than usual, and when I see the usual session screen, I also get this apport notification. Presumably synergy server handles logout/login improperly.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: synergy 1.3.6-1ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
AssertionMessage: synergys: /build/
CrashCounter: 1
Date: Mon Sep 5 00:39:27 2011
ExecutablePath: /usr/bin/synergys
ProcCmdline: /usr/bin/synergys -f --config .quicksynergy/
ProcEnviron:
LANGUAGE=en_US:en
LC_CTYPE=
LC_COLLATE=
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: synergy
StacktraceTop:
raise (sig=6) at ../nptl/
abort () at abort.c:92
__assert_fail (assertion=0x4a2e16 "status == 0", file=<value optimized out>, line=289, function=<value optimized out>) at assert.c:81
CArchMultithre
CXWindowsEvent
Title: synergys assert failure: synergys: /build/
UpgradeStatus: Upgraded to natty on 2011-05-12 (115 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video
XsessionErrors:
(evolution-
(evolution-
(evolution-
(evolution-
(evolution-
visibility: | private → public |
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.