Build for Arm (Raspberry Pi)

[Edward Crosby]

So a while back I was looking for the Synergy client to put on my Raspberry Pi 3. I had found the following link on the Google Groups:

http://symless.com/nightly?filter=Linux-arm

Now, that link does not seem to be valid.

Can someone point me to the updated link so that I can update to the latest on my Raspberry Pi?

Thanks.

[mace]

Bump

Help with this would be appreciated.

[Nick Bolton]

Hey, we were building unofficially for Raspberry Pi, but this was dropped. We may reintroduce it in future.

[TwinIon]

Adding a comment to support the reintroduction of a Raspberry Pi build.

[jaap aarts]

https://github.com/symless/synergy

you can try building it for yourself?

ive never tried it but might be worth looking at.

[mace]

I bought Synergy from Symless to use on my Windows 10 laptop, and my Raspberry Pi.

For the Raspberry Pi, I have tried many tutorials on how to build it from the source code and such.
The best and most current as of now, that I have been able to find, is this wiki (Install Synergy Raspberry Pi 3 - January 2017):
http://www.etcwiki.org/wiki/Install_Synergy_Raspberry_Pi_3_-_January_2017

 

However, I made A LOT of stupid mistakes and ran into issues, that looking back, I should of figured out earlier.
These are just problems I came across, how I diagnosed them, and how I fixed them.
 

Problem 1 If synergy is not connecting what-so-ever, it might be your firewall blocking

On my windows machine, I found that my Antivirus was blocking the program and my firewall was blocking connection.
Simple test to see if this is the issue for you, is for a BRIEF moment, just turning off all anti-virus and firewalls on your computer, and see if the program Synergy can connect the your computer to the Raspberry Pi and just work (like just basic mouse function going between the different screens/computers).
You'll want to turn your firewall and antivirus back on after this test.
If it did resolve the issue, make appropriate changes and rule exceptions for synergy on your security software and firewalls.

(Do be careful when doing this, as turning of your security software is not something I usually recommend.  This is also your choice and your responsible for your computer, and not me.)

 

Problem 2 if your sure problem 1 isn't it, you may of forgot to add the port number

When you type the IP address (say 192.168.1.123) make sure you add the port number onto it that your server is set to listen on (say 192.168.1.123:32123)
This is for when you get to " <synergy server ip or host name> " in the installation guide or if you start it manually.
Just check to make sure you didn't leave it out like I did

On the sever (I'm using the window's GUI) the port number can be seen and changed under the menus at the top left
    Edit -> Setting
There should be an option labeled "Port:" with a number next to it

 

Also as a side note, to run it manually:
Go to the directory you have synergy compiled at.
     cd /usr/local/bin
run the program
    ./synergyc 192.168.1.123:32123
Your IP and Port number will be different.  Check your server for this information.

Problem 3 unrecognized client

If you keep getting something that looks like this...
[2017-09-13T18:40:41] NOTE: started server, waiting for clients
[2017-09-13T18:40:41] INFO: watchdog status: ok
[2017-09-13T18:40:42] NOTE: accepted client connection
[2017-09-13T18:40:42] WARNING: unrecognised client name "raspberrypi", check server config
[2017-09-13T18:40:42] NOTE: disconnecting client "raspberrypi"
[2017-09-13T18:40:42] NOTE: client "raspberrypi" has disconnected
[2017-09-13T18:40:43] NOTE: accepted client connection
[2017-09-13T18:40:43] WARNING: unrecognised client name "raspberrypi", check server config
[2017-09-13T18:40:43] NOTE: disconnecting client "raspberrypi"
[2017-09-13T18:40:43] NOTE: client "raspberrypi" has disconnected
... and those last 4 lines keep repeating.

Go back to your server's GUI menu
Click on 'Configure Server' and pick the 'Screens and links' tab
Make sure that the screen name is set to 'raspberrypi'  OR  whatever name the Log is saying is not unrecognized
     mine had " WARNING: unrecognised client name "raspberrypi", check server config "

My pi is just name raspberrypi and I accidentally put something else for the screen name

 

These are just problems I came across, how I diagnosed them, and how I fixed them.
I hope this helps someone and that someone can learn from my mistakes  ^^;

[TwinIon]

Thanks for posting all that Mace. I did try following that same tutorial, but I haven't been able to successfully get it to build.

[DZubak]

Why don't you put the link on your help page?  (https://symless.com/synergy/help)

So you only tell people in the forum that you now only want them to use email for support but they have to log into the forum to get this message?

[mborus]

Just adding support to the idea to produce a raspberry pi build -
or at least prepare noob-safe instructions how to download, compile and set it up with the current Raspbian.

The raspberry pi with the official screen is an awesome cheap was of doing system monitoring, so having confirmed working intructions on how to use a pi with the upcoming new versions would be very helpful and a reason to test this out.would really be helpful.

[Joe Syn]

Been a few months since installed (ver 1.8 works fine ), but these are the resourses I've documented.  I think I downloaded installed Debian ver 32bit (yes it MUST !!  be 32bit - Pi is NOT 64bit ) :

https://www.raspberrypi.org/forums/viewtopic.php?t=165146

https://learn.adafruit.com/synergy-on-raspberry-pi/setup-synergy-client-autostart

MAIN INSTURCTIONS : https://www.raspberrypi.org/forums/viewtopic.php?t=165146

extract?

???DONT KNOW IF THIS WORKS : use command : sudo dpkg -i <debfile>

will get frustrated since unable to "Build" , so go to :

https://github.com/symless/synergy/wiki/Compiling#Unix_and_Linux

aka :

git clone https://github.com/symless/synergy.git

cd synergy

cmake CMakeLists.txt

make

 

not sure if this helps:

https://github.com/symless/synergy/issues/5529

 

https://www.google.com/search?q=how+to+install+symless+raspberry+pi&ie=utf-8&oe=utf-8

[Melanie_T]

*bump* Please provide a Raspi build or sources that can be built to work with a current server. The repo says it's 2.0.0 and there has just been an update so I suppose that doesn't work anymore.....

[UnixOutlaw]

On 03/04/2018 at 7:49 PM, Melanie_T said:

*bump* Please provide a Raspi build or sources that can be built to work with a current server. The repo says it's 2.0.0 and there has just been an update so I suppose that doesn't work anymore.....

and a BUMP from me too!  I bought the full Pro package - assuming there'd be binaries of BOTH 1.x and 2.x for all platforms.

I've got 1.4.16 installed (from Stretch repos) on my RPi 3b running Stretch (1.4.16 is the most recent version available via apt) - it "works" against 1.8.8 server (installed from Ubuntu repos) running on Ubuntu 18.04 (amd64)...  I say "works" because 1.8.8. kinda hates Ubuntu Bionic Beaver (constant messages about System Tray - and when it's running there's no notification icon and the only way to control it is to "pkill synergy" and run it again and wait for the  "System tray is unvailable, don't close your window." message!  One of the things I kinda "need" between the Pi and my other desktops is clipboard sharing, but it doesn't work between 1.4 and 1.8.

I also have another client machine running elementary Loki 0.4.1 - 1.8.8 I downloaded a deb file for - this works (1.6.2 from repos didn't share clipboard).

Also of note - 1.9.x downloaded from Symless wouldn't install >easily< on Ubuntu Bionic Beaver - so I'll stick with 1.8.8 for a while.

Can't you please restore the nightly builds and archives of old builds (e.g. 1.8.8 for all platforms and operating systems? - i.e. Linux on amd64, Linux on ARM, Linux on i386 and Windows on amd64 - i.e. most especially binaries/deb installers for Debian Jessie and Stretch on ARM [e.g. RPi]).

P.S.  I'm not interested in source, because frankly that's a PITA, I've done it before to get 1.7.x working on other ARM devices and never made any headway and gave up and persevered without clipboard sharing...