Not completely unexpected since I hadn’t updated in a while.
This is what I get
/usr/lib/chromium/chromium: error while loading shared libraries: libxml2.so.2: cannot open shared object file
: No such file or directory
tried reinstalling libxml2 and a couple more unsuccessful devises based on what info I found online.
Some says I have to “rebuild” Chromium. Not sure what that may mean.
Any clues?
One could suspect a partial sync.
I suggest you log out - then switch to a TTY and execute mirror refresh and a full system sync
I have test laptop on stable branch and chromium work just fine.
They’re probably thinking of chrome, which is an AUR package.
chromium — upon which chrome is based — is from the official Manjaro repository, and it works just fine. It’s my default browser and I’m typing this very message with it.
I’m curious where you got that comment; sources are very important. My first reaction was that this is the right answer - generally, if somethign like this happens it’s an AUR package holding up the train - so you can simply remove that sucker and continue upgrading.
However, chromium exists in the ‘extra’ Manjaro repo, also there exist AUR entries for ungoogled-chromium-bin, omarchy-chromium-bin, ungoogled-chromium, chromium-snapshot-bin and chromium-widevine; so please be careful to check exactly what you have.
If you have it from AUR, then purge it and try again - then reinstall later… but best go with the default ‘chromium’ unless you very deliberately chose an alternative.
Don’t mess about… do that first, then you could go with a one-liner to refresh and synchronise… if ‘a while’ is more than a month, maybe keyrings will need tidying up too (will put that later).
⮞ sudo pacman-mirrors --continent && sudo pacman -Syu && pamac upgrade --aur
See how that turns out and paste any terminal output here.
Also be specific about ‘a while’… check pacdiff -o and resolve all issues therein.
sudo pacman -Sy --needed archlinux-keyring manjaro-keyring
sudo pacman-key --populate archlinux manjaro
sudo pacman-key --refresh-keys
sudo pacman -Syu base linux linux-firmware manjaro-system pacman
Thank a lot for your contribution
Good idea especially if it solves it in one clean sweep.
https://bbs.archlinux.org/viewtopic.php?id=305293
I appreciate the advice and I always do it before every major update. I did it before running this one.
Could be even more than three…
So the comment you linked is AUR’s ungoogled chromium, so you need to go back and be clear about what package you actually have installed, because it isn’t chromium - and that’s rather an important detail 
AUR isn’t supported - my advice is to purge anything that messes up the update, then put it back later (hence ‘rebuild’ for the newly synchronised system).
libxml2.so.2 is included in the libxml2-legacy package which is included in the extra repository. Have you tried installing that package?
sudo pacman -S libxml2-legacy
or
pamac install libxml2-legacy
Correct it’s ungoogled chromium.
I repeated the update via TTY and the result was everything fine and up to date. Obviously Chromium is still not working.
While I was at it I got rid of all orphaned packages with sudo pacman -Rs $(pacman -Qtdq) (it was not necessary, just did it… I didn’t remove Chromium though just yet) and run
sudo pacman-mirrors --continent && sudo pacman -Syu && pamac upgrade --aur.
This time it seemed it was actually reinstalling everything from scratch. The process didn’t even go through the end unsurprisingly, it stopped at a point with ==> ERROR: A failure occurred in build(). Aborting...
I tried to run again sudo pacman -Syu here is the outcome
:: Synchronising package databases...
core 147,8 KiB 360 KiB/s 00:00 [####################################] 100%
extra is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (3) systemd-257.8-4 systemd-libs-257.8-4 systemd-sysvcompat-257.8-4
Total Download Size: 12,17 MiB
Total Installed Size: 36,76 MiB
Net Upgrade Size: 0,00 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
systemd-257.8-4-x86_64 10,7 MiB 7,53 MiB/s 00:01 [####################################] 100%
systemd-libs-257.8-4-x86_64 1469,1 KiB 5,24 MiB/s 00:00 [####################################] 100%
systemd-sysvcompat-257.8-4-x86_64 6,7 KiB 106 KiB/s 00:00 [####################################] 100%
Total (3/3) 12,2 MiB 6,20 MiB/s 00:02 [####################################] 100%
(3/3) checking keys in keyring [####################################] 100%
(3/3) checking package integrity [####################################] 100%
(3/3) loading package files [####################################] 100%
(3/3) checking for file conflicts [####################################] 100%
(3/3) checking available disk space [####################################] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
:: Processing package changes...
(1/3) upgrading systemd-libs [####################################] 100%
(2/3) upgrading systemd [####################################] 100%
(3/3) upgrading systemd-sysvcompat [####################################] 100%
:: Running post-transaction hooks...
( 1/14) Creating system user accounts...
( 2/14) Updating journal message catalog...
( 3/14) Reloading system manager configuration...
( 4/14) Reloading user manager configuration...
( 5/14) Updating udev hardware database...
( 6/14) Restarting marked services...
( 7/14) Applying kernel sysctl settings...
( 8/14) Creating temporary files...
( 9/14) Reloading device manager configuration...
(10/14) Arming ConditionNeedsUpdate...
(11/14) Updating the MIME type database...
(12/14) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.189-2-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: '5.15.189-2-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img
==> Starting build: '6.6.101-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect
==> Starting build: '6.6.101-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(13/14) Refreshing PackageKit...
(14/14) Reloading system bus configuration...
I did a reboot after and it is still holding.
What do you mean by
AUR isn’t supported
I tried with sudo pacman -S libxml2 , it says
warning: libxml2-2.14.5-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) libxml2-2.14.5-1
I then tried with
sudo pacman -S libxml2-legacy
and it works, Chromium comes back alive. Reason why I didn’t want to nuke it just yet. Reinstalling it is not fun.
Once again I run sudo pacman -Syu here is the outcome
:: Synchronising package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
there is nothing to do
But I think the system needs some fixing. Any suggestion on where to start?
I could try to run sudo pacman-mirrors --continent && sudo pacman -Syu && pamac upgrade --aur again and see what happens…
Remove that from your system, and everything that depends on it. It messes up the permissions on Arch-based systems.
Yes, you do. It needs to be rebuilt on libxml2. Do not install libxml2-legacy.
An easier alternative is installing the binary ungoogled-chromium-bin package that will not take hours to compile.
ungoogled-chromium-bin have the same issues but will not take hours to compile
Custom packages will almost always require a rebuild after a major update - especially on stable branch.
You should be aware that you need to be on Manjaro unstable branch to be able to use AUR.
Execute the following command - it should provide a similar response - that is - if you want to run custom packages using AUR
$ sudo pacman-mirrors -G
unstable
ungoogled-chromium-bin run fine on unstable branch
Do not replace system libraries with custom packages from AUR - not ever…
Refreshing your mirror list will not provide any changes that affects building custom packages from AUR.
Assuming there is no packaging issues - the following is the recommended approach
sudo pacman-mirrors -aS unstable
sudo pacman -Syu base-devel --needed
git clone https://aur.archlinux.org/ungoogled-chromium
cd ungoogled-chromium
makepkg -iscC
And yes - relying on a package like ungoogled-chromium is a pain - the only way you can remain stable in such case is to create a local (portable) mirror
It could run fine on the unstable branch now, yet it will have the same issue since ungoogled-chromium-bin is a repackaged Arch package of ungoogled-chromium and is prone to the same dynamic linking issues; I was subsbribed to both packages for about 4 years and a lot of comment were and still are error while loading shared libraries: libXXX.so.XXX: cannot open shared object file: No such file or directory
I believe you missed my point - but you are absolute correct…
The point being - whether you choose one over another - to avoid the linked library issues - you will need to use Manjaro unstable branch.
If - by that - you mean someone build the ungoogled-chromium from source then created a package with the result - then you are correct.
You can’t avoid it; you will have less hassle if you use the -bin on the Unstable branch as you said but breakage will happen anyway
It is ungoogled-chromium build in a clean chroot and then repackaged; previously was always an Arch package but built on OpenSuse Build Service (OBS)
well - well - you a nitpicking on phrasing 
must be a language barrier - after all I am from Denmark and you are from Italy 