-
-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service fails to install if ~/Library/LaunchAgents doesn't exist #1728
Comments
Fairly certain this folder will always exist unless a user has specifically decided to delete it, in which case I think failing is better than recreating it. |
It didn't exist after a fresh install of macOS, which is why I filed this issue since I had to dig in to figure out why it wasn't working since the error message wasn't very intuitive. I can definitely see where you're coming from though, so feel free to close this if you want to leave things as is. |
I assumed it would always be there (even after a fresh install) when reading Apple documentation, but as you pointed out that appears to not be the case. I've changed the implementation on master to attempt to create the I am not going to push a new release just for this change though. |
Thanks for reporting this, I ran into this issue just now on a fresh install. |
Sorry for necro, but adding on to the solution: If the directory did not exist, and the user had created it manually (as in my case), the permissions would not allow the process to write to the directory. This can be fixed with a simple I encoutered this issue with skhd, but these appear to have the same impl, so I'm leaving my comment here. Cheers |
This issue seems to be because the plist path is opened without checking if the directory exists:
yabai/src/misc/service.h
Lines 96 to 97 in f4ad453
I believe the user experience here could be a bit better. I can make a PR for this when I get the chance, but I'm filing this issue in case someone can get to it before I do.
The same issue predictably exists for skhd.
The text was updated successfully, but these errors were encountered: