Version-Release number of selected component: 1:synergy-1.8.8-3.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: synergys -c /etc/synergy.conf crash_function: count_bits executable: /usr/bin/synergys journald_cursor: s=05fdd028e9244b6797c9a11a3860831f;i=23aaf;b=7d87c3ce6aab4dd397b8c214b66e2ec7;m=1ee77858dd6;t=56918ee7cb1b3;x=6f2d50cd35316709 kernel: 4.15.6-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 14986 Truncated backtrace: Thread no. 1 (10 frames) #0 count_bits at XExtInt.c:439 #1 copyRawEvent at XExtInt.c:1397 #2 XInputCopyCookie at XExtInt.c:1490 #3 _XCopyEventCookie at XlibInt.c:707 #4 XPeekEvent at PeekEvent.c:48 #5 XWindowsScreen::refreshKeyboard at /usr/src/debug/synergy-1.8.8-3.fc27.x86_64/src/lib/platform/XWindowsScreen.cpp:2030 #6 XWindowsScreen::handleSystemEvent at /usr/src/debug/synergy-1.8.8-3.fc27.x86_64/src/lib/platform/XWindowsScreen.cpp:1395 #7 EventQueue::dispatchEvent at /usr/src/debug/synergy-1.8.8-3.fc27.x86_64/src/lib/base/EventQueue.cpp:271 #8 EventQueue::loop at /usr/src/debug/synergy-1.8.8-3.fc27.x86_64/src/lib/base/EventQueue.cpp:129 #9 ServerApp::mainLoop at /usr/src/debug/synergy-1.8.8-3.fc27.x86_64/src/lib/synergy/ServerApp.cpp:756 Potential duplicate: bug 1325397
Created attachment 1417655 [details] File: backtrace
Created attachment 1417656 [details] File: cgroup
Created attachment 1417657 [details] File: core_backtrace
Created attachment 1417658 [details] File: cpuinfo
Created attachment 1417659 [details] File: dso_list
Created attachment 1417660 [details] File: environ
Created attachment 1417661 [details] File: exploitable
Created attachment 1417662 [details] File: limits
Created attachment 1417663 [details] File: maps
Created attachment 1417664 [details] File: mountinfo
Created attachment 1417665 [details] File: open_fds
Created attachment 1417666 [details] File: proc_pid_status
Created attachment 1417667 [details] File: var_log_messages
Similar problem has been detected: suspended the laptop (as synergy server) while connected to a synergy client, then resumed it on a different network without the client reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: synergys -c /etc/synergy.conf crash_function: count_bits executable: /usr/bin/synergys journald_cursor: s=3d8677c0da4a4383a056dae285ed7f52;i=137a8;b=236a603e268646eaa5e04393b521a903;m=14ad0803f35;t=572fff7cb2d93;x=d0f8a926692ea6b9 kernel: 4.17.7-100.fc27.x86_64 package: 1:synergy-1.8.8-3.fc27 reason: synergys killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 14986
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.