Ubuntu
synergy package

synergys crashed with SIGABRT in raise()

Bug #984611 reported by Oytun on 2012-04-18

This bug report is a duplicate of: Bug #922428: synergys crashed with SIGABRT in __GI___assert_fail(). Edit Remove

This bug affects 1 person

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

Bug Description

I dont know upgrading system.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synergy 1.3.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu4
Architecture: i386
Date: Wed Apr 18 05:48:04 2012
ExecutablePath: /usr/bin/synergys
ExecutableTimestamp: 1324890518
InstallationMedia: This
ProcCmdline: /usr/bin/synergys -f --config .quicksynergy/synergy.conf
ProcCwd: /home/nuty
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
Signal: 6
SourcePackage: synergy
StacktraceTop:
raise () from /lib/i386-linux-gnu/libc.so.6
abort () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libc.so.6
__assert_fail () from /lib/i386-linux-gnu/libc.so.6
CArchMultithreadPosix::closeMutex(CArchMutexImpl*) ()
Title: synergys crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-04-16 (1 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Tags:

Revision history for this message

Oytun (oytunistrator) wrote on 2012-04-18:

Dependencies.txt Edit (779 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-18: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #922428, 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.