Leaderboard

Able to install, and see that both machines are connected, but cannot move mouse across machine boundary. Logs: MAC https://synergy-logs.symless.com/2017-09-21/850-2017-09-21T11-24-05.log Win10 https://synergy-logs.symless.com/2017-09-21/850-2017-09-21T11-23-54.log

Would be nice to have some sort of advanced user option that would give you access to the config similar to 1.8. There are some machines I would like to bypass the auto discovery on and point them directly to a server. (Split Tunneling reasons)

Support asked me to post these first impressions having moved to the 2.0.0-beta4 from 1.8.x First off this doesn't feel like beta software. I've been used to Synergy working reliably for a number of years. I was expecting more of the same here but it seems more like an Alpha at best. I quite understand that you are making big changes but the Beta moniker doesn't really describe the experience at the moment. I don't like the fact that Synergy needs to connect to your servers to configure itself. Why can't we just put a licence code in like other software? Odds are that at some point

Hi, I intentionally blocked outbound access to beta app, and it died... I suppose you must handle exception gracefully...

That's great regarding the start/stop button. I would just like it by default to connect when the software starts up but then you can click like a stop or pause button to just make Synergy disconnect from your other computers until you start or unpause it. Also I wasn't aware of the Scroll Lock thing, good to know. Also you guys will be offering the ability to customise keys and things? I always remap the CMD key to CTRL for my Mac so I can use CTRL + C and CTRL+ V instead of Super + C and Super + V. It's just more natural for me since I'm using my PC keyboard to type to my Mac to keep th

It is performed by NAT yes. New connections use one of the load balanced internet connections at random. Traffic destined for the same port as the packets went out to come back properly to the same IP. So all services, games, websites all work. Just every brand new request (like a new page refresh) uses a randomised connection to the internet. At work we have three. This is all done on the pfSense router at work and not done on our local machines. But it can cause issues with authentication schemes that require the IP to be the same. To be honest since the site is using HTTPS I don't thin

Yep. That pretty much describes my situation as well. Is there any actual documentation for this beta?

Are you certain Scroll lock is off on the Windows system. If on that would keep it stuck at the barrier like that.

Hi Nick! I have to say, as a Synergy user since 2011, I also jumped to purchase Synergy 2 for the $5 as soon as I saw your e-mail. I would like to mention that I truly appreciate the way you are going about this and although I initially thought that I would like a refund, I respect what you are doing and I would love to support you in any way. With that being said, I don't feel the need to request a refund. Although, I can't seem to get the Synergy 2.0 Beta to work. Hmm. I'll keep using 1.8 for now! Cheers,

I wanted to test 2.0beta, but I can't get any access.. I assume it's due to one of the machines are on a split tunnel vpn. Let's please have some way of adding an interface or IP address to select how to access it. Martin

As a note for Ubuntu users: The env command is not located in /bin, but /usr/bin, so the line in the service config should probably read: ExecStart=/usr/bin/env HOME=/home/<username> /usr/bin/synergyd Finally - at least on my ubuntu 17.04, the systemctl reload command to be used is: systemctl daemon-reload Unfortunately the patch described above did not work for me. The service core-dumps on sttartup from systemctl. It works when running manually from the command line as root, though Reading the log with journalctl -u synergy I noticed that the HOME variabl

They've responded to my email, but we're still in the process of investigating it. If ever they do find fix, I'll post it here. On the other hand, if I find some workaround, I'll post it here as well. Oddly enough, I tried the latest install again, and I'm not experiencing disconnections. I still experience lagging though. Though if anyone can, it would help the devs if we get logs off the machines with client disconnects / lags. I'm trying to get logs now so they could find out what's wrong. Unfortunately (or fortunately?), I'm not experiencing the client disconnects as before, so I can'

Editing the config and restarting the service worked for me. Thanks jaap aarts

Perhaps you could have the package create a synergy user and group, and then users that are a member of said group can fire up the manager app and use it (along with the Synergy functionality itself)?

I'm OK with it. This is part of the fun being in a beta testing program. Looking forward to beta 5

I really can't wait for beta5.

If it gives no output it should have worked. The instructions I gave you might have been wrong: If you want to run /usr/lib/synergyd manualy you can undo the changes or execute: systemctl disable synergy systemctl stop synergy But this will mean you will have to enable it again when this gets fixed in an update

Me too. The install won't let us re-install beta3. I'd rather not back down to 1.8.

The biggest worry I have is Synergy not being able to work on a closed network. Having to phone home really takes away from the product.

IMO, you're doing it backwards. Automatic/JFW/IdiotMode/Whatever should be done last, not first. Stabilize the product then turn on autopilot. As stated many times, it's beta software. And as you are finding out, it is not easy, and frustrating for us, to troubleshoot a blackbox. Many (most) of us are techies and are happy to be guinea pigs, but you aren't making our jobs of testing any easier if we don't know what's going on. There's no documentation, no instructions, just "install it, trust us!". Heck I didn't even know it phoned home for registration until it did it. Naughty naughty

Hello, I recently purchased Synergy and have been attempting to set it up with no luck. My server computer is a Windows 10 machine with 1.9 rc3 installed trying to be linked to a macOS Sierra machine with 1.9 rc3 installed for the client. They are both connecting via wireless network. I initially had the 1.8.8 version installed but they were failing to link together. I read through the forums and found multiple suggestions to install 1.9 rc3 to resolve issues so I installed it on the Windows 10 machine and now it attempts to install Bonjour, downloads the file, the UAC prompt comes up whe

Is there a 32-bit version of 1.9.0 for windows 10?