Bug 1303616

Summary: [abrt] synergy: ArchMultithreadPosix::closeMutex(): synergys killed by SIGABRT
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: synergyAssignee: Christian Krause <chkr>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: brian, chkr, kupo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/cdd0f2da4bf9d110804ae3a692655be0dba2f8ca
Whiteboard: abrt_hash:561a7a94d65541fad8fad5fbf430e84df3f9b4ac;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 18:21:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brian J. Murrell 2016-02-01 13:09:30 UTC
Version-Release number of selected component:
synergy-1.6.2-3.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        synergys -f --config /home/brian/.quicksynergy/synergy.conf
crash_function: ArchMultithreadPosix::closeMutex
executable:     /usr/bin/synergys
global_pid:     3338
kernel:         4.3.3-303.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 ArchMultithreadPosix::closeMutex at /usr/src/debug/synergy-1.6.2/src/lib/arch/unix/ArchMultithreadPosix.cpp:292
 #5 XWindowsEventQueueBuffer::~XWindowsEventQueueBuffer at /usr/src/debug/synergy-1.6.2/src/lib/platform/XWindowsEventQueueBuffer.cpp:77
 #7 EventQueue::adoptBuffer at /usr/src/debug/synergy-1.6.2/src/lib/base/EventQueue.cpp:185
 #8 XWindowsScreen::onError at /usr/src/debug/synergy-1.6.2/src/lib/platform/XWindowsScreen.cpp:1736
 #9 XWindowsScreen::ioErrorHandler at /usr/src/debug/synergy-1.6.2/src/lib/platform/XWindowsScreen.cpp:1762
 #10 _XIOError at XlibInt.c:1464
 #11 _XEventsQueued at xcb_io.c:366
 #12 XPending at Pending.c:55
 #13 XWindowsEventQueueBuffer::isEmpty at /usr/src/debug/synergy-1.6.2/src/lib/platform/XWindowsEventQueueBuffer.cpp:265
 #14 EventQueue::getEvent at /usr/src/debug/synergy-1.6.2/src/lib/base/EventQueue.cpp:205

Potential duplicate: bug 1218111

Comment 1 Brian J. Murrell 2016-02-01 13:09:37 UTC
Created attachment 1120096 [details]
File: backtrace

Comment 2 Brian J. Murrell 2016-02-01 13:09:37 UTC
Created attachment 1120097 [details]
File: cgroup

Comment 3 Brian J. Murrell 2016-02-01 13:09:38 UTC
Created attachment 1120098 [details]
File: core_backtrace

Comment 4 Brian J. Murrell 2016-02-01 13:09:39 UTC
Created attachment 1120099 [details]
File: dso_list

Comment 5 Brian J. Murrell 2016-02-01 13:09:40 UTC
Created attachment 1120100 [details]
File: environ

Comment 6 Brian J. Murrell 2016-02-01 13:09:41 UTC
Created attachment 1120101 [details]
File: limits

Comment 7 Brian J. Murrell 2016-02-01 13:09:42 UTC
Created attachment 1120102 [details]
File: maps

Comment 8 Brian J. Murrell 2016-02-01 13:09:43 UTC
Created attachment 1120103 [details]
File: mountinfo

Comment 9 Brian J. Murrell 2016-02-01 13:09:44 UTC
Created attachment 1120104 [details]
File: namespaces

Comment 10 Brian J. Murrell 2016-02-01 13:09:45 UTC
Created attachment 1120105 [details]
File: open_fds

Comment 11 Brian J. Murrell 2016-02-01 13:09:46 UTC
Created attachment 1120106 [details]
File: proc_pid_status

Comment 12 Brian J. Murrell 2016-02-01 13:09:47 UTC
Created attachment 1120107 [details]
File: var_log_messages

Comment 13 Brian J. Murrell 2016-03-14 18:30:12 UTC
Just hit this again.

Comment 14 Brian J. Murrell 2016-04-11 14:53:07 UTC
And hit again.  Why has this not even been triaged?  Is this package more or less unsupported in Fedora?

Can we at least get an update to the 1.7 stable to see if upstream bug fixes have  resolved this and the many other synergy issues?

Comment 15 Johan Swensson 2016-04-18 05:28:42 UTC
(In reply to Brian J. Murrell from comment #14)
> Can we at least get an update to the 1.7 stable to see if upstream bug fixes
> have  resolved this and the many other synergy issues?

1.7.6 is now available in updates-testing, feel free to try it out to see if it resolves your issue.

Comment 16 Fedora End Of Life 2016-11-24 15:19:53 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.

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 17 Fedora End Of Life 2016-12-20 18:21:56 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.