Bug 918320 - [abrt] synergy-1.4.10-1.fc18: closeMutex: Process /usr/bin/synergys was killed by signal 6 (SIGABRT)
Summary: [abrt] synergy-1.4.10-1.fc18: closeMutex: Process /usr/bin/synergys was kille...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: synergy
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9f5203e06d6281241ab1febbf1a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-05 22:06 UTC by Shailender
Modified: 2014-02-05 19:41 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:41:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (23.11 KB, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: build_ids (861 bytes, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: cgroup (130 bytes, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: core_backtrace (2.92 KB, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: dso_list (1.71 KB, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: environ (3.23 KB, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: limits (1.29 KB, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: maps (9.29 KB, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: open_fds (182 bytes, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: proc_pid_status (936 bytes, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details
File: smolt_data (3.56 KB, text/plain)
2013-03-05 22:08 UTC, Shailender
no flags Details

Description Shailender 2013-03-05 22:06:30 UTC
Version-Release number of selected component:
synergy-1.4.10-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        synergys --config synergy.conf
crash_function: closeMutex
executable:     /usr/bin/synergys
kernel:         3.8.1-201.fc18.x86_64
uid:            1000
var_log_messages: Mar  5 16:19:32 localhost abrt[9910]: Saved core dump of pid 1764 (/usr/bin/synergys) to /var/spool/abrt/ccpp-2013-03-05-16:19:31-1764 (18399232 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 closeMutex at /usr/src/debug/synergy-1.4.10-Source/src/lib/arch/CArchMultithreadPosix.cpp:289
 #5 CArchMultithreadPosix::closeMutex at /usr/src/debug/synergy-1.4.10-Source/src/lib/arch/CArchMultithreadPosix.cpp:285
 #6 CXWindowsEventQueueBuffer::~CXWindowsEventQueueBuffer at /usr/src/debug/synergy-1.4.10-Source/src/lib/platform/CXWindowsEventQueueBuffer.cpp:73
 #8 CEventQueue::adoptBuffer at /usr/src/debug/synergy-1.4.10-Source/src/lib/base/CEventQueue.cpp:133
 #9 CXWindowsScreen::onError at /usr/src/debug/synergy-1.4.10-Source/src/lib/platform/CXWindowsScreen.cpp:1727
 #10 CXWindowsScreen::ioErrorHandler at /usr/src/debug/synergy-1.4.10-Source/src/lib/platform/CXWindowsScreen.cpp:1753
 #11 _XIOError at XlibInt.c:1618
 #12 _XEventsQueued at xcb_io.c:365
 #13 XPending at Pending.c:55
 #14 CXWindowsEventQueueBuffer::isEmpty at /usr/src/debug/synergy-1.4.10-Source/src/lib/platform/CXWindowsEventQueueBuffer.cpp:261

Comment 1 Shailender 2013-03-05 22:08:23 UTC
Created attachment 705673 [details]
File: backtrace

Comment 2 Shailender 2013-03-05 22:08:25 UTC
Created attachment 705674 [details]
File: build_ids

Comment 3 Shailender 2013-03-05 22:08:27 UTC
Created attachment 705675 [details]
File: cgroup

Comment 4 Shailender 2013-03-05 22:08:29 UTC
Created attachment 705676 [details]
File: core_backtrace

Comment 5 Shailender 2013-03-05 22:08:30 UTC
Created attachment 705677 [details]
File: dso_list

Comment 6 Shailender 2013-03-05 22:08:32 UTC
Created attachment 705679 [details]
File: environ

Comment 7 Shailender 2013-03-05 22:08:33 UTC
Created attachment 705680 [details]
File: limits

Comment 8 Shailender 2013-03-05 22:08:35 UTC
Created attachment 705682 [details]
File: maps

Comment 9 Shailender 2013-03-05 22:08:36 UTC
Created attachment 705683 [details]
File: open_fds

Comment 10 Shailender 2013-03-05 22:08:38 UTC
Created attachment 705685 [details]
File: proc_pid_status

Comment 11 Shailender 2013-03-05 22:08:39 UTC
Created attachment 705687 [details]
File: smolt_data

Comment 12 Fedora End Of Life 2013-12-21 11:54:09 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2014-02-05 19:41:31 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.