Alexander Gordon Taylor Posted October 11, 2017 Posted October 11, 2017 Hi, excited to try out beta 2, and attempting to install in OpenSUSE 42.2. A few dependencies seem to be falling over on versioning predominantly. I've installed the rpm with --nodeps, as corresponding packages for all the failed dependencies were already installed -full outputs as below. I added symlinks to existing version libraries (which I have found successful in OpenSUSE in the past for other issues): /usr/lib64/libcrypto.so.10 -> /usr/lib64/libcrypto.so.37.0.0 /usr/lib64/libssl.so.10 -> /usr/lib64/libssl.so With that done I can launch /usr/bin/synergyd without obvious visible errors from the process, however the client is reporting ERROR: Reply error message: Invalid JSON request: bad numeric conversion: negative overflow. Very happy to assist with further testing! Client Logs before symlinks added: https://synergy-logs.symless.com/2017-10-11/6199-2017-10-12T09-36-21.log Client Logs after symlinks added: https://synergy-logs.symless.com/2017-10-11/6199-2017-10-12T09-48-08.log Installation messages and relvant installed package info: # rpm -ivh synergy-2.0.0-818.beta4.042356d4.el7.centos.x86_64.rpm error: Failed dependencies: libcrypto.so.10()(64bit) is needed by synergy-2.0.0-818.beta4.042356d4.el7.centos.x86_64 libcrypto.so.10(OPENSSL_1.0.1)(64bit) is needed by synergy-2.0.0-818.beta4.042356d4.el7.centos.x86_64 libcrypto.so.10(libcrypto.so.10)(64bit) is needed by synergy-2.0.0-818.beta4.042356d4.el7.centos.x86_64 libssl.so.10()(64bit) is needed by synergy-2.0.0-818.beta4.042356d4.el7.centos.x86_64 libssl.so.10(libssl.so.10)(64bit) is needed by synergy-2.0.0-818.beta4.042356d4.el7.centos.x86_64 qt5-qtquickcontrols is needed by synergy-2.0.0-818.beta4.042356d4.el7.centos.x86_64 qt5-qtsvg is needed by synergy-2.0.0-818.beta4.042356d4.el7.centos.x86_64 # zypper search --provides libcrypto Loading repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------------+--------------------------------------------------------------------+-------- i+ | libcrypto37 | An SSL/TLS protocol implementation | package | libcrypto37-32bit | An SSL/TLS protocol implementation | package i+ | libcrypto41 | An SSL/TLS protocol implementation | package | libcrypto41-32bit | An SSL/TLS protocol implementation | package | libcryptopp-5_6_2-0 | Cryptographic Library for C++ | package | libcryptopp-5_6_2-0-32bit | Cryptographic Library for C++ | package | libcryptopp-devel | Cryptographic Library for C++ | package | libcryptopp-devel-static | Cryptographic Library for C++ | package | libopenssl-devel | Include Files and Libraries mandatory for Development | package | libopenssl0_9_8 | Secure Sockets and Transport Layer Security | package | libopenssl0_9_8-32bit | Secure Sockets and Transport Layer Security | package i+ | libopenssl1_0_0 | Secure Sockets and Transport Layer Security | package i+ | libopenssl1_0_0-32bit | Secure Sockets and Transport Layer Security | package i+ | libressl-devel | Development files for LibreSSL, an SSL/TLS protocol implementation | package i+ | openSUSE-release | openSUSE | package | syslog-ng | The new-generation syslog-daemon | package # zypper search --provides libssl Loading repository data... Reading installed packages... S | Name | Summary | Type ---+-----------------------+--------------------------------------------------------------------+-------- i+ | dovecot22 | IMAP and POP3 Server Written Primarily with Security in Mind | package | libopenssl-devel | Include Files and Libraries mandatory for Development | package | libopenssl0_9_8 | Secure Sockets and Transport Layer Security | package | libopenssl0_9_8-32bit | Secure Sockets and Transport Layer Security | package i+ | libopenssl1_0_0 | Secure Sockets and Transport Layer Security | package i+ | libopenssl1_0_0-32bit | Secure Sockets and Transport Layer Security | package i+ | libressl-devel | Development files for LibreSSL, an SSL/TLS protocol implementation | package i+ | libssl38 | An SSL/TLS protocol implementation | package | libssl38-32bit | An SSL/TLS protocol implementation | package i+ | libssl43 | An SSL/TLS protocol implementation | package | libssl43-32bit | An SSL/TLS protocol implementation | package i+ | mozilla-nss | Network Security Services | package | mozilla-nss-32bit | Network Security Services | package | mozldap | Mozilla LDAP C SDK | package | mozldap-32bit | Mozilla LDAP C SDK | package | mozldap-libs | Mozilla LDAP C SDK | package i+ | openSUSE-release | openSUSE | package # zypper search --provides qt5-qtquickcontrols Loading repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------------------+----------------------------+-------- i+ | libqt5-qtquickcontrols | Qt 5 Quick Controls Addon | package | libqt5-qtquickcontrols-examples | Qt5 quickcontrols examples | package i+ | openSUSE-release | openSUSE | package Quote
Rodney Baker Posted October 12, 2017 Posted October 12, 2017 (edited) I've had the same issues with openSuSE Tumbleweed. I symlinked libcrytpo.so.38 to libcrypto.so.10 and libssl.so.27 to libssl.so.10. Attempting to start synergy.service from systemctl fails every time (output from journalctl -x -u synergy.service below), but running it from a command line window as per the instructions on the Linux troubleshooting post have it working with one Windows 10 client connected. Here's what happens when attempting to start the service from systemd (this is all from one instance of 'systemctl start synergy.service': Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Started Synergy Service. -- Subject: Unit synergy.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished starting up. -- -- The start-up result is done. Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12920]: /usr/bin/synergyd: /usr/lib64/libcrypto.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12920]: /usr/bin/synergyd: /usr/lib64/libssl.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12920]: [2017-10-12T23:05:02] debug: service log path: /var/log/synergy-service.log Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12920]: [2017-10-12T23:05:02] info: starting service... Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12920]: terminate called after throwing an instance of 'std::runtime_error' Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12920]: what(): HOME environment variable not set Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Main process exited, code=dumped, status=6/ABRT Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Unit entered failed state. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Failed with result 'core-dump'. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Service has no hold-off time, scheduling restart. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Stopped Synergy Service. -- Subject: Unit synergy.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished shutting down. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Started Synergy Service. -- Subject: Unit synergy.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished starting up. -- -- The start-up result is done. Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12923]: /usr/bin/synergyd: /usr/lib64/libcrypto.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12923]: /usr/bin/synergyd: /usr/lib64/libssl.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12923]: [2017-10-12T23:05:02] debug: service log path: /var/log/synergy-service.log Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12923]: [2017-10-12T23:05:02] info: starting service... Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12923]: terminate called after throwing an instance of 'std::runtime_error' Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12923]: what(): HOME environment variable not set Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Main process exited, code=dumped, status=6/ABRT Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Unit entered failed state. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Failed with result 'core-dump'. Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12930]: /usr/bin/synergyd: /usr/lib64/libcrypto.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12930]: /usr/bin/synergyd: /usr/lib64/libssl.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12930]: [2017-10-12T23:05:02] debug: service log path: /var/log/synergy-service.log Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12930]: [2017-10-12T23:05:02] info: starting service... Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12930]: terminate called after throwing an instance of 'std::runtime_error' Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12930]: what(): HOME environment variable not set Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Service has no hold-off time, scheduling restart. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Stopped Synergy Service. -- Subject: Unit synergy.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished shutting down. Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12933]: /usr/bin/synergyd: /usr/lib64/libcrypto.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12933]: /usr/bin/synergyd: /usr/lib64/libssl.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12933]: [2017-10-12T23:05:02] debug: service log path: /var/log/synergy-service.log Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12933]: [2017-10-12T23:05:02] info: starting service... Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12933]: terminate called after throwing an instance of 'std::runtime_error' Oct 12 23:05:02 mako.vk5ztv.ampr.org synergyd[12933]: what(): HOME environment variable not set Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Started Synergy Service. -- Subject: Unit synergy.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished starting up. -- -- The start-up result is done. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Main process exited, code=dumped, status=6/ABRT Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Unit entered failed state. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Failed with result 'core-dump'. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Service has no hold-off time, scheduling restart. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Stopped Synergy Service. -- Subject: Unit synergy.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished shutting down. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Started Synergy Service. -- Subject: Unit synergy.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished starting up. -- -- The start-up result is done. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Main process exited, code=dumped, status=6/ABRT Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Unit entered failed state. Oct 12 23:05:03 mako.vk5ztv.ampr.org synergyd[12943]: /usr/bin/synergyd: /usr/lib64/libcrypto.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:03 mako.vk5ztv.ampr.org synergyd[12943]: /usr/bin/synergyd: /usr/lib64/libssl.so.10: no version information available (required by /usr/bin/synergyd) Oct 12 23:05:03 mako.vk5ztv.ampr.org synergyd[12943]: [2017-10-12T23:05:02] debug: service log path: /var/log/synergy-service.log Oct 12 23:05:03 mako.vk5ztv.ampr.org synergyd[12943]: [2017-10-12T23:05:02] info: starting service... Oct 12 23:05:03 mako.vk5ztv.ampr.org synergyd[12943]: terminate called after throwing an instance of 'std::runtime_error' Oct 12 23:05:03 mako.vk5ztv.ampr.org synergyd[12943]: what(): HOME environment variable not set Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Failed with result 'core-dump'. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Service has no hold-off time, scheduling restart. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Stopped Synergy Service. -- Subject: Unit synergy.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished shutting down. Oct 12 23:05:02 mako.vk5ztv.ampr.org systemd[1]: Started Synergy Service. -- Subject: Unit synergy.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished starting up. -- -- The start-up result is done. Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Main process exited, code=dumped, status=6/ABRT Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Unit entered failed state. Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Failed with result 'core-dump'. Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Service has no hold-off time, scheduling restart. Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: Stopped Synergy Service. -- Subject: Unit synergy.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has finished shutting down. Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Start request repeated too quickly. Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: Failed to start Synergy Service. -- Subject: Unit synergy.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit synergy.service has failed. -- -- The result is failed. Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Unit entered failed state. Oct 12 23:05:03 mako.vk5ztv.ampr.org systemd[1]: synergy.service: Failed with result 'core-dump'. Edited October 12, 2017 by Rodney Baker 1 Quote
Popular Post Rodney Baker Posted October 12, 2017 Popular Post Posted October 12, 2017 OK - I now have it starting from systemd; following a hint in another post, I first added an override in the [service] section of the systemd unit file to set Environment=HOME=/root. I then created /root/.config/synergy and symlinked synergy.conf to my user's ~/.config/synergy/synergy.conf, but this didn't work. The service started OK but the connection was never established. I modified the line in the systemd unit file to Environment=HOME=/home/<my_user>, did systemctl daemon-reload and restarted the service, and it works! Win 10 client is connected and the openSuSE box's keyboard and mouse are being shared successfully. 1 1 Quote
jaap aarts Posted October 12, 2017 Posted October 12, 2017 14 minutes ago, Rodney Baker said: I modified the line in the systemd unit file to Environment=HOME=/home/<my_user>, did systemctl daemon-reload and restarted the service, and it works! Win 10 client is connected and the openSuSE box's keyboard and mouse are being shared successfully. the beta4 is really unreliable, so just simply restart might have done the job the same way. Quote
Rodney Baker Posted October 12, 2017 Posted October 12, 2017 12 minutes ago, jaap aarts said: the beta4 is really unreliable, so just simply restart might have done the job the same way. I tried that, but unfortunately it didn't. Now that it's working, performance seems (subjectively) smoother/faster/less resource intensive on the Win 10 Tablet than 1.88. The machines are on 2 different subnets - that wasn't officially supported on 1.88, but it worked with an avahi reflector proxying bonjour info between subnets, so it did work. I'm guessing that 2.0 doesn't use avahi/bonjour, so it takes that overhead out of the way. Of course, I could be completely wrong about that, too... 1 Quote
jaap aarts Posted October 12, 2017 Posted October 12, 2017 1 hour ago, Rodney Baker said: Oct 12 23:05:03 mako.vk5ztv.ampr.org synergyd[12943]: what(): HOME environment variable not set have you don this:? read a bit futher and you'll find who to properly start the service without it crashing Quote
Rodney Baker Posted October 12, 2017 Posted October 12, 2017 Yes, but rather than run /bin/env, my systemd unit file now looks like this: [Unit] Description=Synergy Service After=network.target [Service] Type=simple Restart=always RestartSec=5 SyslogLevel=err ExecStart=/usr/bin/synergyd Environment=HOME=/home/<my_username> [Install] WantedBy=multi-user.target Where <my_username> above is a placeholder for my actual username. I upped RestartSec to 5 to avoid the errors I was seeing with the service trying to restart too quickly after a failure (mind you, since it's been starting properly it probably hasn't needed that parameter). Both methods are correct - I find this one easier to read, even if it is an extra line of config. I guess it's really down to personal preference. 1 Quote
Alexander Gordon Taylor Posted October 12, 2017 Author Posted October 12, 2017 6 hours ago, Rodney Baker said: Yes, but rather than run /bin/env, my systemd unit file now looks like this: [Unit] Description=Synergy Service After=network.target [Service] Type=simple Restart=always RestartSec=5 SyslogLevel=err ExecStart=/usr/bin/synergyd Environment=HOME=/home/<my_username> [Install] WantedBy=multi-user.target Where <my_username> above is a placeholder for my actual username. I upped RestartSec to 5 to avoid the errors I was seeing with the service trying to restart too quickly after a failure (mind you, since it's been starting properly it probably hasn't needed that parameter). Both methods are correct - I find this one easier to read, even if it is an extra line of config. I guess it's really down to personal preference. Thanks, I am now successfully running, though I did have to alter the symlink from Nick's recommendation, from ln -s ~/.config/Symless/Synergy/synergy.conf ~/.config/synergy/synergy.conf to ln -s ~/.config/Symless/Synergy.conf ~/.config/synergy/synergy.conf ...as the target wasn't as Nick suggested. So at this point my OpenSUSE installation in successful, and I can see and move other screens in the config window. It's not working reliably for me, but I'll put that feedback somewhere more relevant, as the installation issue is solved. 1 Quote
Synergy Team Nick Bolton Posted November 2, 2017 Synergy Team Posted November 2, 2017 Official openSUSE support is coming soon. Thanks for your patience! 1 Quote
jaap aarts Posted November 4, 2017 Posted November 4, 2017 this was a common problem in beta4, try rc1 and see what happens. Quote
Synergy Team Nick Bolton Posted November 4, 2017 Synergy Team Posted November 4, 2017 2 hours ago, jaap aarts said: this was a common problem in beta4, try rc1 and see what happens. 2.0 won't support openSUSE, but it's coming soon. Quote
DanS Posted April 7, 2018 Posted April 7, 2018 I upgraded to Synergy 2 and didnt realize it didnt support openSUSE - and was a bit disappointed. I guess I should have checked first.... Thanks so much to Rodney Baker - his posts/instructions got it working for me!!! Massive kudos to you Rodney! Thanks again! Quote
Synergy Team Nick Bolton Posted April 11, 2018 Synergy Team Posted April 11, 2018 On 4/7/2018 at 4:24 AM, DanS said: I upgraded to Synergy 2 and didnt realize it didnt support openSUSE Sorry about that, we do plan to add openSUSE support, thanks for your patience. 1 Quote
Rodney Baker Posted April 28, 2018 Posted April 28, 2018 Still waiting...it hasn't been working for me since around 2.0.4. Looks like I wasted my money on 2.0. openSuSE support isn't even mentioned in the roadmap - how long should we be patient for, Nick? 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.