Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Synergy 3 RC1 is here!


Recommended Posts

Alexey Smirnov

Yes! I've tried it!!! Very nice app!!! Thank you very much!

There is one problem: If I try to change language with alt+shift at my Ubuntu (left display) when my mouse is at right display (Win), language is not changes.

  • Thanks 1
Link to post
Share on other sites
Kris Dekeyser

Unfortunately I still have the same problem as with the beta versions: the synergy service does not start automatically on my xubuntu 22.04 PCs. This is the output from 'journalctl -xeu synergy.service':

mei 31 21:24:03 beast systemd[1]: Starting Synergy 3 Login service...
â–‘â–‘ Subject: A start job for unit synergy.service has begun execution
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
░░ 
â–‘â–‘ A start job for unit synergy.service has begun execution.
░░ 
â–‘â–‘ The job identifier is 2421.
mei 31 21:25:33 beast systemd[1]: synergy.service: start-pre operation timed out. Terminating.
mei 31 21:25:33 beast systemd[1]: synergy.service: Control process exited, code=killed, status=15/TERM
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
░░ 
â–‘â–‘ An ExecStartPre= process belonging to unit synergy.service has exited.
░░ 
â–‘â–‘ The process' exit code is 'killed' and its exit status is 15.
mei 31 21:25:33 beast systemd[1]: synergy.service: Failed with result 'timeout'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
░░ 
â–‘â–‘ The unit synergy.service has entered the 'failed' state with result 'timeout'.
mei 31 21:25:33 beast systemd[1]: Failed to start Synergy 3 Login service.
â–‘â–‘ Subject: A start job for unit synergy.service has failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
░░ 
â–‘â–‘ A start job for unit synergy.service has finished with a failure.
░░ 
â–‘â–‘ The job identifier is 2421 and the job result is failed.

Link to post
Share on other sites

Just like the beta, I can't get this working at all on MacOS Ventura 13.4 (Intel).

Connection to the background service running
locally on your computer timed out,
please contact support.

Diagnostic tool:

Checking binary Synergy ... OK
Checking binary synergy-core ... OK
Checking binary synergy-service ... OK
Checking binary synergy-tray ... OK
Checking process: synergy-core ... FAIL
 Reason: Process synergy-core not running
Checking service "com.symless.synergy3" ... FAIL
 Reason: Service "com.symless.synergy3" is not installed
Ping synergy-service ... FAIL
 Reason: Fail to ping synergy-service http://127.0.0.1:24802/ping
Checking db structure for /Users/username/Library/Preferences/Synergy/db.json ... FAIL
 Reason: /Users/username/Library/Preferences/Synergy/db.json doesn't exist
Checking db structure for /Users/username/Library/Preferences/Synergy/local.json ... FAIL
 Reason: /Users/username/Library/Preferences/Synergy/local.json doesn't exist
Checking accessibility permissions ... FAIL
 Reason: error sending request for url (http://127.0.0.1:24803/v1/settings): error trying to connect: tcp connect error: Connection refused (os error 61)
Creating report ... 
File /Users/username/Library/Logs/Synergy/synergy.log.old doesn't exist
File /Users/username/Library/Preferences/Synergy/db.json doesn't exist
File /Users/username/Library/Preferences/Synergy/local.json doesn't exist
File /Users/username/Library/Preferences/Synergy/synergy.conf doesn't exist
Report is saved into: /Users/username/Documents/synergy-diagnostic.zip
Diagnostic finished

 

Any suggestions would be appreciated. 

  • Sad 1
Link to post
Share on other sites

Hi, just tried the new version and I got the same error @Marbro described.

The only difference are:

- I am on macOS Monterey

- Synergy 3 works after a fresh install but fails once computer is restarted

Link to post
Share on other sites
Lee Anderson
7 hours ago, Monti said:

How do you update the licence in RC1 in Mac?

This worked for me:

 

  1. In the top left menu, go to Synergy>About>Update serial key
  2. Select either; "Update using Symless account" or "Update manually using serial key"
  3. Enter either login details or serial key
  4. Choose update this computer
  5. Repeat above steps for each computer
  • Thanks 1
Link to post
Share on other sites
58 minutes ago, Lee Anderson said:

This worked for me:

 

  1. In the top left menu, go to Synergy>About>Update serial key
  2. Select either; "Update using Symless account" or "Update manually using serial key"
  3. Enter either login details or serial key
  4. Choose update this computer
  5. Repeat above steps for each computer

That works for windows, in Mac there is not an about menu that i can see. I fixed it by resetting all settings, so the next time it started it popped out with a message to insert the serial or sign in.

Link to post
Share on other sites
IT Troll
1 hour ago, Lee Anderson said:

Repeat above steps for each computer

Or you can choose to update all from one.

  • Like 1
Link to post
Share on other sites
Alec Bell

I downloaded the Windows version (synergy-win_x64-v3.0.72.1-rc1.msi, 120,926,208 bytes).
I get "This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package."
Windows Installer service was not running, so I started it, but I get the same result.

Running Windows 11 22H2 (OS Build 22631.1830)

Apologies if I missed anything else I should have done.

Link to post
Share on other sites

I have a server (Windows 10) and my client is MorphOS

The client is running (old software version, since I can't see where the update it) and is trying to connect.
I've disabled security on both.
In the logs on the Windows 10 server, i keep seeing:
synergy-core [2023-06-04T14:58:18] - WARNING - unrecognised client name "MorphOS", check server config

I can't seem to add the MorphOS (Mac Mini G4) by IP or by Hostname. It keeps saying: Connection Failed.
My network is Ethernet

Link to post
Share on other sites
On 6/1/2023 at 7:56 AM, Marbro said:

Just like the beta, I can't get this working at all on MacOS Ventura 13.4 (Intel).

Connection to the background service running
locally on your computer timed out,
please contact support.

Diagnostic tool:


Checking binary Synergy ... OK
Checking binary synergy-core ... OK
Checking binary synergy-service ... OK
Checking binary synergy-tray ... OK
Checking process: synergy-core ... FAIL
 Reason: Process synergy-core not running
Checking service "com.symless.synergy3" ... FAIL
 Reason: Service "com.symless.synergy3" is not installed
Ping synergy-service ... FAIL
 Reason: Fail to ping synergy-service http://127.0.0.1:24802/ping
Checking db structure for /Users/username/Library/Preferences/Synergy/db.json ... FAIL
 Reason: /Users/username/Library/Preferences/Synergy/db.json doesn't exist
Checking db structure for /Users/username/Library/Preferences/Synergy/local.json ... FAIL
 Reason: /Users/username/Library/Preferences/Synergy/local.json doesn't exist
Checking accessibility permissions ... FAIL
 Reason: error sending request for url (http://127.0.0.1:24803/v1/settings): error trying to connect: tcp connect error: Connection refused (os error 61)
Creating report ... 
File /Users/username/Library/Logs/Synergy/synergy.log.old doesn't exist
File /Users/username/Library/Preferences/Synergy/db.json doesn't exist
File /Users/username/Library/Preferences/Synergy/local.json doesn't exist
File /Users/username/Library/Preferences/Synergy/synergy.conf doesn't exist
Report is saved into: /Users/username/Documents/synergy-diagnostic.zip
Diagnostic finished

I get the same message.  Noticed that Ventura is not supported.  They should have made that clearer on their website, as most mac users are likely to be using the latest OS.   I need to figure out how to retrieve the previous version.

 

On 6/1/2023 at 7:56 AM, Marbro said:

Any suggestions would be appreciated. 

 

  • Like 1
Link to post
Share on other sites

Looks pretty nice, however, is there anyway to make it start in the background? Kinda annoying to have a big, white, unneeded window pop up every time I start any of my computers.

  • Like 1
Link to post
Share on other sites
charleshb

Hey,

Long time user of Synergy, an early adopter even, but first time here in the forum.

Just upgraded to Synergy 3 as I was prompted to download the latest version, which is something I have done for years.

So years later, and how many years is making me feel a tad old, and a bit nostalgic, I am puzzled.

I have an number of computers dotted around, and currently have two pairs working together in two locations, which is quite conservative, for me.
In the past this was not an issue Synergy worked with the paired computers, I sat down it was like I had one machine, I didn't have to do a thing.

So far a day into Synergy 3, I have to remember to go to the interface and change the active computer.

This after years of doing the same thing, and not thinking about it, came as a rude shock.

So what am I missing? 

Or is this downgrade something I am going to have live with?

  • Like 1
Link to post
Share on other sites

I am loving this new version of synergy, although I have one issue I can't seem to wrap my head around. 

In the BETA I was able to unlock my m1 mac from my windows as the host, now with the new rc1 version, it no longer works. The settings are checked to have the ability to unlock my mac and synergy is still in the login items under system preferences. 
I am stumped, anyone else having this issue/know a fix?
 

Keep up the great work Symless.

  • Thanks 1
Link to post
Share on other sites
Disappointed
On 6/2/2023 at 10:48 AM, JJC said:

Will Synergy 3 support Wayland on Linux?

It was claimed it was too much work for Synergy 1 so we would have to wait 4+ years for Synergy 3. 

Yet here we are, still nothing.   Frankly I'm not surprised. 

 

Link to post
Share on other sites
  • 1 month later...
  • Synergy Team
Nick Bolton

Thanks for your patience everyone, we've been working away furiously on RC2, which has been released today!

On 6/5/2023 at 10:33 PM, charleshb said:

In the past this was not an issue Synergy worked with the paired computers, I sat down it was like I had one machine, I didn't have to do a thing.

So far a day into Synergy 3, I have to remember to go to the interface and change the active computer.

Ah, do you run separate Synergy configs? If so,  we have a feature planned called profiles that'll let you split out your Synergy setups into different configs in Synergy 3, like you could in Synergy 1.

For now, you can continue using Synergy 1 as this is still supported (and will be until 2028).

On 6/7/2023 at 3:25 AM, Xygnal said:
On 6/2/2023 at 4:48 PM, JJC said:

Will Synergy 3 support Wayland on Linux?

It was claimed it was too much work for Synergy 1 so we would have to wait 4+ years for Synergy 3. 

Yet here we are, still nothing.   Frankly I'm not surprised. 

Ah, check out the Synergy roadmap. Not sure what you mean by "too much work for Synergy 1" but, we'll be supporting Wayland in both Synergy 1 and Synergy 3.

Quote

Sadly, as of 2023, Wayland is incompatible with Synergy. Thankfully, it is possible to easily switch back to X on most Linux distros, but not everyone wants to go back to X, as they prefer the new features in Wayland. Right now, many people have to choose: Synergy or Wayland. A lot of people are very unhappy about this.

Since Wayland is the way forward and X is being phased out, we are committed to doing everything we can to make Synergy work with Wayland. But, this depends on Wayland. Wayland needs to actually add support for apps like Synergy. The future does look promising, as Wayland community is now discussing Synergy support in the Wayland libei library. The Wayland libei library was created to add Emulated Input to Wayland, and is primarily aimed at the Wayland stack. The Wayland libei library even mentions Synergy nine times, which certainly sounds promising.

  

On 6/5/2023 at 7:41 PM, Pooks said:

Looks pretty nice, however, is there anyway to make it start in the background? Kinda annoying to have a big, white, unneeded window pop up every time I start any of my computers.

Synergy 3 starts automatically in the background. Once you're finished configuring it, just close the GUI.

I think we should add dark mode to the roadmap 😉

On 6/6/2023 at 12:48 AM, later85 said:

I am loving this new version of synergy, although I have one issue I can't seem to wrap my head around. 

In the BETA I was able to unlock my m1 mac from my windows as the host, now with the new rc1 version, it no longer works. The settings are checked to have the ability to unlock my mac and synergy is still in the login items under system preferences. 

We think we may have fixed this in RC2, please give it a try and let me know!

On 6/6/2023 at 12:48 AM, later85 said:

Keep up the great work Symless.

Thank you so much!

Link to post
Share on other sites
  • Kyle Bloom unpinned and unfeatured this topic
On 6/1/2023 at 8:11 AM, Kris Dekeyser said:

Unfortunately I still have the same problem as with the beta versions: the synergy service does not start automatically on my xubuntu 22.04 PCs. This is the output from 'journalctl -xeu synergy.service':

....
â–‘â–‘ An ExecStartPre= process belonging to unit synergy.service has exited.
░░ 
â–‘â–‘ The process' exit code is 'killed' and its exit status is 15.
mei 31 21:25:33 beast systemd[1]: synergy.service: Failed with result 'timeout'.
 

@Kris Dekeyser
Did you manage to get past this issue on RC1 or RC2 at all?

Link to post
Share on other sites
Kris Dekeyser
On 7/30/2023 at 9:15 AM, zwarbo said:

@Kris Dekeyser
Did you manage to get past this issue on RC1 or RC2 at all?

Nope, I just tried with a full uninstall of RC1 and clean install RC2. Nothing changed. Your startup still waits for the file /var/run/user/$GDM_ID/gdm/Xauthority which is never created.

root@beast:~# systemctl status synergy.service 
× synergy.service - Synergy 3 Login service
     Loaded: loaded (/etc/systemd/system/synergy.service; enabled; vendor preset: enabled)
     Active: failed (Result: timeout) since Mon 2023-07-31 18:07:09 CEST; 4min 52s ago
    Process: 879 ExecStartPre=/opt/Synergy/resources/services/system/loginLauncherPre.sh (code=killed, signal=TERM)
        CPU: 65ms

jul 31 18:05:39 beast systemd[1]: Starting Synergy 3 Login service...
jul 31 18:07:09 beast systemd[1]: synergy.service: start-pre operation timed out. Terminating.
jul 31 18:07:09 beast systemd[1]: synergy.service: Control process exited, code=killed, status=15/TERM
jul 31 18:07:09 beast systemd[1]: synergy.service: Failed with result 'timeout'.
jul 31 18:07:09 beast systemd[1]: Failed to start Synergy 3 Login service.
 

Link to post
Share on other sites
Kris Dekeyser
7 hours ago, Kris Dekeyser said:

Nope, I just tried with a full uninstall of RC1 and clean install RC2. Nothing changed. Your startup still waits for the file /var/run/user/$GDM_ID/gdm/Xauthority which is never created.
 

The synergy-service only starts when the client is started.

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...