Just updated RPI-5, unstable, with KDE desktop.
Chromium crashes immediately.
When running from terminal gives:
/usr/lib/chromium/chromium: error while loading shared libraries: libicui18n.so.75: cannot open shared object file: No such file or directory
Tried to install libicui18n.so.75, but it gives
target not found
Any ideas?
ARCH-ARM needs to do a chromium rebuilld. Use firefox or chromium flatpack until they fix things.
Chromium flatpak is now at Version 133.0.6943.141 (Official Build) (64-bit)
Thanks. Chromium flatpak OK, except for webgl aquarium.
I was checking the forum for some good news and then this came up. I recently switched back to RPIOS due to similar problems i had after each and every update. Really want to come back, because arch definitely runs so much faster than this. But things like this makes it discouraging.
As it is also broke on arch-arm hopefully it will get rebuilt pretty soon.
@Sam_Fisher I hope you find a distro that never has any miscues especially after a major upgrade. I have not seen one yet after many, many years and any many distros.
It is not that i am looking for perfection. But every time i give the command “pacman -Syyu” shouldn’t end up with “oh s.hit” type of deal should it 
I was really frustrated with the Qt bug lately which prevented me from using some of my favorite apps. I mean Plasma is Qt. I read somewhere that arch arm was actually maintained by one person. I hope that is not real.
The qt6 bug is not linked to arch. The mesa bug affecting
chromium flatpak is not linked to arch. The electron bug affecting chromium, for example, is unrelated to arch. The only real bug is that after a major update, they forgot to recompile a few packages. In their defense, there aren’t many people involved, and in truth, that’s what happens in a Rolling Release distribution. The forum is there to give answers. Most of the time, reinstalling an old version of a package is enough.
For a quick fix, keep the following files from icu-75 and flac-1.4.3-2
/usr/lib/libicudata.so.75
/usr/lib/libicudata.so.75.1
/usr/lib/libicui18n.so.75
/usr/lib/libicui18n.so.75.1
/usr/lib/libicuuc.so.75
/usr/lib/libicuuc.so.75.1
/usr/lib/libFLAC.so.12
/usr/lib/libFLAC.so.12.1.0
You’ll find the icu and flac packages in /var/cache/pacman/pkg or in the arm-testing repo
Looks like v134 is in the works for arch-arm at the moment.
diff --git a/extra/chromium/.SRCINFO b/extra/chromium/.SRCINFO
index 1c069a2cf..ba059532d 100644
--- a/extra/chromium/.SRCINFO
+++ b/extra/chromium/.SRCINFO
@@ -1,6 +1,6 @@
pkgbase = chromium
pkgdesc = A web browser built for speed, simplicity, and security
- pkgver = 133.0.6943.141
+ pkgver = 134.0.6998.35
pkgrel = 1
url = https://www.chromium.org/Home
arch = x86_64
Chromium_133.0.6943.141 has not been release on arch-arm as far as I can tell.
No it has not. I keep a local clone here of their PKGBUILDS and do a pull every day. A lot of times they change versions and it never makes it to their mirrors for what ever reason. v134.0.6998.35 may not make it to the mirrors also as it has been a couple of days and I have not seen any progress with it also. Guessing there are issues with it. The new firefox came out the same day they updated it’s PKGBUILD.
Thanks for the info.
Ok there was some mistake on the archlinux arm forum post, here is an easy to follow version of it:
###Download the package:
curl -LO http://tardis.tiny-vps.com/aarm/repos/2025/03/01/aarch64/core/icu-75.1-2-aarch64.pkg.tar.xz
###Create a temporary folder:
mkdir -p icu
###Extract the package:
tar -xf icu-75.1-2-aarch64.pkg.tar.xz -C icu
###Copy the icu 75.1 libraries to the system directory:
sudo cp icu/usr/lib/libicu*75.1 /usr/lib/
###Create symlinks for icu 75.1 to 75:
for file in /usr/lib/libicu*.so.75.1; do
sudo ln -s "${file}" "${file/75.1/75}"
done
###Create a symlink for libFLAC:
sudo ln -s /usr/lib/libFLAC.so.14 /usr/lib/libFLAC.so.12
###Clean up the downloaded files:
rm -rf icu-75.1-2-aarch64.pkg.tar.xz icu
###Once the problem is solved (a new update to chromium will possibly make this fix unnecessary), you can delete the files you added with the following command:
sudo rm /usr/lib/libicu*75 /usr/lib/libicu*75.1 /usr/lib/libFLAC.so.12
In addition to this fix, for Chromium to not crash due to Manjaro using 16k kernel, you need to enter the following flag into the chromium-flags.conf file that you created in your $home/.config/ directory. You can enter more than one flag into this file, one line per flag:
--js-flags="--no-decommit-pooled-pages"
If you can’t see anything in WebGL Aquarium, then you need to also enter
--use-angle=gles
into the chromium-flags.conf file. This could be for X11 only, i do not use wayland so i am not sure about that. Try and see.
With this and the latest unstable update, the problems with chromium appear to have gone. Even the fishes are OK. Thanks.
Running KDE Plasma on an RPI5
Why is it taking so long for the chromium to be updated?
They can not get it to build.
Coffee-Bread-Bill had managed to build chromium_v134 and have tested it is working but unfortunately I think v4l2-request had not be enabled in this build.
Here is the pre-build chrome from latest arch, the full makepkg setup with all patches, build log (lol), and screenshot showing it running: Browsers – Google Drive
I didn’t try to patch in any extra features, but you now have a working chrome 134 base to try to patch them in whoever wanted to add video related patches.
Edit: Additional info.
https://archlinuxarm.org/forum/viewtopic.php?f=15&t=17210&p=73476&hilit=chromium+build+chromium#p73476
So if anyone is interested, i can tell you how to enable chromium sync and also widewine support for the flatpak version of chromium. It took me some time but i have figured it out. You can also use your already available “chromium-flags.conf” file for the flatpak version easily.
@Sam_Fisher I am interested.
Chromium is now 136.0.7103.59 in flatpak.