Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - synergy-1.6

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: synergy-1.6 1.6.3-1

Git Clone URL: https://aur-dev.archlinux.org/synergy-1.6.git (read-only)
Package Base: synergy-1.6
Description: Synergy upstream 1.6 branch. 1.7.x is very unstable on Linux.
Upstream URL: http://synergy-foss.org
Licenses: GPL2
Conflicts: synergy
Provides: synergy
Submitter: flavi0
Maintainer: flavi0
Last Packager: flavi0
Votes: 10
Popularity: 0.183622
First Submitted: 2015-08-12 16:42
Last Updated: 2016-06-06 23:07

Latest Comments

flavi0 commented on 2016-06-06 23:21

I added a patch which declares the destructor in question as noexcept(false). This is strictly speaking just as wrong as before, since destructors should never throw in C++ (see e.g. http://www.gotw.ca/gotw/047.htm). However I guess this will not be addressed upstream anymore, since it's actually a libcryptopp issue and I assume devs won't bother updating the 1.6.3 dependency since there's lots of pending work for 1.7. For completeness, this was not just an issue of more warnings being emitted, g++ 6 defaults to -std=g++14, and in C++11 destructors are implicitly declared noexcept.

@samueldr Thanks for reporting!

samueldr commented on 2016-05-21 18:32

The recent updates to gcc probably added more warnings, as the default build now terminates with:

.../synergy-1.6/src/synergy-1.6.3-final/src/lib/io/../../../ext/cryptopp562/algparam.h:277:34: error: throw will always call terminate() [-Werror=terminate]
throw ParameterNotUsed(m_name);

Since this was previously "fine" with earlier versions of the compiler, bypassing the warning should be fine, maybe. The error should be fixed "upstream", but this would entail doing more work, and probably understanding the codebase. For a quick fix, compilation can be changed to not treat warnings as error, just before the call to cmake:

sed -i'' 's/-Werror//' CMakeLists.txt

Or as a patch:

--- a/PKGBUILD 2016-05-21 14:26:41.618115277 -0400
+++ b/PKGBUILD 2016-05-21 14:19:42.132744548 -0400
@@ -43,6 +43,7 @@
build() {
cd $_pkgname-1.6.3-final

+ sed -i'' 's/-Werror//' CMakeLists.txt

(Alternatively, and a better alternative, would be to find out how to treat all warnings as error, except for -Werror=terminate.)

flavi0 commented on 2016-02-23 09:43

@bldewolf: thanks for notification, updated!

bldewolf commented on 2016-02-23 06:03

Their github account changed names (from synergy to symless) so the download URL needs to be updated.

flavi0 commented on 2015-10-12 14:24

In order to tunnel using ssh, you can do, instead of 'synergyc <remote>':
ssh -L24800:localhost:24800 <remote>
synergyc localhost

ceri commented on 2015-10-12 14:20

Ah that's good news. I only started using synergy with the 1.7 series and I've been experiencing those annoying hangs in regards to the clipboard too. I'm guessing it's not compatible with a 1.7 client?

I'll probably try your package. Thanks!

flavi0 commented on 2015-10-12 14:08

They switched to using openssl for all connections, and something is terribly broken, have hard to track crashes because of race conditions. Seems to be triggered by / related to clipboard and copy and pasting. No time to look up the bug tracker entries now, but it rendered the 1.7 version completely unusable to me. After much frustration and investigation, I reverted to 1.6.3 and everything was fine again. For security, you might want to tunnel the stuff using ssh!

ceri commented on 2015-10-12 14:05

What kind of instablity issues were you experiencing on 1.7.x that don't occur on 1.6.x?