Description of problem: 1. start synergy (as server) on fedora 17 2. start synergy (as client) on windows 7 3. client is sucessfully connected to server 4. move mouse from server to client 5. synergy crash i have apple magic mouse and apple keyboard connected to the Fedora 17 if I disconnect Magic Mouse from computer an connect classic USB mouse: 1. start synergy (as server) on fedora 17 2. synergy crash Version-Release number of selected component: synergy-1.4.10-1 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/bin/synergys -f --no-tray --debug NOTE --name vlado-desktop -c /tmp/qt_temp.M14737 --address :24800 crash_function: operator delete kernel: 3.6.9-2.fc17.i686 truncated backtrace: :Thread no. 1 (10 frames) : #6 operator delete at ../../../../libstdc++-v3/libsupc++/del_op.cc:48 : #7 operator delete[] at ../../../../libstdc++-v3/libsupc++/del_opv.cc:33 : #8 CXWindowsScreen::updateButtons() : #9 CScreen::enable() : #10 CServer::CServer(CConfig const&, CPrimaryClient*, CScreen*) : #11 CServerApp::openServer(CConfig const&, CPrimaryClient*) : #12 CServerApp::startServer() : #13 CServerApp::startNode() : #14 CServerApp::mainLoop() : #15 standardStartupStatic(int, char**)
Created attachment 665164 [details] File: environ
Created attachment 665165 [details] File: var_log_messages
Created attachment 665166 [details] File: backtrace
Created attachment 665168 [details] File: limits
Created attachment 665169 [details] File: cgroup
Created attachment 665170 [details] File: smolt_data
Created attachment 665171 [details] File: executable
Created attachment 665172 [details] File: maps
Created attachment 665173 [details] File: dso_list
Created attachment 665174 [details] File: proc_pid_status
Created attachment 665175 [details] File: build_ids
Created attachment 665176 [details] File: open_fds
Vladimir, Where are you getting synergy-1.4.10-1 from since the manager of the synergy package on fedora doesn't seem interested in updating the package beyond 1.3.7?
synergy-1.4.10-1 I have from authors web page. I reached the same result with package synergy-1.3.7-6.fc18.i686 from Fedora's package manager
(In reply to comment #13) > Vladimir, > > Where are you getting synergy-1.4.10-1 from since the manager of the synergy > package on fedora doesn't seem interested in updating the package beyond > 1.3.7? I see it in updates for x86_64, btw. Updating: synergy x86_64 1.4.10-1.fc18 updates 384 k So it's in the repos somehow. And it's broken in more ways than this. It doesn't even show up in the system menu anymore when it updates from 1.4.9 to 1.4.10.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.