bug-When I update nix - with nixos rebuild switch --flake

Help
1

please help me
when i want to upgrade my system i got this error
today i use nix flake update and still i got this error
thanks :pray::smiling_face_with_tear:



terminating due to unexpected unrecoverable internal error: Assertion ‘result == ecSuccess || result == ecFailed || result == ecNoSubstituters’ failed in nix::Goal::Done nix::Goal::amDone(ExitCode) at ../build/goal.cc:204
Nix crashed. This is a bug. Please report this at https://github.com/NixOS/nix/issues with the following information included:

std::terminate() called without exception
Stack trace:
0# 0x00000000001124AE in nix
1# 0x00000000000C539A in /nix/store/chqq8mpmpyfi9kgsngya71akv5xicn03-gcc-15.2.0-lib/lib/libstdc++.so.6
2# std::unexpected() in /nix/store/chqq8mpmpyfi9kgsngya71akv5xicn03-gcc-15.2.0-lib/lib/libstdc++.so.6
3# 0x00000000000E92EF in /nix/store/a90px0h1szz9y9c67ww1sa163z44flf9-nix-util-2.34.7/lib/libnixutil.so.2.34.7
4# \__wrap___assert_fail in /nix/store/yxb9ryjd5nrkjyisq612laz9w23s900b-nix-store-2.34.7/lib/libnixstore.so.2.34.7
5# 0x00000000000BD59C in /nix/store/yxb9ryjd5nrkjyisq612laz9w23s900b-nix-store-2.34.7/lib/libnixstore.so.2.34.7
6# 0x00000000001B5A0E in /nix/store/yxb9ryjd5nrkjyisq612laz9w23s900b-nix-store-2.34.7/lib/libnixstore.so.2.34.7
7# nix::Goal::work() in /nix/store/yxb9ryjd5nrkjyisq612laz9w23s900b-nix-store-2.34.7/lib/libnixstore.so.2.34.7
8# nix::Worker::run(std::set<std::shared_ptr<nix::Goal>, nix::CompareGoalPtrs, std::allocator<std::shared_ptr<nix::Goal> > > const&) in /nix/store/yxb9ryjd5nrkjyisq612laz9w23s900b-nix-store-2.34.7/lib/libnixstore.so.2.34.7
9# nix::Store::buildPathsWithResults(std::vector<nix::DerivedPath, std::allocator<nix::DerivedPath> > const&, nix::BuildMode, std::shared_ptr<nix::Store>) in /nix/store/yxb9ryjd5nrkjyisq612laz9w23s900b-nix-store-2.34.7/lib/libnixstore.so.2.34.7
10# nix::Installable::build2(nix::ref<nix::Store>, nix::ref<nix::Store>, nix::Realise, std::vector<nix::ref<nix::Installable>, std::allocator<nix::ref<nix::Installable> > > const&, nix::BuildMode) in /nix/store/2cv1nsfm7xqlscdi13zbb6cz623brgr0-nix-cmd-2.34.7/lib/libnixcmd.so.2.34.7
11# nix::Installable::build(nix::ref<nix::Store>, nix::ref<nix::Store>, nix::Realise, std::vector<nix::ref<nix::Installable>, std::allocator<nix::ref<nix::Installable> > > const&, nix::BuildMode) in /nix/store/2cv1nsfm7xqlscdi13zbb6cz623brgr0-nix-cmd-2.34.7/lib/libnixcmd.so.2.34.7
12# 0x0000000000103A0E in nix
13# nix::InstallablesCommand::run(nix::ref<nix::Store>, std::vector<std::\__cxx11::basic_string<char, std::char_traits, std::allocator >, std::allocator<std::\__cxx11::basic_string<char, std::char_traits, std::allocator > > >&&) in /nix/store/2cv1nsfm7xqlscdi13zbb6cz623brgr0-nix-cmd-2.34.7/lib/libnixcmd.so.2.34.7
14# nix::RawInstallablesCommand::run(nix::ref<nix::Store>) in /nix/store/2cv1nsfm7xqlscdi13zbb6cz623brgr0-nix-cmd-2.34.7/lib/libnixcmd.so.2.34.7
15# nix::StoreCommand::run(nix::ref<nix::StoreConfig>) in /nix/store/2cv1nsfm7xqlscdi13zbb6cz623brgr0-nix-cmd-2.34.7/lib/libnixcmd.so.2.34.7
16# virtual thunk to nix::StoreConfigCommand::run() in /nix/store/2cv1nsfm7xqlscdi13zbb6cz623brgr0-nix-cmd-2.34.7/lib/libnixcmd.so.2.34.7
17# 0x000000000019FADB in nix
18# nix::handleExceptions(std::\__cxx11::basic_string<char, std::char_traits, std::allocator > const&, nix::fun<void ()>) in /nix/store/a90px0h1szz9y9c67ww1sa163z44flf9-nix-util-2.34.7/lib/libnixutil.so.2.34.7
19# 0x00000000000E1A0B in nix
20# 0x000000000002B285 in /nix/store/57iz36553175g3178pvxjij8z5rcsd4n-glibc-2.42-61/lib/libc.so.6
21# \__libc_start_main in /nix/store/57iz36553175g3178pvxjij8z5rcsd4n-glibc-2.42-61/lib/libc.so.6
22# 0x00000000000E6675 in nix

Command ‘nix --extra-experimental-features ‘nix-command flakes’ build --print-out-paths ‘/etc/nixos#nixosConfigurations.“nixos”.config.system.build.toplevel’ --no-link’ died with <Signals.SIGABRT: 6>.
2

If you roll back the changes to your lockfile, can you build again then?

When using build with the updated lockfile does it work? Does using --fast change anything?

Is your flake public to maybe reproduce your issue?

2 Likes
3

It tells you what do with this info, right?

But yes, you should share your flake.nix and flake.lock at least.

1 Like
4

Thank you for asking the right questions! Your second question actually made me think about deleting the flake.lock file entirely to see if it would fix the issue.

Fortunately, that did the trick. It turns out Nix was falsely reporting this as an internal bug/crash, but after removing the flake.lock file completely and avoiding nix flake update, the fresh generation and download went through without any issues.

I have also reported this on GitHub to help others who might run into this weird behavior. Thanks again for your help!

5

Thanks for the reply!

I actually reported this issue on GitHub before posting here. Fortunately, as I mentioned, Nobbz second question prompted me to completely delete the flake.lock file instead of relying on nix flake update, and that luckily resolved the crash.

I usually always use nix flake update without any issues, but this time it somehow got stuck in that weird state.

Since the issue is now fully resolved, I have updated and closed my GitHub issue. Here is the link to it for reference:

6

It would have been better to share the flake.lock like we asked before deleting it, so it’d be possible to confirm if there was a bug here.

2 Likes
7

Thanks for the tip! You’re totally right. Next time I report an issue, I’ll make sure to share the files or link my GitHub repository beforehand so it can be properly debugged. I appreciate your guidance!