There have been several new upstream releases of "synergy" since the last Fedora build; most recently 1.13.1.41 ( https://github.com/symless/synergy-core/releases/tag/1.13.1.41-stable )
FEDORA-2021-1d86c5a47e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1d86c5a47e
thanks, should be in the repos soon.
FEDORA-2021-1d86c5a47e has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1d86c5a47e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1d86c5a47e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thanks. Would you consider an update also on the Fedora 33 branch?
maybe - but I'm not sure if this is just a feature update, which is discouraged on stable releases. are there reasons to push it to f33 anyway (e.g. major bugfixes)?
Just updated to this 1.13 version. After reboot Synergy pop'ed up a window asking for a serial key. I've seen that before, but it could just be closed again. Now, if closing it - server isn't started, and pressing the start button immidiately pops the same registration window up again. In other words - pay the ransom to symless, or the app doesn't work. Not sure if this is some new standard in Fedoras repos ?? Anyway, downgrading to 1.12 makes it work again.
yes, I didn't catch that - I did see the nagging screen, but only when starting the app. The command line version (synergys) still works - because of this I didn't see it. This change seems to have been intentional - I've found a closed bug[1] where this is stated. There is a command line flag I can use, I've asked them if they are ok with it - I'll wait for a response for some time, but if I don't get a response I'll just add that as a bugfix. [1] https://github.com/symless/synergy-core/issues/6866
FEDORA-2021-1d86c5a47e has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
Reopening the bug, because the issue is not solved completely, despite the new version being pushed out already.
Upstream recommends to downgrade again to 1.12.2 - there will be a new community version, but not in the near future. Is this an acceptable solution?
Fine by me
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
we need to get this issue fixed. Either downgrade it to a working version, or use that compile flag as others recommended. It is very annoying that this is still an issue on F34-F35-F36
There is now an update to synergy which should fix this issue, please test. Updates: rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5b7d0a496c f35: https://bodhi.fedoraproject.org/updates/FEDORA-2021-59ae27a60d f34: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c912534263
Finally. Tested F34 and rawhide as client - now works great again. Thank you. Karma left for F34.
FEDORA-2022-b909ed9ffa has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b909ed9ffa
FEDORA-2022-93dd848978 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-93dd848978
FEDORA-2022-3f79c71403 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3f79c71403
FEDORA-2022-93dd848978 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-93dd848978` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-93dd848978 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b909ed9ffa has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b909ed9ffa` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b909ed9ffa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-3f79c71403 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-3f79c71403` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3f79c71403 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b909ed9ffa has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-3f79c71403 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-93dd848978 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.