seanbjauice

This version of Synergy is not supported anymore - Using Beta 5

15 posts in this topic

Hello,

I just upgraded to Beta 5 on both Mac and PC, I uninstalled both and re-installed and still get the error message "This version is not supported anymore. Please download the latest version.".

I am running the latest version Beta 5 and it appears to be working fine, but I keep getting that message every-time I launch.

Let me know if there is something I can change to get rid of the popup every time.

 

 

Share this post


Link to post
Share on other sites

I'm having the same issue.  Uninstalling and reinstalling did not help.

According to control panel details, version 2.0 is still being installed though the installer name suggests that it is for Beta 5.

Share this post


Link to post
Share on other sites

Me too on my Mac.  My Windows 10 x64 desktop is not giving me this error.  But if 1/2 doesn't work, it is useless!

Share this post


Link to post
Share on other sites

How do you even uninstall (on Mac), i cannot seem to find an official documentation on how to uninstall), I tried killing the process several times and deleting the app on the applications folder. And delete the the ~/Library/Synergy folder (and everything in it), and I also tried to delete the /Users/shared/Synergy folder (and everything in it).

But I also get the not supported version message (along with all the existing machines listed (even the ones no longer in use)

Share this post


Link to post
Share on other sites
15 minutes ago, JustTryin said:

How do you even uninstall (on Mac), i cannot seem to find an official documentation on how to uninstall), I tried killing the process several times and deleting the app on the applications folder. And delete the the ~/Library/Synergy folder (and everything in it), and I also tried to delete the /Users/shared/Synergy folder (and everything in it).

But I also get the not supported version message (along with all the existing machines listed (even the ones no longer in use)

On a Mac, uninstalling is typically as easy as dragging the application from the application folder to the trash.  With Synergy though, I had to kill it in activity monitor first as it wouldn't properly close in the current "not the latest version" state.

Share this post


Link to post
Share on other sites
1 hour ago, seanbjauice said:

I just upgraded to Beta 5 on both Mac and PC, I uninstalled both and re-installed and still get the error message "This version is not supported anymore. Please download the latest version.".

 

Try now! :)

 

Share this post


Link to post
Share on other sites
Just now, Nick Bolton said:

Try now! :)

 

Hi Nick,

Looks like this was fixed server side, I didn't touch the app, now when I open it I no longer get the message.

Thanks for the quick fix.

Sean

Share this post


Link to post
Share on other sites

Started to work for me too on a Ubuntu 17.10 server and a 16.04 client. I also removed the startup-applications for synergyd I had used in beta4. 

Also FWIW:

My client doesn't start correctly. I have to re-issue the systemctl restart synergy command for the client. every time so far.  

On the server I ran  synergy-config to get the blue box with the client and server yucky green internal boxes with server and client names. Then everything worked.

Much easier to get running than beta4. 

Jim

Share this post


Link to post
Share on other sites
13 hours ago, jim1 said:

My client doesn't start correctly. I have to re-issue the systemctl restart synergy command for the client. every time so far.  

1

Hmm. Next time you have to do that, could you check your log? It's under /var/log/synergy/

Share this post


Link to post
Share on other sites

Of course. This what beta is about. 

With both the synergy server and client working fine, I shut down my synergy client computer only to complete halt. then powered it back on. The synergy service is not working The log for synergy-service is below. There is a repeating "connecting websock" line followed by 6 lines. After that the  lines read "retrying websocket connection now" followed by 5 lines. Those line repeat continuously at various seconds. I have cut the list off after only a few down to the .... ....break ....

When I manually restart the client's synergy.service, via ssh login, the lines following the ...break.... are recorded and the synergy client becomes active.

Jim

[ Service ] [2017-10-31T22:41:28] debug: service log path: /var/log/synergy/synergy-service.log
[ Service ] [2017-10-31T22:41:28] debug: install dir: /usr/bin
[ Service ] [2017-10-31T22:41:28] info: starting service...
[ Service ] [2017-10-31T22:41:28] debug: connecting websocket
[ Service ] [2017-10-31T22:41:28] debug: tcp client resolve error: Host not found (non-authoritative), try again later
[ Service ] [2017-10-31T22:41:28] debug: websocket connect failed
[ Service ] [2017-10-31T22:41:28] debug: retrying websocket connection in 5s
[ Service ] [2017-10-31T22:41:28] debug: setting core uid from config: 1000
[ Service ] [2017-10-31T22:41:28] debug: creating rpc endpoints
[ Service ] [2017-10-31T22:41:28] debug: rpc endpoints created
[ Service ] [2017-10-31T22:41:33] debug: retrying websocket connection now
[ Service ] [2017-10-31T22:41:33] debug: connecting websocket
[ Service ] [2017-10-31T22:41:33] debug: tcp client resolve error: Host not found (non-authoritative), try again later
[ Service ] [2017-10-31T22:41:33] debug: websocket connect failed
[ Service ] [2017-10-31T22:41:33] error: websocket connection error
[ Service ] [2017-10-31T22:41:33] debug: retrying websocket connection in 1s
[ Service ] [2017-10-31T22:41:34] debug: retrying websocket connection now
[ Service ] [2017-10-31T22:41:34] debug: connecting websocket
[ Service ] [2017-10-31T22:41:34] debug: tcp client resolve error: Host not found (non-authoritative), try again later
[ Service ] [2017-10-31T22:41:34] debug: websocket connect failed
[ Service ] [2017-10-31T22:41:34] error: websocket connection error
[ Service ] [2017-10-31T22:41:34] debug: retrying websocket connection in 10s
[ Service ] [2017-10-31T22:41:44] debug: retrying websocket connection now
[ Service ] [2017-10-31T22:41:44] debug: connecting websocket
....

.... break

....

[ Service ] [2017-10-31T23:01:10] debug: core process is not running, ignoring shutdown
[ Service ] [2017-10-31T23:01:10] debug: core process is not running, ignoring shutdown
[ Service ] [2017-10-31T23:01:10] debug: service log path: /var/log/synergy/synergy-service.log
[ Service ] [2017-10-31T23:01:10] debug: install dir: /usr/bin
[ Service ] [2017-10-31T23:01:10] info: starting service...
[ Service ] [2017-10-31T23:01:10] debug: connecting websocket
[ Service ] [2017-10-31T23:01:10] debug: setting core uid from config: 1000
[ Service ] [2017-10-31T23:01:10] debug: creating rpc endpoints
[ Service ] [2017-10-31T23:01:10] debug: rpc endpoints created
[ Service ] [2017-10-31T23:01:11] debug: cloud client connected
[ Service ] [2017-10-31T23:01:11] debug: websocket connected
[ Service ] [2017-10-31T23:01:11] debug: comparing profiles, id=-1 this=v-1 other=v2
[ Service ] [2017-10-31T23:01:11] debug: profile id changed, -1->5067
[ Service ] [2017-10-31T23:01:11] debug: profile name changed, ->default
[ Service ] [2017-10-31T23:01:11] debug: profile server changed, -1->9992
[ Service ] [2017-10-31T23:01:11] debug: profile screen set changed, added=2 removed=0
[ Service ] [2017-10-31T23:01:11] debug: profile changed, storing local copy
[ Service ] [2017-10-31T23:01:11] debug: handling local profile server changed, mode=unknown thisId=11280 serverId=9992 lastServerId=-1
[ Service ] [2017-10-31T23:01:11] debug: starting core client process
[ Service ] [2017-10-31T23:01:11] debug: starting core process with command: /usr/bin/synergy-core --client -f --run-as-uid 1000 --debug DEBUG --name Pompeii --enable-drag-drop --profile-dir /var/lib/synergy --log /var/log/synergy/synergy-core.log 127.0.0.1:24801
[ Service ] [2017-10-31T23:01:11] debug: core process started, id=2418
[ Service ] [2017-10-31T23:01:11] debug: handling local profile screen set changed, mode=client
[ Service ] [2017-10-31T23:01:11] debug: comparing profiles, id=5067 this=v2 other=v2
[ Service ] [2017-10-31T23:01:11] debug: profile screen active changed, screenId=9992 false->true
[ Service ] [2017-10-31T23:01:11] debug: profile changed, storing local copy

 

.

 

Share this post


Link to post
Share on other sites
9 hours ago, jim1 said:

the synergy client becomes active.

So it started working after 20 mins?

Share this post


Link to post
Share on other sites

No. It did NOT recover during the 20 minutes. I had to issue the "systemctl restart synergy.service". I did that via an ssh login since it was a remote computer. The local computer has the mouse and KB attached.

FWIW. Using the ssh login I was able to find the running processes before and after the "systemctl restart synergy.service".

Before:    root       979  0.0  0.0 111332  9284 ?        Ss   10:05   0:00 /usr/bin/synergy-service

After:      root      3298  0.0  0.0 112512 10880 ?        Ss   10:13   0:01 /usr/bin/synergy-service
               jim       3301  0.0  0.0 137860  6412 ?        Sl   10:13   0:02 /usr/bin/synergy-core --client -f --run-as-uid 1000 --debug                                        DEBUG --name Pompeii --enable-drag-drop --profile-dir /var/lib/synergy --log /var/log/synergy/synergy-core.log                                    127.0.0.1:24801

Apparently the synergy-core is not starting correctly. When synergy-core is active the remote is available the local's mouse &KB are usable on the remote.

Suggestions for test are welcome.

Jim 

 

Share this post


Link to post
Share on other sites

Ah, I understand. Yeah, there's a bug in the service where it hangs when starting the core. We're fixing that right now. Stay tuned!

Share this post


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