Synergy Team Popular Post Kyle Bloom 6 Posted July 26 Synergy Team Popular Post Share Posted July 26 Synergy 3 RC2 is here! A few of the changes: Many fixes on all operating systems Skip empty screen with continue button Improved overall installation process Use readable names in generated config file More comprehensive reset procedure on macOS You can get RC2 on the download page. 3 Link to post Share on other sites
Salty Dog 3 Posted July 30 Share Posted July 30 Not working for me, can't find other devices. Windows 11, same subnet, wired. (RC1 worked fine.) Link to post Share on other sites
DieselDrax 2 Posted July 31 Share Posted July 31 RC2 is broken for me as well. Win11 server, Ubuntu 22.04 client. The connection is working but the mouse is "invisible" (actual pointer on Ubuntu doesn't move but I can see when my mouse is moving over buttons that highlight. Also, the keyboard isn't working. I've reset Synergy on both machines, no change. 1 Link to post Share on other sites
DieselDrax 2 Posted July 31 Share Posted July 31 Looks like this may actually be an issue with a recent update with Ubuntu that was applied today as I went back to RC1 and the same thing is happening. Sigh. Link to post Share on other sites
DieselDrax 2 Posted July 31 Share Posted July 31 11 minutes ago, DieselDrax said: Looks like this may actually be an issue with a recent update with Ubuntu that was applied today as I went back to RC1 and the same thing is happening. Sigh. I wish there were an edit option. Switching back to RC1 and rebooting both machines has me back up and running. Link to post Share on other sites
Salty Dog 3 Posted July 31 Share Posted July 31 It's working now, after trying a bunch of random things. Looks like I have to connect out from the "server" and not the "client" computers. Going from client to server resulted in "can't connect." I suspect it is a TLS thing? Don't know. Link to post Share on other sites
Salty Dog 3 Posted July 31 Share Posted July 31 @DieselDrax You might try disabling TLS in security. I'm not a 100 percent sure, but I saw a bunch of those kinds of errors when trying to connect an RC2 new install to a RC2 over RC1 install. I suspect RC1 didn't use TLS? Worth a shot just to try. Link to post Share on other sites
Salty Dog 3 Posted July 31 Share Posted July 31 @DieselDrax Disregard. TLS wouldn't affect mouse not showing/keyboard not working and sounds like your issue has to do with Ubuntu. Link to post Share on other sites
DieselDrax 2 Posted July 31 Share Posted July 31 10 minutes ago, Salty Dog said: @DieselDrax Disregard. TLS wouldn't affect mouse not showing/keyboard not working and sounds like your issue has to do with Ubuntu. It's an issue with RC2, I reset Synergy on both, reinstalled RC1, rebooted both, configured them, and now I'm back up and running again. I might try and reproduce the issue with RC2 again this evening just to confirm I have the same problem come back. 1 Link to post Share on other sites
PGP_Protector 0 Posted July 31 Share Posted July 31 Just to verify. After the Software Support Update date, we'll still be able to download the current version we're licensed for correct? Link to post Share on other sites
airtonix 0 Posted August 1 Share Posted August 1 still broken on fedora 38. the systemd unit file is pointing at shell scripts that do nothing on fedora 38 Link to post Share on other sites
Brendawg 0 Posted August 10 Share Posted August 10 When will Synergy 3 for RPI be available ? Link to post Share on other sites
R. W. 1 Posted August 23 Share Posted August 23 Is Synergy 3 RC2 already tested and working with the latest Parallels Desktop V19.0.0 under Host Macos Intel x86 and Windows 10/11 VM ? Please give me a short info, if there were any known issues. Link to post Share on other sites
DieselDrax 2 Posted August 28 Share Posted August 28 On 7/31/2023 at 12:18 PM, DieselDrax said: It's an issue with RC2, I reset Synergy on both, reinstalled RC1, rebooted both, configured them, and now I'm back up and running again. I might try and reproduce the issue with RC2 again this evening just to confirm I have the same problem come back. Just to follow up on this, it seems that my issue was related to Ubuntu 22.04 somehow switching from Xorg to Wayland, it would seem Synergy 3 doesn't fully/properly support Wayland. The only way I figured this out was when I switched back to Synergy 1 as even RC1 started failing and then Synergy 1 errored that it doesn't support Wayland. Weird as I never selected Wayland. Anyway, I'm back to running RC2 on Xorg and I have no problems. Link to post Share on other sites
DGHawks 0 Posted September 1 Share Posted September 1 Issue here with Ubuntu 22.04 (Server) and Latest build of Windows 11 (client). Running RC3 on both with TLS enabled. Windows 11 is 27" Monitor above my Samsung Neo 49". I have the smaller one directly above centered. Issue: My cursor never even makes an attempt to move upwards to the other screen. I can reproduce it every time. There is no attempt, and the verbose logging doesn't show that it's left my Ubuntu server screen and "entered" the Windows 11. Something is keeping it from recognizing it. Additional Bug: Interestingly enough, I had an application full screen (to the left of my Samsung) that is a second display connected to Ubuntu. In some odd cases (I have seen it twice now), when the application is running, and I move my mouse over it, it then switches to the Windows 11 machine. The entire width of the application appears to give the cursor the ability to move to my Windows machine. Unfortunately, I do not know how to replicate this and it appears to gone away after a restart. When it was doing it, it almost appeard that I had to hit the top edge of my monitor (simulating going to the Windows 11 monitor) before it would start doing it. Since that time, I have attempted to repeat it and cannot. Thanks, DG Link to post Share on other sites
airtonix 0 Posted September 7 Share Posted September 7 @Kyle Bloom and who ever "Daniel support" is: ~ x sudo systemctl status synergy.service × synergy.service - Synergy 3 Login service Loaded: loaded (/etc/systemd/system/synergy.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: failed (Result: timeout) since Thu 2023-09-07 19:53:20 ACST; 2min 42s ago Process: 282936 ExecStartPre=/opt/Synergy/resources/services/system/loginLauncherPre.sh (code=killed, signal=TE> CPU: 34ms Sep 07 19:52:34 brass systemd[1]: Starting synergy.service - Synergy 3 Login service... Sep 07 19:53:20 brass systemd[1]: synergy.service: start-pre operation timed out. Terminating. Sep 07 19:53:20 brass systemd[1]: synergy.service: Control process exited, code=killed, status=15/TERM Sep 07 19:53:20 brass systemd[1]: synergy.service: Failed with result 'timeout'. Sep 07 19:53:20 brass systemd[1]: Failed to start synergy.service - Synergy 3 Login service. ~ took 3s x sudo systemctl restart synergy ^C ~ took 20s x cat /etc/systemd/system/synergy.service; [Unit] Description=Synergy 3 Login service [Service] ExecStartPre=/opt/Synergy/resources/services/system/loginLauncherPre.sh ExecStart=/opt/Synergy/resources/services/system/loginLauncher.sh StandardOutput=syslog StandardError=syslog [Install] WantedBy=graphical.target ~ > cat /opt/Synergy/resources/services/system/loginLauncherPre.sh #!/usr/bin/env bash GDM_ID=$(id -u gdm) while [ ! -f "/var/run/user/$GDM_ID/gdm/Xauthority" ]; do sleep 1; done /bin/systemctl set-environment XAUTHORITY="/var/run/user/$GDM_ID/gdm/Xauthority" ~ > GDM_ID=$(id -u gdm) ls -al "/var/run/user/$GDM_ID/gdm/Xauthority" ls: cannot access '/var/run/user/42/gdm/Xauthority': No such file or directory ~ x GDM_ID=$(id -u gdm) ls -al "/var/run/user/$GDM_ID/gdm/" ls: cannot access '/var/run/user/42/gdm/': No such file or directory ~ x GDM_ID=$(id -u gdm) ls -al "/var/run/user/$GDM_ID/" ls: cannot access '/var/run/user/42/': No such file or directory ~ x GDM_ID=$(id -u gdm) ls -al "/var/run/user/" total 0 drwxr-xr-x. 4 root root 80 Aug 31 20:35 . drwxr-xr-x. 56 root root 1420 Sep 7 07:51 .. drwx------. 3 root root 60 Aug 31 20:35 0 drwx------. 20 zenobius zenobius 540 Sep 7 19:57 1000 ~ > ~ x ~ x cat /opt/Synergy/resources/services/system/loginLauncherPre.sh #!/usr/bin/env bash GDM_ID=$(id -u gdm) while [ ! -f "/var/run/user/$GDM_ID/gdm/Xauthority" ]; do sleep 1; done /bin/systemctl set-environment XAUTHORITY="/var/run/user/$GDM_ID/gdm/Xauthority" ~ > cat /etc/systemd/system/synergy.service; [Unit] Description=Synergy 3 Login service [Service] ExecStartPre=/opt/Synergy/resources/services/system/loginLauncherPre.sh ExecStart=/opt/Synergy/resources/services/system/loginLauncher.sh StandardOutput=syslog StandardError=syslog [Install] WantedBy=graphical.target ~ > cat /opt/Synergy/resources/services/system/loginLauncher.sh #!/usr/bin/env bash source /etc/Synergy/loginInfo if [ -z "$ARGS" ]; then echo "Login agent is disabled" else /opt/Synergy/synergy-core $ARGS fi ~ > cat /etc/Synergy/loginInfo ARGS=""% ~ > ????? ~ x /opt/Synergy/synergy-core Usage: synergy-core <server | client> [...options] server - start as a server (synergys) client - start as a client (synergyc) use synergy-core <server|client> --help for more information. ~ > /opt/Synergy/synergy-core server ~ > ???? wutttt????? ~ x sigh zsh: sigh: command not found... ~ x so disapoint son zsh: so: command not found... ~ Link to post Share on other sites
ArgonAlex 0 Posted September 9 Share Posted September 9 My antivirus on a Macbook is detecting the synergy service as virus in RC2. RC1 was fine. Link to post Share on other sites
BigCat 0 Posted September 12 Share Posted September 12 I'm getting RC2 rejected by my corporate virus scanner too - it is VirusTotal I believe. I would really like to use it otherwise. Link to post Share on other sites
BigCat 0 Posted September 12 Share Posted September 12 More info: https://www.virustotal.com/gui/file/1e0380b93c954e63b514c84c10694eea0527b9ec6e165931df846d953250b172/detection/f-1e0380b93c954e63b514c84c10694eea0527b9ec6e165931df846d953250b172-1694207023 Link to post Share on other sites
phillip.haydon 0 Posted September 14 Share Posted September 14 RC2 doesn't work on MacOS at all. Same issues as RC1, service doesn't start. Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now