Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Leaderboard

Popular Content

Showing content with the highest reputation on 02/16/21 in all areas

  1. 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.
    1 point
×
×
  • Create New...