-
Notifications
You must be signed in to change notification settings - Fork 57
Immediately Stopped Working After Launch #35
Comments
Can you download the most recent version with full error logging from here, and then paste the output you get after launching it. Make sure to click 'Stop the Background Agent & Quit' before running the new version. |
You cannot run the app under a non-admin account, this is expected behavior, although I guess I could make the error message more informative. |
Updated the docs: ef4c552 |
To anyone who's having this issue and really doesn't want to run with a admin account, you can add the user to the wheel group |
@timeartist careful, that effectively makes your user part of the admin group, and gives them admin read permissions to a lot of things in the filesystem. I don't recommend adding yourself to wheel just to run this app, as it defeats the purpose of running a non-admin account in the first place. The |
I noticed that later as well. Thanks for the info
…On Thu, Jan 26, 2017, 13:33 Nick Sweeting ***@***.***> wrote:
@timeartist <https://github.com/timeartist> careful, that effectively
makes your user part of the admin group, and gives them admin read
permissions to a lot of things in the filesystem. I don't recommend adding
yourself to wheel just to run this app, as it defeats the purpose of
running a non-admin account in the first place. The sudo chmod 644
/var/log/system.log should be enough on it's own to allow your non-admin
account read access.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD-OA8NFqydb741p_e-rDa7fGGD3CZ-lks5rWRE9gaJpZM4Ikh4F>
.
|
Hello,
I've got this message on my notification panel:
Stopped Watching Sources @ 14:20 IOError
Do I need to do a further tweak in order to make it run on my OS 10.11.3?Thanks.
Faxo
The text was updated successfully, but these errors were encountered: