Open talanb opened 3 weeks ago
Blind guess: put start-at-login = true
in your config
But I don't yet understand what's happening
Thanks for the guess! I updated my config to include start-at-login = true
, restarted my computer and tried to run Aerospace.app and I got the same result.
I'm running into a similar issue, adding start-at-login = true
is causing Aerospace to no longer be able to open until I reinstall it, similar to this https://github.com/nikitabobko/AeroSpace/issues/167
edit: Please lmk if there are any helpful logs I can provide, initially commented during midnight hours and didn't dive too deeply.
I don't think the bootout
line in your log is the problem. There is an unrelated(?) bug that I can't quite articulate yet to raise an issue, where the app tries to 'unload' the launch agent on startup if start-at-login
is false in your config. (which it is in the default config). Both the code to register and unregister the service are broken.
Anyway, that's for another time. Let's see if I can help you debug.
Curiously, the fact aerospace is in your launchd logs means the app bundle is at least executing to a point. (launchd will also manage mac os 'apps' throughout their lifecycle afaik)
Firstly, can you make sure you don't have any existing agents/instances running for aerospace:
In your terminal can you first run:
launchctl list | grep bobko.aerospace
If you don't see anything, great. Otherwise, you might have something that looks like this (could be more than one line):
23465 0 application.bobko.aerospace.89834155.120171650
For each line in the result, take the right hand part and stop the agent with:
# in this case, this is just my running instance, not the startup agent
launchctl stop application.bobko.aerospace.89834155.120171650
That'll make sure there are no agents running, left over from you previously launching.
Next, you can run aerospace from your terminal and if it throws any errors you should get some useful output. (You might need to grant your terminal accessibility permissions and run aerospace again)
/Applications/AeroSpace.app/Contents/MacOS/AeroSpace
You will probably see:
Unload failed: Input/output error
This is the bug I mentioned before, so you can ignore this for now. If the app is crashing I would expect you to see more errors.
As well, how did you install aerospace?
Can I also ask, did you replace some text in your logs with <private>
for privacy reasons or is that how the logs were? My logs of the same error show the path to the plist where yours say
I am unable to launch Aerospace successfully. I've tried it on two different computers (work and home), both running MacOS Sonoma 14.6.1 (23G93).
I am using an unmodified version of the default config at
~/.aerospace.toml
I usually launch using Alfred, but I also tried to open directly from the Finder.
I've included an extract from my launchd.log where Aerospace is trying to start. The error (I think) is
2024-08-20 11:42:58.340459 (gui/502 [100013]) <Notice>: Bootout by launchctl[45675] for <private> failed (2: No such file or directory)
Checklist