Known Bugs in Synergy 2 with Workarounds

Did You Find a Bug?

If you think you've found a bug, please contact our support team who'll be more than happy to help you out. Opening a support ticket will also provide us with vital technical information which is useful to our development team for fixing these bugs!

List of Known Bugs

Background service or network layer gets into a bad state

We introduced a new background service and local network layer in Synergy 2. So far this is actually where most of the new bugs have come from. The new background service and network layer wrap the older core component, providing: cross-platform auto-start in the background, modern SSL network encryption (more secure than our legacy SSL implementation), two-way connection topology (helps with firewalls and tricky networks), and the ability to share control from any computer on the fly (also known as bi-directional sharing). With all this new code, there are bugs in the background service and network layer where either can get into a bad state. We have identified and fixed many of the bugs since the November 2017 launch, but there are still a few issues that we're working on.

Workaround: Restart the background service (on all computers)

Working computers sometimes show offline

When a computer is green, that means Synergy 2 is working (it's online). When it's gray, that means that it's offline (it's either disabled, or the machine is turned off). There's also a 3rd status; connecting, which shows when Synergy 2 is trying to connect to another computer. There is a known bug where sometimes, even though a computer is actually connected, it'll show as either offline or connecting. We're aware of this bug and are gradually fixing the problem. It's caused by a race condition, in case you were curious.

Workaround: There's nothing you really need to do here since the computer is actually connected (assuming this is the case), but if it's bugging you then you can always re-arrange your screens or enable and disable a computer, or reboot your machine (but it's really not necessary).

IP address changes aren't detected

When moving between work and home, your IP address changes. That's the most obvious cause. But there are other more innocuous things to blame for an IP change; getting a little technical here, but what about when your computer is asleep for a while? Often, the DHCP lease can expire (it's the system that assigns IP addresses), and your IP address is handed out to someone else. In this case, even if they're another Synergy 2 user, the connection will be refused and no connection will be made. The lack of IP change handling is actually more like a missing feature, but it sure feels like a bug. In either case, this is something we'll be fixing very soon. It's also driving us nuts here at Symless.

Workaround: Restart the background service (on all computers)

File Drag & Drop is broken

You can also find this one on the Synergy 2 roadmap. We introduced file Drag & Drop (the ability to drag and drop files between computers) in Synergy 1.6, and while it was only available between macOS and Windows, it worked most of the time (but wasn't very reliable). Sadly, Synergy 2 was the nail in the coffin for this feature, and it stopped working entirely. Our short-term plan is to get this up and running again in Synergy 2, but a longer-term plan consists of making it much more robust, and of course adding file copy paste (right-click a file, copy, then paste the file on another computer).

Workaround: Sorry, no real workarounds yet. The only thing you can do is use traditional file sharing, which is far from seamless, we know.

Auto-switch to Linux server is broken

This is down to the delayed Wayland support. Essentially, to fix this, we have to re-write a huge chunk of code on Linux, and it'll take us some time. Even using Xorg as your display using manager won't help.

Workaround: Right-click the Linux computer you want to share from (in the Synergy 2 config app) and select Share from.

Linux client can randomly take/lose control

Sometimes when you're using Linux as your secondary computer (i.e. sharing to that computer rather than from it), it'll randomly grab control. We think this is down to Xorg randomly inserting keypress events into the event loop which aren't identifiable as faked key presses. This is related to the broken auto-switch bug, again down to lack of Wayland support. When we add Wayland support, it should fix both this issue and the broken Linux auto-switch issue.

Workaround: Auto-switch back to the main computer by clicking or pressing a key. Yes, we know, it's very frustrating when this happens.

Other Known Bugs

Workarounds coming very soon...

  • Alt+Gr doesn't work for some users
  • Mouse scroll may sometimes stop working
  • Clicks on Windows clients may stop working
  • Clipboard sharing sometimes stops working
  • Modifier keys (Shift/Ctrl/Alt/Win) not working in Parallels
  • Some keys don't work on some i10n keyboard layouts
  • Computer may be prevented from sleeping in some scenarios
  • Ctrl+Alt+Del emulation with Ctrl+Alt+Pause is not working