All Activity

This stream auto-updates     

  1. Today
  2. Yesterday
  3. Some observations about the screen/mouse freezing problem.

    It didn't help, I'm still getting intermittent freezes. Also, clipboard sharing stopped working.
  4. Last week
  5. English US International Keyboard not working

    Hey i saw you introduced some workarouns to make the US Int keyboard work on some clients, i.e., Windows to Windows it works. I'm really glad to see that. But from some other systems it still doesn't work, from Linux to Windows it stills doesn't work. Am i mising some configuration or something?
  6. Is the disabled call XWindowsUtil::getWindowProperty()? I've been running my own patched version of 10.1 and 10.2 with that disabled for a couple weeks. It's been much better, but I have seen occasional freezes, especially when using Qt applications. (I was laying out a widget with designer the other day and it was pretty bad).
  7. keyboard input sometimes ignored for some Java programs

    Not sure if you are still watching this thread. i've been having this issue with PyCharm, which is in the IntelliJ family of IDE's. Your steps to reproduce the issue consistently reproduce the issue for me as well. Also, I've been able to get the caret (text prompt) back by opening the settings dialog, or other dialog using the mouse, but it is a pain in the butt! If you happen to read this and you have since solved the problem, could you post your solution here?
  8. Some observations about the screen/mouse freezing problem.

    Hi guys, I have been tracking issues about mouse freezing for a while now. Although the symptom is the mouse freezing the causes seems to be varied in the reports I have received. One of the causes is solved by disabling a particular function and I would like to check if it solves the problem in other cases of the mouse freezing. Could you try out the development builds below, They are based on the current 1.10.2 release with the probable offending function disabled. Windows x64:http://snapshots.symless.com/synergy/v1-core-standard/windows-x64/Release/Synergy_v1.10.2-testing6487_b119-93275071.msi Windows x32: http://snapshots.symless.com/synergy/v1-core-standard/windows-x86/Release/Synergy_v1.10.2-testing6487_b117-93275071.msi macOS: http://snapshots.symless.com/synergy/v1-core-standard/macos/Synergy_v1.10.2-testing6487_b133-93275071.dmg Ubuntu16: http://snapshots.symless.com/synergy/v1-core-standard/ubuntu16/synergy_1.10.2.testing6487~b107+93275071_amd64.deb Ubuntu18: http://snapshots.symless.com/synergy/v1-core-standard/ubuntu18/synergy_1.10.2.testing6487~b17+93275071_amd64.deb Ubuntu19: http://snapshots.symless.com/synergy/v1-core-standard/ubuntu19/synergy_1.10.2.testing6487~b19+93275071_amd64.deb Debian 9: http://snapshots.symless.com/synergy/v1-core-standard/debian/synergy_1.10.2.testing6487~b115+93275071_amd64.deb CentOS 7.5: http://snapshots.symless.com/synergy/v1-core-standard/centos/x86_64/synergy-1.10.2-116.testing6487.93275071.el7.x86_64.rpm Could you post your results in this thread or on the GitHub issue here
  9. Auto start on Linux before login

    I gave it a try, and it looks like it works! (I was worried about overloading XAUTHORITY more globally). Much cleaner than going through bash.
  10. Auto start on Linux before login

    In my case, I also removed the ExceStart statement. It takes a little while until it starts working, but it works so my ExecStart looks like this: ExecStart=/bin/bash -c "XAUTHORITY=/var/run/lightdm/root/:0 /usr/bin/synergy-core --client --no-daemon --debug INFO --name mynuc TxWh:24800" Earlier in this thread, I saw that someone did Environment="XAUTHORITY=/var/run/lightdm/root/:0" after the ExecStart instead of executing a shell to run the service executable. I have not tried that
  11. Auto start on Linux before login

    I had a few moments to install LightDM and confirmed it worked on my end too. For completeness, here's my working synergy.service file: [Unit] Description=Synergy Service Requires=display-manager.service After=display-manager.service [Service] Type=simple Restart=always RestartSec=3 ExecStartPre=/bin/bash -c "sleep 10; /bin/systemctl set-environment LIGHTDMXAUTH=/var/run/lightdm/root/:0" ExecStart=/bin/bash -c "XAUTHORITY=${LIGHTDMXAUTH} /opt/synergy-core/build/bin/synergyc -f -n minotaur 192.168.0.150" [Install] WantedBy=graphical.target If anyone has a general way of finding the XAuthority file for multiple window managers, It'd be nice to see. Glad its working for you, @marcelo!
  12. Auto start on Linux before login

    Great! Now it works Finally! Thanks so much!
  13. Auto start on Linux before login

    @Xerotope Dean, I missed that setting, thank you for noticing. However, I've tried, but no success yet. I still have to login into the GUI for the service to be able to connect to the synergy server. I'm not an expert on this, so any help will be appreciated. my current synergy.service is: [Unit] Description=Synergy Client Daemon Requires=display-manager.service After=display-manager.service After=network.target [Service] ;User=marcelo ;Group=root Type=simple Restart=always RestartSec=3 ExecStartPre=/bin/bash -c "sleep 5;sudo /bin/systemctl set-environment SDDMXAUTH=/var/run/lightdm/marcelo/xauthority" ExecStart=/bin/bash -c "XAUTHORITY=/var/run/lightdm/marcelo/xauthority /usr/bin/synergy-core --client --no-daemon --debug INFO --name intelnuc1 TxWh:24800" [Install] WantedBy=graphical.target the status of the service before login into the GUI is: $ sudo systemctl status synergy ● synergy.service - Synergy Client Daemon Loaded: loaded (/etc/systemd/system/synergy.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2019-05-23 14:48:52 EDT; 47s ago Process: 1347 ExecStartPre=/bin/bash -c sleep 5;sudo /bin/systemctl set-environment SDDMXAUTH=/var/run/lightdm/marcelo/xauthority (code=exited, status=0/SUCCESS) Main PID: 2526 (synergy-core) Tasks: 3 (limit: 4915) Memory: 3.4M CGroup: /system.slice/synergy.service └─2526 /usr/bin/synergy-core --client --no-daemon --debug INFO --name intelnuc1 TxWh:24800 May 23 14:48:47 intelnuc1 systemd[1]: Starting Synergy Client Daemon... May 23 14:48:52 intelnuc1 sudo[2389]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl set-environment SDDMXAUTH=/var/run/lightdm/marcelo/xauthority May 23 14:48:52 intelnuc1 sudo[2389]: pam_unix(sudo:session): session opened for user root by (uid=0) May 23 14:48:52 intelnuc1 sudo[2389]: pam_unix(sudo:session): session closed for user root May 23 14:48:52 intelnuc1 systemd[1]: Started Synergy Client Daemon. May 23 14:48:52 intelnuc1 bash[2526]: [2019-05-23T14:48:52] WARNING: failed to set process uid to: -1 May 23 14:48:52 intelnuc1 bash[2526]: No protocol specified May 23 14:48:52 intelnuc1 bash[2526]: [2019-05-23T14:48:52] WARNING: secondary screen unavailable: unable to open screen looking at the synergy process before login in: $ ps -elf |grep syn 4 S root 2526 1 0 80 0 - 7208 - 14:48 ? 00:00:00 /usr/bin/synergy-core --client --no-daemon --debug INFO --name intelnuc1 Marcelo-s-Mac-TxWh:24800 0 R marcelo 3280 3043 0 80 0 - 53936 - 14:50 pts/1 00:00:00 grep --color=auto syn looking at the lightDM processes at the same time (note that there is a lightdm user): $ ps -elf |grep light 4 S root 1118 1 0 80 0 - 60060 - 14:48 ? 00:00:00 /usr/sbin/lightdm 4 S root 1344 1118 0 80 0 - 141171 - 14:48 tty1 00:00:00 /usr/libexec/Xorg -core -noreset :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch 4 S root 1495 1118 0 80 0 - 45637 - 14:48 ? 00:00:00 lightdm --session-child 18 21 4 S lightdm 1499 1 0 80 0 - 5012 - 14:48 ? 00:00:00 /usr/lib/systemd/systemd --user 5 S lightdm 1501 1499 0 80 0 - 12986 - 14:48 ? 00:00:00 (sd-pam) 4 S lightdm 1509 1495 0 80 0 - 220549 - 14:48 ? 00:00:01 /usr/sbin/lightdm-gtk-greeter 0 S lightdm 1512 1499 0 80 0 - 69176 - 14:48 ? 00:00:00 /usr/bin/dbus-broker-launch --scope user 0 S lightdm 1513 1512 0 80 0 - 1295 - 14:48 ? 00:00:00 dbus-broker --log 4 --controller 11 --machine-id 4047399e12c94233ae08a61711b9a466 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000 0 S lightdm 1514 1499 0 80 0 - 76275 - 14:48 ? 00:00:00 /usr/libexec/at-spi-bus-launcher 0 S lightdm 1519 1514 0 80 0 - 67078 - 14:48 ? 00:00:00 /usr/bin/dbus-broker-launch --config-file=/usr/share/defaults/at-spi2/accessibility.conf --scope user 0 S lightdm 1520 1519 0 80 0 - 1264 - 14:48 ? 00:00:00 dbus-broker --log 4 --controller 9 --machine-id 4047399e12c94233ae08a61711b9a466 --max-bytes 100000000000000 --max-fds 6400000 --max-matches 5000000000 0 S lightdm 1522 1499 0 80 0 - 40140 - 14:48 ? 00:00:00 /usr/libexec/at-spi2-registryd --use-gnome-session 0 S lightdm 1523 1499 0 80 0 - 111648 - 14:48 ? 00:00:00 /usr/libexec/gvfsd 0 S lightdm 1530 1499 0 80 0 - 78149 - 14:48 ? 00:00:00 /usr/libexec/gvfsd-fuse /run/user/976/gvfs -f -o big_writes 0 S root 1557 1118 0 80 0 - 6610 - 14:48 ? 00:00:00 lightdm --session-child 14 21 4 S root 2798 1130 0 60 -20 - 11557 - 14:48 ? 00:00:00 /usr/NX/bin/nxexec --node --user lightdm --priority realtime --mode 0 --pid 18 4 S lightdm 2810 2798 0 60 -20 - 402194 - 14:48 ? 00:00:00 /usr/NX/bin/nxnode.bin 0 S marcelo 3299 3043 0 80 0 - 53936 - 14:52 pts/1 00:00:00 grep --color=auto light after logging into the GUI the lightdm user disappears, so I think the greeter is running under its own user: $ ps -elf |grep light 4 S root 1118 1 0 80 0 - 60068 - 14:48 ? 00:00:00 /usr/sbin/lightdm 4 S root 1344 1118 0 80 0 - 81518 - 14:48 tty1 00:00:02 /usr/libexec/Xorg -core -noreset :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch 4 S root 3736 1118 0 80 0 - 47752 - 15:06 ? 00:00:00 lightdm --session-child 14 21 0 S marcelo 5472 3043 0 80 0 - 53936 - 15:06 pts/1 00:00:00 grep --color=auto light the status of the synergy service after login into the GUI is : $ sudo systemctl status synergy ● synergy.service - Synergy Client Daemon Loaded: loaded (/etc/systemd/system/synergy.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2019-05-23 15:23:11 EDT; 2s ago Process: 12045 ExecStartPre=/bin/bash -c sleep 5;sudo /bin/systemctl set-environment SDDMXAUTH=/var/run/lightdm/marcelo/xauthority (code=exited, status=0/SUCCESS) Main PID: 12120 (synergy-core) Tasks: 3 (limit: 4915) Memory: 2.2M CGroup: /system.slice/synergy.service └─12120 /usr/bin/synergy-core --client --no-daemon --debug INFO --name intelnuc1 TxWh:24800 May 23 15:23:05 intelnuc1 systemd[1]: Starting Synergy Client Daemon... May 23 15:23:10 intelnuc1 sudo[12075]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl set-environment SDDMXAUTH=/var/run/lightdm/marcelo/xauthority May 23 15:23:11 intelnuc1 sudo[12075]: pam_unix(sudo:session): session opened for user root by (uid=0) May 23 15:23:11 intelnuc1 sudo[12075]: pam_unix(sudo:session): session closed for user root May 23 15:23:11 intelnuc1 systemd[1]: Started Synergy Client Daemon. May 23 15:23:11 intelnuc1 bash[12120]: [2019-05-23T15:23:11] WARNING: failed to set process uid to: -1 May 23 15:23:11 intelnuc1 bash[12120]: [2019-05-23T15:23:11] NOTE: started client May 23 15:23:11 intelnuc1 bash[12120]: [2019-05-23T15:23:11] NOTE: connecting to 'Marcelo-s-Mac-TxWh': 192.168.1.130:24800 May 23 15:23:11 intelnuc1 bash[12120]: [2019-05-23T15:23:11] NOTE: connected to server under the /var/run/lightdm there are: /var/run/lightdm/root/:0 /var/run/lightdm/marcelo/xauthority /var/run/lightdm/lightdm/xauthority Not sure which one to use. Or if I need the ExecStartPre if I'm setting the XAUTHORITY in the ExecStart Not sure either what user and group should I use for the service (I commented that out for the time being) Marcelo
  14. SSL certificate doesn't exist

    Just wanted to write and say that turning off SSL/TLS on the server fixed the problem for me. I had just switched one of my clients to the server and I was receiving this same error. ERROR: secure socket error: tls certificate doesn't exist: /Users/admin/Library/Synergy/SSL/Synergy.pem I noticed as well that there was no SSL fingerprint listed as well so... turning it off and back on makes sense to generate the SSL fingerprint. Cheers!
  15. Synergy 1.10.2 Finally Released

    Updating Little Snitch still causes an error -65541 from Synergy that constantly opens an error dialog and requires force-quitting Synergy to stop for restart. Cropped screen capture below showing the error window opening while it is already open, the alpha shadow around it becoming opaque due to the number of stacked identical windows present. Something Little Snitch is doing while updating boot caches or earlier is affecting Synergy, making it go crazy with this error. I suspect but cannot yet confirm if quitting Synergy before updating Little Snitch prevents this error, but I assume it would. I hope Synergy could respond more gracefully to this. This was an instance of Little Snitch running on the Synergy server machine. I understand when Little Snitch refuses synthetic clicks on a remote machine in its dialogs as a security measure. This is separate from that.
  16. Hi, I just got an Nvidia Jetson TX2 and plan to install synergy on it. I followed the instruction and successfully make the file. But, I can't find the synergy app in my application search. Could you please help? https://github.com/symless/synergy-core/issues/6029 git clone https://github.com/symless/synergy-core.git cd synergy-core mkdir build cd build cmake .. make
  17. Auto start on Linux before login

    You still need to have your ExecStart line use bash to set the value of the XAUTHORITY environment variable for synergy. Hacky, I know, but was the easiest way off the top of my head.
  18. Auto start on Linux before login

    @Xerotope Oh, well, I hardcoded: SDDMXAUTH=/var/run/lightdm/root/:0 and I still have the same problem, the service client does not connect to the synergy server in the master computer until I login into the GUI of the client system. before the login to the GUI, I request the service status (via ssh terminal) and I get $ sudo systemctl status synergy ● synergy.service - Synergy Client Daemon Loaded: loaded (/etc/systemd/system/synergy.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2019-05-23 12:27:58 EDT; 19s ago Main PID: 2728 (synergy-core) Tasks: 3 (limit: 4915) Memory: 928.0K CGroup: /system.slice/synergy.service └─2728 /usr/bin/synergy-core --client --no-daemon --debug INFO --name intelnuc1 server_computer:24800 May 23 12:27:58 intelnuc1 systemd[1]: Started Synergy Client Daemon. May 23 12:27:58 intelnuc1 synergy-core[2728]: [2019-05-23T12:27:58] WARNING: failed to set process uid to: -1 May 23 12:27:58 intelnuc1 synergy-core[2728]: No protocol specified May 23 12:27:58 intelnuc1 synergy-core[2728]: [2019-05-23T12:27:58] WARNING: secondary screen unavailable: unable to open screen After I login to the GUI: $ sudo systemctl status synergy ● synergy.service - Synergy Client Daemon Loaded: loaded (/etc/systemd/system/synergy.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2019-05-23 12:27:58 EDT; 4min 36s ago Main PID: 2728 (synergy-core) Tasks: 3 (limit: 4915) Memory: 1.5M CGroup: /system.slice/synergy.service └─2728 /usr/bin/synergy-core --client --no-daemon --debug INFO --name intelnuc1 server_computer:24800 May 23 12:31:58 intelnuc1 synergy-core[2728]: [2019-05-23T12:31:58] NOTE: started client May 23 12:31:58 intelnuc1 synergy-core[2728]: [2019-05-23T12:31:58] NOTE: connecting to 'server_computer': 192.168.1.130:24800 May 23 12:31:58 intelnuc1 synergy-core[2728]: [2019-05-23T12:31:58] NOTE: connected to server So if you ever get a chance to look at LightDM, I'll appreciate it. This is my current synergy.service: [Unit] Description=Synergy Client Daemon Requires=display-manager.service After=display-manager.service After=network.target [Service] User=marcelo Group=root Type=simple Restart=always RestartSec=3 ExecStartPre=/bin/bash -c "sleep 10; sudo /bin/systemctl set-environment SDDMXAUTH=$(/var/run/lightdm/root/:0)" ExecStart=/usr/bin/synergy-core --client --no-daemon --debug INFO --name intelnuc1 server_computer:24800 [Install] WantedBy=graphical.target BTW, I'm using gnome in Fedora 30 with Wayland disabled. Thank you, Marcelo
  19. Download link for 1.10.1

    Same problem here. 1.10.2 is useless.
  20. Hi everyone, I am running a Mac-PC layout setup right now, and it would be great if we can have an option just to use 1 key combination to toggle back and forth through the screens. That would be incredibly useful for people with "1 server 1 client" setup! Thank you very much for your time reading this and consideration of this feature! Keep up the good work guys! Best, Mike
  21. I've just updated the machine running the synergy client and I'm faced with this problem; Was working fine with windows 10 as server and linux mint 18 (ubuntu 16) as client; I've upgraded to linux mint 19 (ubuntu 18) today and random freezes all over the place. Quite unusable like that. I've been trying other versions and I find that the synergy_1.10.1.stable_b87+8941241e_debian_amd64 seems to work good so far on mint 19. Alternatively I'll just revert back to the 1.6.3 which has yet to let me down.
  22. Synergy 1.10.2 Finally Released

    Looking at the Change Log there are some security updates like the following v1.9.1 Updated OpenSSL to v1.0.2o for better security v1.10.1-stable Forced use of TLS 1.2 without fallback method v1.10.2 Fixed TLS memory leak on Linux server when using client So there have been updates to the encryption protocols since 1.8.8 on top of other bug fixes and enhancements.
  23. Synergy 1.10.2 Finally Released

    OK, thanks. As I wrote in my original comment, 1.8.8 works fine for me, and I don't see anything in the fixes or enhancements that addresses my usage. That is, I really don't see - at first glance - any reason to update. Just to repeat, is v. 1.10.2 more secure in any meaningful way than 1.8.8? Thanks again.
  24. Synergy 1.10.2 Finally Released

    That is the case for Synergy 2 Beta. However for Synergy 1 it does not require an internet connection or for you to login to use the application.
  25. Hotkeys not working

    So...still no fix for hotkeys on the Mac then?
  26. Auto start on Linux before login

    I don't have the time to boot my machine with LightDM as the display manager right now, but google suggests it might be /var/run/lightdm/root/0. Maybe see what's there in your system? (If it doesn't change every boot, you don't even need the ExecStartPre and just hard code the path into the value of XAuthority). It would probably be cleaner to have a script that isn't dependent on a specific display manager.
  27. Auto start on Linux before login

    @Xerotope Thanks Dean, How would I have to modify the ExecStartPre statement if I'm using gnome and LightDM as the display manager? So far, I don't have that statement. instead, I have User=myUser Group=root the problem I have so far is that it does not work upon reboot. For it to work, I have to login (via other means) to the GUI, and then restart the service Thanks for your help, Marcelo
  1. Load more activity