-
Notifications
You must be signed in to change notification settings - Fork 225
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
error while loading shared libraries: libiniparser.so #568
Comments
Looks like this https://gitlab.archlinux.org/archlinux/packaging/packages/iniparser/-/commit/11885ca3a924ac52a0329ccf95f8314663f9ebc6 |
could be that the package was changed from providing a .1 to not providing a .1. Try doing a complete reinstall of cava. |
I have the same problem my machine: |
I did try reinstalling before filing here.. error stayed the same. |
I thought maybe that a rebuild would make it search for the library again and find the correct one. I don't think that there is anything in the cava build stuff that makes it look for the .1 link or not the .1 You would have to check with the iniparser arch package maintainer why the .1 was removed and how it is supposed to work now. |
i have the same problem. using arcolinux (arch based) |
Same issue here, Arch + Hyprland |
I thought that the linker would look for did any of you arch people actually clone and build from source? |
Got a fix, simply uninstalled the aur pkg |
nope sorry will do that now |
I can confirm that installing the AUR package |
Describe the bug
When I launch Cava I get following error:
cava: error while loading shared libraries: libiniparser.so.1: cannot open shared object file: No such file or directory
To Reproduce
Steps to reproduce the behavior:
cava
Expected behavior
Cava without error.
Screenshots
Desktop (please complete the following information):
Terminal emulator
Additional context
It was working fine for past 6 months.
Did not use it for few days, when I tried today, I got this issue.
I have
/usr/lib/libiniparser.so
The text was updated successfully, but these errors were encountered: