FS#74496 - libvterm01 incorrect library path causing neovim failing to run
Attached to Project:
Community Packages
Opened by Letu Ren (FantasqueX) - Monday, 18 April 2022, 16:25 GMT
Last edited by Daniel M. Capella (polyzen) - Monday, 18 April 2022, 23:51 GMT
Opened by Letu Ren (FantasqueX) - Monday, 18 April 2022, 16:25 GMT
Last edited by Daniel M. Capella (polyzen) - Monday, 18 April 2022, 23:51 GMT
|
Details
Description:
After upgrading libvterm01 to 0.1.4-2 and neovim to 0.7.0-2, neovim failed to start due to `nvim: error while loading shared libraries: libvterm.so.0: cannot open shared object file: No such file or directory` . I realized it is because libvterm01 transfer libvterm.so.0 to usr/lib/libvterm01/ and ld cannot find the library. A temporary solution for fish user is `set -x LD_LIBRARY_PATH /usr/lib/libvterm01/`. Adding the new library path to ld library path in PKGBUILD can solve this problem permanently. |
This task depends upon
Closed by Daniel M. Capella (polyzen)
Monday, 18 April 2022, 23:51 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in https://github.com/archlinux/svntogit-co mmunity/commit/2ded2c67f0add06262bd77916 96c6edaca9d2f7e and moved out of testing
Monday, 18 April 2022, 23:51 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in https://github.com/archlinux/svntogit-co mmunity/commit/2ded2c67f0add06262bd77916 96c6edaca9d2f7e and moved out of testing
The situation emerged due to my attempt at fixing https://bugs.archlinux.org/task/74492.
Unfortunately both libvterm and libvterm01 provide libvterm.so.0, which can not coexist in /usr/lib.
Please check whether neovim 0.7.0-3 in [community-testing] fixes this for you. It uses patchelf to hack in an rpath for /usr/lib/libvterm01.
Note: A global override in /etc/ld.so.conf.d/ would also apply to all other software on the system, which is unfortunately counterproductive, too.