Description of problem: I have: - desktop w/ F21 that acts as a server (dual monitor) - wired connection, mouse wireless on it's own receiver - laptop w/ F21 that is the client - wireless connection Desktop starts synergys from a bash I created after login. Laptop - I start the client (w/ some params if I'm at home and w/ other params if I'm in the office) What actually caues the issue i do not now! :( Version-Release number of selected component: synergy-1.6.2-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: synergyc --daemon --name devops-remote.brainient-dev.com --restart 192.168.100.2 crash_function: ArchMultithreadPosix::closeMutex executable: /usr/bin/synergyc kernel: 3.19.5-200.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Thu 2014-12-11 11:29:55 EET, end at Mon 2015-05-04 09:51:43 EEST. -- 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:1498 #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
Created attachment 1021587 [details] File: backtrace
Created attachment 1021588 [details] File: cgroup
Created attachment 1021589 [details] File: core_backtrace
Created attachment 1021590 [details] File: dso_list
Created attachment 1021591 [details] File: environ
Created attachment 1021592 [details] File: limits
Created attachment 1021593 [details] File: maps
Created attachment 1021594 [details] File: open_fds
Created attachment 1021595 [details] File: proc_pid_status
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.