Randolph Williams 0 Posted February 27, 2017 Author Share Posted February 27, 2017 Sorry if this has been addressed, I looked and couldn't find anything that could help. So, I have my main computer that is the server for my keyboard and mouse. The client is my secondary. On the client everything works well enough, however, when I'm on the client and change to a different user, I have no access to the synergy app. The app icon is greyed out and a line through it. I tried giving everyone permission to read/write the app in 'Get Info' to no avail. Is there anything I can do to use Synergy while on my other accounts?  Thanks  Steve Link to post Share on other sites
Randolph Williams 0 Posted February 27, 2017 Author Share Posted February 27, 2017 Thank you, I tried that. After asking for my password it went back to a normal prompt. I logged into the other account and tried to open Synergy and got an error that reads 'You can't open the application "Synergy" because it may be damaged or incomplete. Link to post Share on other sites
dawnrae 0 Posted April 24, 2017 Share Posted April 24, 2017 I have this same issue. I too tried changing permissions on the app and get the same message. I am able to use it in one user account but not the other. Any suggestions of things I can try or a solution is welcome. Link to post Share on other sites
dawnrae 0 Posted May 6, 2017 Share Posted May 6, 2017 Any chance of ever getting an answer on this? I still have this problem Link to post Share on other sites
Sanergy 0 Posted May 9, 2017 Share Posted May 9, 2017 I was able to do this by installing the Synergy app into the applications folder again on the second user and clicking 'keep both' when prompted. This then had a Synergy.app and Synergy 2.app in the applications folder and each account used a seperate one and worked when switching users Link to post Share on other sites
Jacob W 0 Posted June 6, 2017 Share Posted June 6, 2017 (edited) I ran into this problem and solved it by changing the file permissions of the app to match those of other apps. If you open the terminal window and do the following: cd /Applications sudo chown -R root:wheel Synergy.app/ sudo chmod +a "everyone deny delete" Synergy.app/ sudo chmod -R 755 Synergy.app/ This sets the same permissions as Apple's built in apps and with these I was able to run Synergy across multiple accounts on my Mac. If you then add the synergy app to the users Login Items there is no downtime when switching between users. Edited June 6, 2017 by Jacob W Correctly named the Login Items Link to post Share on other sites
Paul Suarez 107 Posted June 29, 2017 Share Posted June 29, 2017 On 6/7/2017 at 5:59 AM, Jacob W said: I ran into this problem and solved it by changing the file permissions of the app to match those of other apps. If you open the terminal window and do the following: cd /Applications sudo chown -R root:wheel Synergy.app/ sudo chmod +a "everyone deny delete" Synergy.app/ sudo chmod -R 755 Synergy.app/ This sets the same permissions as Apple's built in apps and with these I was able to run Synergy across multiple accounts on my Mac. If you then add the synergy app to the users Login Items there is no downtime when switching between users. Thanks for sharing this @Jacob W. Can you verify what macOS version you are using? Link to post Share on other sites
Jacob W 0 Posted June 29, 2017 Share Posted June 29, 2017 On 06/06/2017 at 10:59 PM, Jacob W said: I ran into this problem and solved it by changing the file permissions of the app to match those of other apps. If you open the terminal window and do the following: cd /Applications sudo chown -R root:wheel Synergy.app/ sudo chmod +a "everyone deny delete" Synergy.app/ sudo chmod -R 755 Synergy.app/ This sets the same permissions as Apple's built in apps and with these I was able to run Synergy across multiple accounts on my Mac. If you then add the synergy app to the users Login Items there is no downtime when switching between users. This is on macOS 10.12.5. Link to post Share on other sites
Rick Buford 0 Posted February 17, 2019 Share Posted February 17, 2019 Sorry to necro an old thread, but this solution appears to have corrected the same problem that suddenly started on a MBP running Mojave after working correctly for several weeks. 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