Arch Linux User Repository

@jholbrook you can fix this with the same fix from @brianc

for some reason I can't do sudo echo "distrib_release=99.0" >> /etc/arch-release I get permission denied....

but editing the /etc/arch-release with vim works fine. for some reason that file got truncated, and it was empty. adding the content fixed the issue

Any chance of getting an update to 3.2.1?

There's a bug in 3.2.0 where you can't open GUI and you only get the Wayland error message. This is fixed in 3.2.1.

Thanks.

I'm not a linux pro so I got lost at first. Hope this helps someone.

Run /opt/Synergy/synergy to open the GUI. Press ignore whenever an error pops up (it's related to OS version not getting detected properly, which doesn't matter as far as I can tell). Configure any way you like. Make sure the correct computer has the keyboard/mouse (you can change it under "Manage computers" menu by clicking the 3 dots right next to the computer you want to be the server and click "Keyboard and mouse computer").

At this point Synergy should work as expected. If it doesn't work check the logs in GUI and .local/state/Synergy/synergy.log. Don't continue to the next steps until Synergy works properly.

Quit GUI. Kill the synergy-service process.

GUI is no longer needed unless you need to configure something from the GUI. So you can just remove ~/.config/synergy/ directory (note the lowercase "s"). Don't remove the ~/.config/Synergy/ directory (note the uppercase "S")

Now all you need is to run /opt/Synergy/synergy-service which you can either do directly or via a user unit systemctl --user enable --now synergy.service.

I had some issues with this package, when installing. UI was loading, I was able to detect other machines, but for some reason, mouse was not moving between laptops.

Runing the "Diagnostic Tool" on Troubleshooting section it showed that Synergy-core was not running and logs were not saying anything usefull. So when I tried to run synergy-core manually, some qt library was missing. I fixed it installing qt5-tools (https://archlinux.org/packages/extra/x86_64/qt5-tools/)

command to run synergy-core manually, if you are having the same issue is: /opt/Synergy/synergy-core server -f --ipc -c /home/[username]/.config/Synergy/synergy.conf --serial-key xxxxxx --name [machine-name] --enable-crypto --tls-cert /home/[username]/.config/Synergy/synergyCert.pem --debug DEBUG1 --address 0.0.0.0:24800

amazing work done here, but for some reason when I install this package, I get the beta version installed.

my bad, for some reason I got the version pointing the beta on my user cache folder. I just removed it and got the correct one. problems for being an arch newbie

I agree that this package should be used for the stable versions of Synergy 3, so I'll be making a new package synergy3-beta-bin. I'll be reverting this version to the RC3 and we can ask @jonstelly's package to be merged with this one.

The beta version can be found in this new package: https://aur.archlinux.org/packages/synergy3-beta-bin

Sadly, it is not starting the service for me and I can't find the cause:

Started Synergy 3 Service.
Pkg: Error reading from file.

Yeah, I felt like the stable-bin package name was a bit strange or not the aur-norm at least. I'd be happy to retire that package if it makes more sense to retarget this package at stable builds and have a separate beta package, I was just looking for the quick fix.

I was just coming here to comment that this package should probably be synergy3-bin-beta as it's packaging the latest beta version. While this isn't necessarily a problem on its own, the beta and stable versions of Synergy3 are incompatible. I was having no luck connecting with my mac with what looked like the "latest version" from the Synergy site until I realized the version mismatch. Once I updated my mac to the beta, things worked instantly.

I was having some issues with the 3.1 beta so I spun up a separate package, synergy3-stable-bin. Plan is to stick to GA builds (and RC builds of 3.0 until that GAs) to give people a stable option or fallback, just figured I'd mention it here.