Jump to content
Get SynergyOpen a support ticket

Keyboard not working - Mac Server, Windows Client


Recommended Posts

Danny Parker

Had the same issue this morning. Mac server, Windows client, Windows only recieving win key presses (CTRL on mac).

I went to the Privacy Tab in the Security and Privacy system prefs, and unchecked Synergy from the Accessibility list (while it was still running-stupid I know). This immediately soft-locked my mac. The keyboard was non-responsive. The mouse pointer was there, but couldn't do anything on the mac side, it would still go over to the pc, and the win key still worked, but I had to hold the power button to shut the mac down.

On restart I got the security popup saying synergy needs accessibilty settings turned on, so I did that and everything works again as before.

I think there might be some error checking and safety needed around the calls that needs those accessibiltiy security settings.

  • Sad 1
Link to post
Share on other sites
  • 2 months later...

Running Synergy 1 Pro 1.13.0-stable-863f70a5.  Mac 11.1 OS running Synergy server.  Windows and Mac Clients.

All running same version.

Worked fine yesterday and earlier.

Today, no keyboard on either client except Windows key and Control key on Mac.

All systems have been rebooted.

Still not working.

Link to post
Share on other sites
Ing.Fips

had this issue to - one day keyboard worked as a charme, next day it did not 

 

classic solution - 2nd law of support - unplug the device and plug it in again - best practice on a different usb port 

 

worked for me ...

Link to post
Share on other sites

  I have the problem between Win10(64) and Win7(64) It just started happening a few months ago- strange thing is that it worked fine for years ( version 1.10.1 stable)  I paid for 2Pro a few years ago, but I couldn't get that to work right for me, so I went back to what worked.  Mouse is fine, but in the middle of typing something my Client keyboard will just stop.  I can fix it by stopping both and restarting but it's happening quite a few times a day now and that is quite inconvenient.  It isn't just when I'm typing in a browser, but can happen in notepad or whatever. I was going to try upgrading, but it looks like that doesn't work- sighh.  Wish someone would find a fix.

Link to post
Share on other sites
  • 2 weeks later...
bashbang
On 10/9/2020 at 6:36 AM, sandstheman said:

Just to chip in - same problem for me too, was working fine and then a couple days ago keyboard stopped working again. - Tried the latest versions of both Synergy 1 and Synergy 2, currently running Synergy 2 v2.0.12 (beta) on 2 macbooks and windows, one of the macbooks is the server

I had the same issue...just magically this morning the mouse stopped working.  The above fix did the trick on my OSX Server (Synergy Version 1.11.1) connecting to my Win10 (Synergy 1.11.1) client.

Link to post
Share on other sites

Same problem. When mouse is in Windows PC, and I type, the key presses end up on my macOS focused application.

For a while it works, but then it always reverts to this behavior. Worked fine with macOS to macOS.

Link to post
Share on other sites

Running from terminal using `/Applications/Synergy.app/Contents/MacOS/synergys` seemed to fix it for me.

I am guessing its something to do with the way that the Synergy frontend starts the service. The different behavior could be explained by:

- Different environment variables

- Maybe the way the process is started impacts how Accessibility API permissions (`tcc` stuff) works. Maybe the permissions were inherited from the GUI, instead of the service.

Edited by vjpr
  • Thanks 1
Link to post
Share on other sites
wokninja
On 2/15/2021 at 10:49 AM, vjpr said:

Running from terminal using `/Applications/Synergy.app/Contents/MacOS/synergys` seemed to fix it for me.

I just started it this way and this seems to have worked for me as well - hopefully this guides development toward a fix.

Link to post
Share on other sites
  • 2 weeks later...

Key strokes were not sent to Windows 10 client from M1 mac mini (Big Sur 11.2.1). I added Synergy in Security&Privacy->Privacy->Input Monitoring. Now it works fine.

Link to post
Share on other sites
On 2/25/2021 at 10:07 PM, Siva said:

Key strokes were not sent to Windows 10 client from M1 mac mini (Big Sur 11.2.1). I added Synergy in Security&Privacy->Privacy->Input Monitoring. Now it works fine.

Again, not working after couple days. Mouse is working fine. Keystrokes are not sent to Windows 10 client.

Link to post
Share on other sites
  • 1 month later...
Bitwarden was causing the issue in my case.
If Bitwarden is in LOCKED state at server computer, Synergy was not able to get the key strokes in client computer. Once I logged in or Quit the application, Synergy is working fine.
Edited by Siva
  • Thanks 1
Link to post
Share on other sites

Hi all,

Same issue here. In my case however it starts to work again during a day. Didn't find a pattern yet. I have this with quite some versions so far. It's a bit interessting when you post your password to company channels beacuse you think you are typing it on other PC :).

I hope well have some fix for this.

Thanks.

br,

Tomi

Link to post
Share on other sites
Danny Parker

Small addition in case anyone is not aware. There are 2 causes of this that I am aware of:

1. If there is a password entry field open on the Mac server, keypresses will not go over to the Windows client. I'm sure this is intended from a security point of view - but it would be great to have some sort of indicator so we know whats going on, but appreciate that might be unlikely.

2. Unknown. The client stops receiving keypresses the same as though there is a password field open - but there isn't one. See thread for various solutions to this one.

  • Like 1
Link to post
Share on other sites
2 hours ago, Danny Parker said:

Small addition in case anyone is not aware. There are 2 causes of this that I am aware of:

1. If there is a password entry field open on the Mac server, keypresses will not go over to the Windows client. I'm sure this is intended from a security point of view - but it would be great to have some sort of indicator so we know whats going on, but appreciate that might be unlikely.

2. Unknown. The client stops receiving keypresses the same as though there is a password field open - but there isn't one. See thread for various solutions to this one.

It makes sense. I think, it happens only for native applications which uses mac's native password field. In my case, it was Bitwarden which sitting quietly in menu bar and prompting password.

Link to post
Share on other sites
Danny Parker
40 minutes ago, Siva said:

It makes sense. I think, it happens only for native applications which uses mac's native password field. In my case, it was Bitwarden which sitting quietly in menu bar and prompting password.

It happens for me even with webpage password fields in chrome - but it needs to be foregrounded to cause the issue there. My biggest issue has been Chrome Remote Desktop, as the window might be open in the background, but if it gets logged out (as it does from time-to-time) it will show the password to log back in, and as you say, for native apps, it does not need to be in the foreground... queue WTF moment.

  • Like 1
Link to post
Share on other sites
menczingerm

Thanks, it was surly one of my browser window, when i closed the browsers (osx server) the keyboard started to work on client (win 10)

  • Like 1
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...