Jump to content

Synergy + Zoom - Unable to Clickon Client systems


Gavin Barnard

Recommended Posts

Gavin Barnard

Hi

This has been occurring since synergy 2.0.6.  I have upgraded to 2.0.10 and the issue is still present.

If I join a Zoom meeting https://zoom.us all my client screens can no longer receive left/right/middle clicks until I restart the synergy service on the main computer.

This is very easy to repro.  Install synergy on two or more systems.   Launch a Zoom meeting on the system sharing mouse/keyboard, all other systems are unable to receive clicks until service restart.

Link to comment
Share on other sites

  • Gavin Barnard changed the title to Synergy + Zoom - Unable to Clickon Client systems
  • 1 month later...
Kelvin Tran
On 4/24/2018 at 1:14 PM, Gavin Barnard said:

Hi

This has been occurring since synergy 2.0.6.  I have upgraded to 2.0.10 and the issue is still present.

If I join a Zoom meeting https://zoom.us all my client screens can no longer receive left/right/middle clicks until I restart the synergy service on the main computer.

This is very easy to repro.  Install synergy on two or more systems.   Launch a Zoom meeting on the system sharing mouse/keyboard, all other systems are unable to receive clicks until service restart.

Let me investigate this issue for ya and see if I can reproduce it.

Link to comment
Share on other sites

I had the same thing happen to me today.  Joined a zoom meeting and client clicks stopped working.  (Restarting the service on the server is a temporary workaround and that got things working again).  

Link to comment
Share on other sites

Gavin Barnard

Logs:

mainleft https://synergy-logs.symless.com/83b6246f88d0b275a5a4cebe940a78f9/logs/647-2018-06-19T18-35-20.log

middle https://synergy-logs.symless.com/83b6246f88d0b275a5a4cebe940a78f9/logs/647-2018-06-19T18-35-37.log

right: https://synergy-logs.symless.com/83b6246f88d0b275a5a4cebe940a78f9/logs/647-2018-06-19T18-35-52.log

 

from mainleft: issue occurs during this window


[ Core    ] [2018-06-19T18:33:22] INFO: switch from "gavin-pc-win8" to "GAVINBARNARD-E7" at 3831,976
[ Core    ] [2018-06-19T18:33:22] INFO: entering screen

> Zoom meeting joined and mainleft cursor to middle


[ Core    ] [2018-06-19T18:33:55] INFO: switch from "GAVINBARNARD-E7" to "gavin-pc-win8" at 0,91
[ Core    ] [2018-06-19T18:33:55] INFO: leaving screen
[ Core    ] [2018-06-19T18:33:55] DEBUG: open clipboard
[ Core    ] [2018-06-19T18:33:55] DEBUG: close clipboard
[ Core    ] [2018-06-19T18:33:55] DEBUG: ignored screen "GAVINBARNARD-E7" update of clipboard 0 (unchanged)
[ Core    ] [2018-06-19T18:33:55] DEBUG: open clipboard
[ Core    ] [2018-06-19T18:33:55] DEBUG: close clipboard
[ Core    ] [2018-06-19T18:33:55] DEBUG: ignored screen "GAVINBARNARD-E7" update of clipboard 1 (unchanged)
[ Core    ] [2018-06-19T18:33:55] DEBUG: dropped bogus delta motion: +2981,-449
[ Core    ] [2018-06-19T18:33:55] INFO: switch from "gavin-pc-win8" to "DESKTOP-GRN89IA" at 8,703
[ Core    ] [2018-06-19T18:33:55] DEBUG: sending clipboard 0 to "DESKTOP-GRN89IA"
[ Core    ] [2018-06-19T18:33:55] DEBUG: sent clipboard size=101
[ Core    ] [2018-06-19T18:33:55] DEBUG: sending clipboard 1 to "DESKTOP-GRN89IA"
[ Core    ] [2018-06-19T18:33:55] DEBUG: sent clipboard size=101
[ Core    ] [2018-06-19T18:33:56] INFO: switch from "DESKTOP-GRN89IA" to "gavin-pc-win8" at 1912,449
[ Core    ] [2018-06-19T18:34:20] INFO: switch from "gavin-pc-win8" to "DESKTOP-GRN89IA" at 6,827
[ Core    ] [2018-06-19T18:34:24] INFO: switch from "DESKTOP-GRN89IA" to "gavin-pc-win8" at 1860,347
[ Core    ] [2018-06-19T18:34:42] INFO: switch from "gavin-pc-win8" to "GAVINBARNARD-E7" at 3814,644
[ Core    ] [2018-06-19T18:34:42] INFO: entering screen
[ Core    ] [2018-06-19T18:35:05] INFO: switch from "GAVINBARNARD-E7" to "gavin-pc-win8" at 0,485
[ Core    ] [2018-06-19T18:35:05] INFO: leaving screen
[ Core    ] [2018-06-19T18:35:05] DEBUG: open clipboard
[ Core    ] [2018-06-19T18:35:05] DEBUG: close clipboard
[ Core    ] [2018-06-19T18:35:05] DEBUG: ignored screen "GAVINBARNARD-E7" update of clipboard 0 (unchanged)
[ Core    ] [2018-06-19T18:35:05] DEBUG: open clipboard
[ Core    ] [2018-06-19T18:35:05] DEBUG: close clipboard
[ Core    ] [2018-06-19T18:35:05] DEBUG: ignored screen "GAVINBARNARD-E7" update of clipboard 1 (unchanged)
[ Core    ] [2018-06-19T18:35:09] INFO: switch from "gavin-pc-win8" to "DESKTOP-GRN89IA" at 51,1513
[ Core    ] [2018-06-19T18:35:12] INFO: switch from "DESKTOP-GRN89IA" to "gavin-pc-win8" at 1910,557
[ Core    ] [2018-06-19T18:35:12] INFO: switch from "gavin-pc-win8" to "GAVINBARNARD-E7" at 3750,602
[ Core    ] [2018-06-19T18:35:12] INFO: entering screen

Link to comment
Share on other sites

Kelvin Tran
1 hour ago, Gavin Barnard said:

Logs:

mainleft https://synergy-logs.symless.com/83b6246f88d0b275a5a4cebe940a78f9/logs/647-2018-06-19T18-35-20.log

middle https://synergy-logs.symless.com/83b6246f88d0b275a5a4cebe940a78f9/logs/647-2018-06-19T18-35-37.log

right: https://synergy-logs.symless.com/83b6246f88d0b275a5a4cebe940a78f9/logs/647-2018-06-19T18-35-52.log

 

from mainleft: issue occurs during this window


[ Core    ] [2018-06-19T18:33:22] INFO: switch from "gavin-pc-win8" to "GAVINBARNARD-E7" at 3831,976
[ Core    ] [2018-06-19T18:33:22] INFO: entering screen

> Zoom meeting joined and mainleft cursor to middle


[ Core    ] [2018-06-19T18:33:55] INFO: switch from "GAVINBARNARD-E7" to "gavin-pc-win8" at 0,91
[ Core    ] [2018-06-19T18:33:55] INFO: leaving screen
[ Core    ] [2018-06-19T18:33:55] DEBUG: open clipboard
[ Core    ] [2018-06-19T18:33:55] DEBUG: close clipboard
[ Core    ] [2018-06-19T18:33:55] DEBUG: ignored screen "GAVINBARNARD-E7" update of clipboard 0 (unchanged)
[ Core    ] [2018-06-19T18:33:55] DEBUG: open clipboard
[ Core    ] [2018-06-19T18:33:55] DEBUG: close clipboard
[ Core    ] [2018-06-19T18:33:55] DEBUG: ignored screen "GAVINBARNARD-E7" update of clipboard 1 (unchanged)
[ Core    ] [2018-06-19T18:33:55] DEBUG: dropped bogus delta motion: +2981,-449
[ Core    ] [2018-06-19T18:33:55] INFO: switch from "gavin-pc-win8" to "DESKTOP-GRN89IA" at 8,703
[ Core    ] [2018-06-19T18:33:55] DEBUG: sending clipboard 0 to "DESKTOP-GRN89IA"
[ Core    ] [2018-06-19T18:33:55] DEBUG: sent clipboard size=101
[ Core    ] [2018-06-19T18:33:55] DEBUG: sending clipboard 1 to "DESKTOP-GRN89IA"
[ Core    ] [2018-06-19T18:33:55] DEBUG: sent clipboard size=101
[ Core    ] [2018-06-19T18:33:56] INFO: switch from "DESKTOP-GRN89IA" to "gavin-pc-win8" at 1912,449
[ Core    ] [2018-06-19T18:34:20] INFO: switch from "gavin-pc-win8" to "DESKTOP-GRN89IA" at 6,827
[ Core    ] [2018-06-19T18:34:24] INFO: switch from "DESKTOP-GRN89IA" to "gavin-pc-win8" at 1860,347
[ Core    ] [2018-06-19T18:34:42] INFO: switch from "gavin-pc-win8" to "GAVINBARNARD-E7" at 3814,644
[ Core    ] [2018-06-19T18:34:42] INFO: entering screen
[ Core    ] [2018-06-19T18:35:05] INFO: switch from "GAVINBARNARD-E7" to "gavin-pc-win8" at 0,485
[ Core    ] [2018-06-19T18:35:05] INFO: leaving screen
[ Core    ] [2018-06-19T18:35:05] DEBUG: open clipboard
[ Core    ] [2018-06-19T18:35:05] DEBUG: close clipboard
[ Core    ] [2018-06-19T18:35:05] DEBUG: ignored screen "GAVINBARNARD-E7" update of clipboard 0 (unchanged)
[ Core    ] [2018-06-19T18:35:05] DEBUG: open clipboard
[ Core    ] [2018-06-19T18:35:05] DEBUG: close clipboard
[ Core    ] [2018-06-19T18:35:05] DEBUG: ignored screen "GAVINBARNARD-E7" update of clipboard 1 (unchanged)
[ Core    ] [2018-06-19T18:35:09] INFO: switch from "gavin-pc-win8" to "DESKTOP-GRN89IA" at 51,1513
[ Core    ] [2018-06-19T18:35:12] INFO: switch from "DESKTOP-GRN89IA" to "gavin-pc-win8" at 1910,557
[ Core    ] [2018-06-19T18:35:12] INFO: switch from "gavin-pc-win8" to "GAVINBARNARD-E7" at 3750,602
[ Core    ] [2018-06-19T18:35:12] INFO: entering screen

Hmm.

I'm sorry, I just got around to taking a look at your issue and your reproduction of the issue.

Looking at your logs, there's nothing immediately wrong from logs alone that I can notice. It seems that Synergy is handling the mouse-switching perfectly, the issue now can be narrowed down to the compatibility between Synergy and Zoom.

However, I do have a theory for the issue, and @Nick Bolton, it may serve you well to look into this as it may be a potential issue with other application of Zoom's kind.

You mentioned in your video of the issue that Synergy will begin to work again when the main Zoom window is brought to the background instead of being in the foreground, and I must ask you - does Zoom have any functionality that would allow you to share the screen or any other functionality that might try to grab the mouse? I think the issue is that Zoom is messing around with the mouse's driver call in such a way that it will track cursor movement but, for some reason that I can't fathom, would mess up the system call for a mouse click.

Have you tried this on Synergy 1? Can this issue be reproduced with Synergy 1, since I do see that you are running the beta release of the software?

Link to comment
Share on other sites

56 minutes ago, Kelvin Tran said:

Have you tried this on Synergy 1? Can this issue be reproduced with Synergy 1, since I do see that you are running the beta release of the software?

This happened to me today using Synergy 1.9.1 stable.  I joined a Zoom meeting and the exact same symptoms occurred.  

Link to comment
Share on other sites

Kelvin Tran
Just now, jayvee said:

This happened to me today using Synergy 1.9.1 stable.  I joined a Zoom meeting and the exact same symptoms occurred.  

Hmm. Interesting.

My theory seems somewhat sound based on what you all have described.

Link to comment
Share on other sites

1 hour ago, Kelvin Tran said:

@Nick Bolton, it may serve you well to look into this as it may be a potential issue with other application of Zoom's kind.

@Kelvin TranAnother application that seems to cause issues is AutoHotKey (both in Synergy 1.x and 2.x).  The same symptoms happen, though... when the issue is triggered, clicking on the server's "desktop" (removing focus from any application) allows clicks to go through, at least until an application takes focus on the server.  

There's a more general discussion of this issue here, going back over a year.  

 

Link to comment
Share on other sites

Kelvin Tran
Just now, jayvee said:

@Kelvin TranAnother application that seems to cause issues is AutoHotKey (both in Synergy 1.x and 2.x).  The same symptoms happen, though... when the issue is triggered, clicking on the server's "desktop" (removing focus from any application) allows clicks to go through, at least until an application takes focus on the server.  

There's a more general discussion of this issue here, going back over a year.  

 

And with AHK, what triggers the issue? AHK being in foreground or AHK just running?

That just affirms my theory of Synergy glitching out with software that also manipulates system calls.

Link to comment
Share on other sites

2 minutes ago, Kelvin Tran said:

And with AHK, what triggers the issue? AHK being in foreground or AHK just running?

That just affirms my theory of Synergy glitching out with software that also manipulates system calls.

The AHK issue happens much more sporadically/randomly.  Not anywhere near as clean-cut as triggering it with Zoom according to the instructions above.  However, when it happens, the symptoms are exactly the same, even down to the behavior of broken clicks when an application has focus on the server, and clicks working when focus is moved to the server's desktop.  

AHK has a directive to not hook mouse calls by adding a "#Hotstring NoMouse" line in the AHK script (details are in the other thread).  Since implementing that, I believe my AHK-triggered broken_client_clicks have subsided.  Now that I know to expect it with Zoom, I'll have to watch and see if there are any more non-Zoom triggers.  

I'm more than happy to provide additional information from my 1.9.1 environment, and I'm sure that @Gavin Barnard is more than happy to do the same with his 2.x.  

Thanks for looking into this!  

Link to comment
Share on other sites

Gavin Barnard
2 hours ago, Kelvin Tran said:

You mentioned in your video of the issue that Synergy will begin to work again when the main Zoom window is brought to the background instead of being in the foreground, and I must ask you - does Zoom have any functionality that would allow you to share the screen or any other functionality that might try to grab the mouse? I think the issue is that Zoom is messing around with the mouse's driver call in such a way that it will track cursor movement but, for some reason that I can't fathom, would mess up the system call for a mouse click.

Have you tried this on Synergy 1? Can this issue be reproduced with Synergy 1, since I do see that you are running the beta release of the software?

Yes zoom allows you to share your screen, allow others to take control, or for you to take control of their shared screen.  I have not had similar issues with Webex or TeamViewer.

I cannot take the time to re-install on 1.9 and rebuild my configs across systems it would be too much downtime, I may be able to do this after summer and the rest of my own work team is back.   Right now I need all systems available to work.

Link to comment
Share on other sites

Kelvin Tran
1 hour ago, Gavin Barnard said:

Yes zoom allows you to share your screen, allow others to take control, or for you to take control of their shared screen.  I have not had similar issues with Webex or TeamViewer.

I cannot take the time to re-install on 1.9 and rebuild my configs across systems it would be too much downtime, I may be able to do this after summer and the rest of my own work team is back.   Right now I need all systems available to work.

Well, of course not with TeamViewer, as the way TeamViewer works, because it's remote control, it's not constantly interrupting system calls for your mouse driver.

Link to comment
Share on other sites

  • 3 weeks later...

Also chiming in to confirm that I see the same thing using Synergy 1.8.8-stable.  Exiting Zoom on the server machine also serves as a workaround but of course you have to be done using Zoom for that moment.

Link to comment
Share on other sites

  • 2 months later...

ShareMouse solves this issue.  In another topic someone recommended using a different product, ShareMouse.  Sharemouse is free for personal use and works automatically as well as allows me to click to my heart's content while in a Zoom meeting and worked out of the box with no configuration changes needed.  Switching to ShareMouse!

Link to comment
Share on other sites

Actually Mouse without Borders from Microsoft is amazing and solves this issue and is free.  I ended up having problems with ShareMouse and it puts up a pay wall after a short period of time if you have multiple monitors (which everyone does).

 

Link to comment
Share on other sites

  • 1 month later...
Gavin Barnard

I'm now using a MacOSX as my work computer and this issue does not occur with zoom meetings hosted from it.   It seems to only be related to Win versions when they are in server mode.

Link to comment
Share on other sites

invalid_reference_of_a_nul

I also have this issue with Zoom conflicting with Synergy 2. I have not tested in Synergy 1. FWIW, a workaround I discovered is that once the mouse-click fails on the client system, if I click on the Windows Desktop of the server system, the mouse-clicks begin to work again. They will continue to work until Zoom has focus on the server system. 

I am really excited to see discussion around this issue. It drives me nuts.

Link to comment
Share on other sites

  • 2 weeks later...

Everyone who is experiencing issues with Zoom and Synergy compatibility:

It's most likely caused by conflicting instructions for mouse and keyboard control between Synergy and Zoom. It could also possibly be another incompatibility/inefficiency or a combination of the two.

If someone would like to do so, please start a thread with Zoom about the issue and share the results here. I am truly interested.

A CS thread with Zoom may expose an incompatibility between how Zoom and how Synergy handle API-level mouse and keyboard control. 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...