Description of problem: Synergy hasn't been updated for quite a while. Let's of performance and stability updates in newest "beta" version. Version-Release number of selected component (if applicable): 1.3.7 -> 1.4.9 The beta is barely beta. In fact it is the only released listed on their download page. To get to the "stable" releases you have to drill down into "alternate downloads". Please consider pushing updated release to F16/F17. Thanks! Joel
Note that this upgrade should fix https://bugzilla.redhat.com/show_bug.cgi?id=749025
Note that 1.4.10 is released now (and for a long time) as well as 1.3.8 on the stable branch. Any chance an update for this can go out? Thanks!
Bump!
synergy-1.4.10-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/synergy-1.4.10-1.fc18
synergy-1.4.10-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/synergy-1.4.10-1.fc17
Thanks folks! Looks good. Joel
Package synergy-1.4.10-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing synergy-1.4.10-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2792/synergy-1.4.10-1.fc17 then log in and leave karma (feedback).
synergy-1.4.10-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Would it be possible to push this version on to the RHEL6 epel branch, since 1.3 and 1.4 are not compatible?
Just noticed this incompatibility when trying to connect F17 and F18 since 1.4.10-1.fc17 is still in updates-testing (as per [comment 7] as per comments in Bodhi, it seems this is status quo) and hence the default is ~1.3.7-5.fc17. BTW., the incompatibility may be only partial: server\client| 1.3.7-5.fc17 | 1.4.10-1.fc18 -------------+--------------+-------------- 1.3.7-5.fc17 | (should) | NO (client-side diagnostics) -------------+--------------+-------------- 1.4.10-1.fc* | YES | YES So if possible, one can use a roles swap as a workaround.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Synergy is now at 1.4.10 in fc20. It is now out of date again by several versions. 1.4.14 is current and 1.4.15 is in beta. Also, there are a bunch of synergy abrt bugs that aren't from the fedora synergy package. These should be closed? I am closing this bug (as reporter).
re [comment 10]: With the recent 1.4.* -> 1.6.* update in Fedora 21, I've just noticed that 1.6.* client cannot connect to 1.4.* server.
(In reply to Jan Pokorný from comment #13) > re [comment 10]: > > With the recent 1.4.* -> 1.6.* update in Fedora 21, I've just noticed > that 1.6.* client cannot connect to 1.4.* server. It's a bummer that upstream synergy didn't cater to this situation. Basically, they state: client server status 1.4.* 1.4.* supported 1.4.* 1.6.* supported 1.6.* 1.4.* broken 1.6.* 1.6.* supported so as long as your server is at least as new as your newest client, you are okay; old clients are okay (the mismatch is only when the server is older). I was also quite bummed that this upgrade broke my setup (F21 server, rawhide client); my workaround was to install the rawhide synergy package on the Fedora 21 box.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days