Something about missing libxml2.so.2

Support AUR
1

Latest version of libxml2 borked my system, something about missing libxml2.so.2 and that causing my display/graphic to be corrupted.

Anyone else experiencing the same? I can only use tty for now

2

Note that I moved your reply from the Unstable Updates thread to it’s own topic.

The only people who have experienced what you have that I’ve seen have been in an unsupported, partial upgrade state. Make sure your mirror list is current and perform an update. See Pacman-mirrors - Manjaro.

1 Like
3

It is unlikely that libxml2 borked your system. The package was updated recently in the unstable branch to 2.14.2. Certain packages or AUR packages may still need the older version (2.13.8), Nordvpn.bin (AUR) required a workaround in the PKGBUILD to accommodate the missing file.
The Arch packagers have released a libxml2-legacy package. That may be an option:
https://archlinux.org/packages/extra/x86_64/libxml2-legacy/

2 Likes
4

I also have issues with libxml2 even though I believe my system is up-to-date, including mirror list.

$ sudo pacman-mirrors --fasttrack && sudo pacman -Syu
...
$ php -v
php: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory
$ yay -S libxml2-legacy
 -> No AUR package found for libxml2-legacy
 there is nothing to do

Also did a system restart between refreshing mirrors and the other commands.

5

This package is not in the AUR. It is in the official Arch repositories. It can be downloaded from the website listed in my earlier post (download from mirror) or from any synced Arch repository (extra) e.g. Index of /pub/archlinux/extra/os/x86_64

1 Like
6

This worked for me. Thanks!

$ wget https://mirror.math.princeton.edu/pub/archlinux/extra/os/x86_64/libxml2-legacy-2.13.8-1-x86_64.pkg.tar.zst
...
$ sudo pacman -U libxml2-legacy-2.13.8-1-x86_64.pkg.tar.zst
$ php -v
PHP 8.3.14

(fyi: currently using php83 instead of php, therefore it doesn’t show PHP 8.4 here)

7

This is an AUR package, it needs to be rebuilt.

1 Like
8

It’s also marked out-of-date.

1 Like
9

I am well aware, and that would’ve been my first try if php83 didn’t have its own problems. One PHP 8.3 module I need currently depends on php81, which is obviously not correct.

I’ll investigate what I can do myself to either contribute to keeping these packages up-to date, or to work around these issues, but that’s a bit too much off-topic for this thread.

10

3 posts were split to a new topic: Automount failing

13

Strange that this problem happened to me last week and I fixed it by installing that legacy package after rox-filer refused to run. Then AGAIN this week the same problem ! Why after I had installed the legacy package repairing the “damage” does it happen yet again. I had to re-install the legacy package. It seems that package is not the real solution to the problem. What is ???

Thanks

14

I don’t think there is a definite answer - take a look at the packages in the repo.

From the listing on unstable branch

pamac search libxml2 --no-aur

It appears that two packages providing

libxml2-legacy 2.13.8-1 in extra repo
libxml2 2.14.3-1 in core repo

libalpm decides which package to install by order of appearance in pacman.conf

Both packages provides libxml2.so but supporting different versions 2-64 vs. 16-64.

You can use pamac or pacman to query the metadata

pamac info <pkgname>

or

pacman -Qi <pkgname>

Please note the Provides and Required By.

Both packages provides level 16 to 64 but only the legacy version provides 2 to 15.

So if you are using a component that requires version 2 to 15 you would go for the legacy version otherwise you stay with the current version.

1 Like