Ubuntu

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

Reported by Martin Olsson on 2009-08-27
918
This bug affects 119 people
Affects Status Importance Assigned to Milestone
Synergy
Unknown
Unknown
synergy (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: synergy

crash

ProblemType: Crash
Architecture: amd64
AssertionMessage: synergys: CArchMultithreadPosix.cpp:286: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
Date: Thu Aug 27 20:03:13 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/synergys
Package: synergy 1.3.1-6ubuntu1
ProcCmdline: /usr/bin/synergys -f --config .quicksynergy/synergy.conf
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
Signal: 6
SourcePackage: synergy
StacktraceTop:
 *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 *__GI_abort () at abort.c:88
 *__GI___assert_fail (assertion=0x477d7d "status == 0", file=<value optimized out>, line=<value optimized out>, function=0x478360 "virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*)") at assert.c:83
 ?? ()
 ?? ()
Title: synergys assert failure: synergys: CArchMultithreadPosix.cpp:286: virtual void CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0' failed.
Uname: Linux 2.6.31-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Martin Olsson (mnemo) wrote :
visibility: private → public

StacktraceTop:raise () from /lib/libc.so.6
abort () from /lib/libc.so.6
__assert_fail () from /lib/libc.so.6
CArchMultithreadPosix::closeMutex (
~CXWindowsEventQueueBuffer (this=0x1ec2dc0)

Changed in synergy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Derek (bugs-m8y) wrote :

Same assertion is failing, only on 32 bit x86

Tuukka Hastrup (tuukkah) wrote :

Same here, and I didn't have to do more than log in and wait a sec. I don't even have any synergy client machines turned on.

Dominik Sommer (dominik.sommer) wrote :

Experiencing the same as Tuukka since upgrading to Ubuntu 09.10.

Derek (bugs-m8y) wrote :

Happens to me every few hours maybe.
Sometimes lasts a day.

My workaround as been:
while((1));do synergys -f;done

Martin Olsson (mnemo) wrote :

I just hit it again on a x64 box with synergy 1.3.1-6ubuntu1 (Lucid pre-release).

Chris Johnston (cjohnston) wrote :

Martin, I'm having the same problem on x64.

Chris Johnston (cjohnston) wrote :

If I try running synergy via synergs -f I get:

INFO: synergys.cpp,1042: Synergy server 1.3.1 on Linux 2.6.32-12-generic #16-Ubuntu SMP Thu Jan 28 07:47:05 UTC 2010 x86_64
DEBUG: synergys.cpp,1051: opening configuration "/home/chris/.synergy.conf"
DEBUG: synergys.cpp,1062: configuration read successfully
DEBUG: CXWindowsScreen.cpp,847: XOpenDisplay(":0.0")
DEBUG: CXWindowsScreenSaver.cpp,339: xscreensaver window: 0x00000000
DEBUG: CXWindowsScreen.cpp,117: screen shape: 0,0 3360x1050 (xinerama)
DEBUG: CXWindowsScreen.cpp,118: window is 0x04c00004
DEBUG: CScreen.cpp,38: opened display
WARNING: synergys.cpp,505: cannot listen for clients: cannot bind address: Address already in use
DEBUG: synergys.cpp,519: retry in 10 seconds

Changed in synergy (Ubuntu):
status: New → Confirmed
Daniel Holbert (dholbert) wrote :

> WARNING: synergys.cpp,505: cannot listen for clients:
> cannot bind address: Address already in use

That just means you already have synergys running on that machine... Do "killall synergys" and try again.

Chris Johnston (cjohnston) wrote :

Daniel, I am now getting:

INFO: synergyc.cpp,716: Synergy client 1.3.1 on Linux 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64
DEBUG: CXWindowsScreen.cpp,847: XOpenDisplay(":0.0")
DEBUG: CXWindowsScreenSaver.cpp,339: xscreensaver window: 0x00000000
DEBUG: CXWindowsScreen.cpp,117: screen shape: 0,0 1920x1200
DEBUG: CXWindowsScreen.cpp,118: window is 0x05000004
DEBUG: CScreen.cpp,38: opened display
NOTE: synergyc.cpp,330: started client
WARNING: synergyc.cpp,265: failed to connect to server: Timed out
DEBUG: synergyc.cpp,237: retry in 1 seconds
WARNING: synergyc.cpp,265: failed to connect to server: Timed out
DEBUG: synergyc.cpp,237: retry in 3 seconds
^CDEBUG: CScreen.cpp,49: closed display
NOTE: synergyc.cpp,408: stopped client

on the client computer. The server system appears to be running properly.

Daniel Holbert (dholbert) wrote :

Chris, I'm not sure what that issue means -- perhaps a firewall / connectivity problem? -- but in any case, we shouldn't discuss it any further here. I'd recommend taking that to Google, the ubuntu forums, or #ubuntu on irc.freenode.net.

This bug page here is for discussion of the specific issue it was filed on (a particular assertion failure & abort in synergy). If we use it to talk about unrelated synergy issues, then it just gets impossible to read.

Martin Olsson (mnemo) wrote :

I've switched from the outdated synergy packaged that Lucid provides to synergy-plus, but that synergy fork also exhibits this particular bug. Since the real synergy upstream has ceased all development and bugfixing I reported the bug to synergy-plus. The bug report at _that_ upstream is located here:
http://code.google.com/p/synergy-plus/issues/detail?id=418

Martin Olsson (mnemo) wrote :

btw, launchpad bug 385529 is a wishlist item that requests the the synergy Ubuntu/Debian package should be replaced by the latest version from the synergy-plus upstream.

tags: added: bugpattern-needed

Experiencing problem after upgrade to Ubuntu 10.10 RC.

bug 655475

tags: added: precise
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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