New version of synergy is released.
Really need to get this bumped, 1.7.3 is the WORST version of synergy ever! No clue what is going on but to many times daily synergys and synergyc lose sync or something. I have to kill and restart one or the other, sometimes both. I NEVER had this problem with any prior version of synergy. Really wish 1.7.1 was left in tree as 1.7.3 is very unstable. I have ran synergy many years without issues like I am experiencing many times a day...
1.7.4 is in the tree.
Thank you very much!
I can run this as the server, as long as I tell the client to disable SSL encryption. Runnign the server with nothing special: synergys --config ~/.synergy.conf --daemon --plugin-dir ~/.synergy/plugins my ~/.synergy/plugins contains libns.so, which I downloaded from the synergy site. ldd ~/.synergy/plugins/libns.so |grep 'not found' libssl.so.10 => not found libcrypto.so.10 => not found https://github.com/synergy/synergy/issues/4890 says I need to hack symlinks. ln -s /usr/lib64/libcrypto.so.0.9.8 /usr/lib64/libcrypto.so.10 ln -s /usr/lib64/libssl.so.0.9.8 /usr/lib64/libssl.so.10 This allows ssl to work but it makes me feel dirty. Is there some way to build libns.so against the system libs as part of the install?
(In reply to John Stile from comment #4) > I can run this as the server, as long as I tell the client to disable SSL > encryption. That's bug #550692.