-
Notifications
You must be signed in to change notification settings - Fork 53
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
macOS (aarch64): Installation immediately errors and can't be undone #520
Comments
This is suspicious. Did you perhaps used to have Nix installed? |
A relatively long time ago, from the official installer and I went through a lot of effort to clean up everything after. Thanks for your help btw! |
Can you tell me if I suspect you ran this at some point % sudo launchctl disable system/org.nixos.darwin-store.plist You may be able to enable the service then bootout it? % sudo launchctl enable system/org.nixos.darwin-store.plist
% sudo launchctl bootout system /Library/LaunchDaemons/org.nixos.darwin-store.plist |
The file does not exist, sorry, I should have mentioned that earlier. The bootout fails because the file does not exist:
|
So... is Launchctl failing because we are trying to bootstrap a service which it had previously disabled, but has been removed and entirely recreated? I feel so confused. |
I can relate to that, can't quite wrap my head around what's happening here. |
When I was poking around I was able to list disabled services (even non-existing ones) via
If you run that do you see them disabled? If so, can you run |
We've seen this with the official installer at least once (albeit with nix-daemon) in NixOS/nix#6499 |
If re-enabling the service is indeed the step to take, I think we can write some logic to do that! |
tl;dr: It finally worked. For details on the journey, see below. Thanks @Hoverbear! I re-enabled it but re-running the installer errored out in the exact same way as before. I then also manually removed the service from Interestingly, after the reboot, I also had a Nix volume and was asked for a password for it. I removed the volume, and now the installer fails with
I already ran the command several times, it assures me the password has been deleted:
However, the installer still insists that it already exists. Update: after several tries the password was finally gone for real (in a way the installer liked). I then hit the following problem:
So I performed the suggested clean up actions, re-ran the installer and we're back to square 1:
Update 2: After this failure I re-enabed the service again. I also removed it from |
Oh my goodness that's such a chore, I'm sorry you had to do all that. :( The Part of me wonders if we're being too specific with that command somehow... I'm gonna make a ticket to enable the service if it's disabled, as well as a ticket to revisit the password delete command and see if it's too specific. Thank you for your cooperation investigating this issue! I'm glad we got it working. |
I'm going to close this issue since we have two specific follow ups to address from this. Once those are closed this issue is also fixed of course. |
I suspect that the reason the commands are succeeding is that there's more than one credential matching the invocation from previous install attempts. Edit: I guess it might not be deleting the credential, but I'd rule out duplicates before tilting at that possibility? Edit edit: Since the official installer doesn't remove creds and this user notes that they used it at some point, they may have had multiple credentials from that timeframe instead of from running the detsys installer. It's possible this output is out of date since it's from an older macOS, but I do get an error status if there's no matching credential: $ security delete-generic-password -a "one" -s "two" -l "three" -D "four"; echo $?
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
44 Keeping passwords matched up with volumes is part of why the official shell installer is using the volume UUID in the credential and mounting service definition. |
Error
The offered undo step also fails:
Additional info
/nix
was created:diskutil apfs list
/nix
Metadata
The text was updated successfully, but these errors were encountered: