Description of problem: Using 'synergys --debug WARNING' to start the server errors out with "Synergy 1.13.1: [2021-09-13T15:43:27] FATAL: unknown screen name `valid-hostname`". With 'valid-hostname' being the hostname of the server (aka localhost) Now I know 'valid-hostname' is valid because host 'valid-hostname' gives the valid ip and host 'valid-ip' gives the valid hostname. Plus ping 'valid-hostname' works as well. One caveat... Neither 'valid-hostname' or 'valid-ip' are in the defined in the DNS server... They are only defined in /etc/hosts. Version-Release number of selected component (if applicable): synergy-1.13.1.41-2.fc34.x86_64 How reproducible: use synergys Steps to Reproduce: 1. Define the local hostname (aka the synergy server) only in /etc/hosts not in the DNS server which is defined in /etc/resolv.conf which is the systemd-resolved daemon in F34 1. start synergys --debug WARNING Actual results: synergys fails but does not exit Expected results: To work. Additional info:
Note... The problem goes away when I downgrade to synergy-1.12.0-2.fc34
There is now an update to synergy. I don't know if this fixes the issue, please test. Does the output of `hostname` match the configured host name in synergy? 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
(In reply to David Kaufmann from comment #2) > There is now an update to synergy. I don't know if this fixes the issue, > please test. Fixes the problem for me! > > Does the output of `hostname` match the configured host name in synergy? Yes hostname matches both the server hosts in the screeens and links sections. > > 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 Thank you!
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.