Description of problem: In my case, this seems to happen when my Fedora machine (the Synergy client) and the Synergy server (a Windows machine) both have their screens unlocked after being locked for an extended period of time. Version-Release number of selected component: synergy-2.0.0-3.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/synergyc --no-daemon --no-restart --debug WARNING --name anubis --enable-crypto EWeatherwax-02:24800 crash_function: ArchNetworkBSD::copySocket executable: /usr/bin/synergyc journald_cursor: s=4d117ce24ed2469b8722ab2be752a052;i=e86e;b=b4988446f8884bee8c495de227a5c665;m=11feb0cd73;t=57314225f858c;x=8f1ee2395fe61c30 kernel: 4.17.12-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ArchNetworkBSD::copySocket at /usr/src/debug/synergy-2.0.0-3.fc28.x86_64/src/lib/arch/unix/ArchNetworkBSD.cpp:135 #1 TSocketMultiplexerMethodJob<SecureSocket>::TSocketMultiplexerMethodJob at /usr/src/debug/synergy-2.0.0-3.fc28.x86_64/src/./lib/net/TCPSocket.h:80 #2 SecureSocket::secureConnect() at /usr/src/debug/synergy-2.0.0-3.fc28.x86_64/src/lib/net/SecureSocket.cpp:132 #3 EventQueue::dispatchEvent at /usr/src/debug/synergy-2.0.0-3.fc28.x86_64/src/lib/base/EventQueue.cpp:271 #4 EventQueue::loop() at /usr/src/debug/synergy-2.0.0-3.fc28.x86_64/src/lib/base/EventQueue.cpp:129 #5 ClientApp::mainLoop() at /usr/src/debug/synergy-2.0.0-3.fc28.x86_64/src/lib/core/ClientApp.cpp:482 #6 ClientApp::runInner(int, char**, ILogOutputter*, int (*)(int, char**)) at /usr/src/debug/synergy-2.0.0-3.fc28.x86_64/src/lib/core/ClientApp.cpp:537 #7 App::run(int, char**) at /usr/src/debug/synergy-2.0.0-3.fc28.x86_64/src/./lib/core/App.h:86 #9 __libc_print_version at version.c:45 #10 ??
Created attachment 1475000 [details] File: backtrace
Created attachment 1475001 [details] File: cgroup
Created attachment 1475002 [details] File: core_backtrace
Created attachment 1475003 [details] File: cpuinfo
Created attachment 1475004 [details] File: dso_list
Created attachment 1475005 [details] File: environ
Created attachment 1475006 [details] File: exploitable
Created attachment 1475007 [details] File: limits
Created attachment 1475008 [details] File: maps
Created attachment 1475009 [details] File: mountinfo
Created attachment 1475010 [details] File: open_fds
Created attachment 1475011 [details] File: proc_pid_status
Created attachment 1475012 [details] File: var_log_messages
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.