Version-Release number of selected component: synergy-1.4.10-6.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: synergys -f --config /home/brian/.quicksynergy/synergy.conf crash_function: CArchMultithreadPosix::closeMutex executable: /usr/bin/synergys kernel: 3.17.7-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #4 CArchMultithreadPosix::closeMutex at /usr/src/debug/synergy-1.4.10-Source/src/lib/arch/CArchMultithreadPosix.cpp:289 #5 CXWindowsEventQueueBuffer::~CXWindowsEventQueueBuffer at /usr/src/debug/synergy-1.4.10-Source/src/lib/platform/CXWindowsEventQueueBuffer.cpp:73 #7 CEventQueue::adoptBuffer at /usr/src/debug/synergy-1.4.10-Source/src/lib/base/CEventQueue.cpp:133 #8 CXWindowsScreen::onError at /usr/src/debug/synergy-1.4.10-Source/src/lib/platform/CXWindowsScreen.cpp:1727 #9 CXWindowsScreen::ioErrorHandler at /usr/src/debug/synergy-1.4.10-Source/src/lib/platform/CXWindowsScreen.cpp:1753 #10 _XIOError at XlibInt.c:1498 #11 _XEventsQueued at xcb_io.c:366 #12 XPending at Pending.c:55 #13 CXWindowsEventQueueBuffer::isEmpty at /usr/src/debug/synergy-1.4.10-Source/src/lib/platform/CXWindowsEventQueueBuffer.cpp:261 #14 CEventQueue::getEvent at /usr/src/debug/synergy-1.4.10-Source/src/lib/base/CEventQueue.cpp:153 Potential duplicate: bug 1046700
Created attachment 976422 [details] File: backtrace
Created attachment 976423 [details] File: cgroup
Created attachment 976424 [details] File: core_backtrace
Created attachment 976425 [details] File: dso_list
Created attachment 976426 [details] File: environ
Created attachment 976427 [details] File: limits
Created attachment 976428 [details] File: maps
Created attachment 976429 [details] File: open_fds
Created attachment 976430 [details] File: proc_pid_status
Created attachment 976431 [details] File: var_log_messages
Indeed, this does look like a duplicate of bug 1046700. If this bug is closed as such, please update the Version: in bug 1046700 to reflect the currency (F21) of this bug so that it does not get closed as EOL prematurely.
Another user experienced a similar problem: aftter starting the synergyc the whole gnome-shell crashes and it asks me to relogin! reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: synergyc --name gabrielLaptop --daemon 192.168.100.2 crash_function: CArchMultithreadPosix::closeMutex executable: /usr/bin/synergyc kernel: 3.17.8-300.fc21.x86_64 package: synergy-1.4.10-6.fc21 reason: synergyc killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.