-
-
Notifications
You must be signed in to change notification settings - Fork 219
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
bug: eza: error while loading shared libraries: libgit2.so.1.7: cannot open shared object file: No such file or directory #819
Comments
i have the same problem here after switching my nixos configs without restart |
What's the output of |
$ uname -a
$ nix-info
|
I can't seem to reproduce this. Did you install from nixpkgs? |
yup, as a system package
I manage my configuration as a flake, and i do have |
I'm not sure, but you could try removing the user package and see if that changes something. Also just to be sure, can you post the command you're running and the error output? |
I did, and that seems to fix the switching issue. But the error appears again when i tried the exact error message:
|
Seems like your store is in a pretty cursed state, specially the no such file or directory errors seem worrying. Have you tried this on another machine? |
I just updated my WSL Ubuntu system (update, upgrade, cargo updates, brew updates, the works), and then found that I was unable to run
eza
. This is onv0.18.0 [+git]
.I generally run either of the following commands, but not even plain
eza
worked:However, every time I tried to run
eza
, I'd get this error:My solution
I tried updating my Ubuntu from 22 to 24.04, but that didn't work. I also reinstalled a few times, checked for clashing dependencies between packages, etc., but nothing seemed to work.
Then I found this old PR: #192 & this comment on an issue on
cargo-update
: nabijaczleweli/cargo-update#243 (comment)After running:
the problem was solved.
So there's no problem for me anymore, but I wanted to ensure people who googled this issue would find a solution. Hope to save you 30 minutes :)
I'm not sure if there's an issue with the latest build or something, given the earlier PR that included
vendored-libgit2
?There must be something I don't know, or haven't set up properly.
If it's just a mistake on my part, feel free to close the issue - the problem is solved, then.
Thanks!
The text was updated successfully, but these errors were encountered: