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
Created attachment 1120096 [details] File: backtrace
Created attachment 1120097 [details] File: cgroup
Created attachment 1120098 [details] File: core_backtrace
Created attachment 1120099 [details] File: dso_list
Created attachment 1120100 [details] File: environ
Created attachment 1120101 [details] File: limits
Created attachment 1120102 [details] File: maps
Created attachment 1120103 [details] File: mountinfo
Created attachment 1120104 [details] File: namespaces
Created attachment 1120105 [details] File: open_fds
Created attachment 1120106 [details] File: proc_pid_status
Created attachment 1120107 [details] File: var_log_messages
Just hit this again.
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?
(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.
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.
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.