/usr/lib/chromium/chromium: error while loading shared libraries: libicui18n.so.70: cannot open shared object file: No such file or directory
Since last update, ICU is now at: libicui18n.so.71.1
Git Clone URL: | https://aur.archlinux.org/ungoogled-chromium.git (read-only, click to copy) |
---|---|
Package Base: | ungoogled-chromium |
Description: | A lightweight approach to removing Google web service dependency |
Upstream URL: | https://github.com/ungoogled-software/ungoogled-chromium |
Keywords: | blink browser privacy web |
Licenses: | BSD-3-Clause |
Conflicts: | chromedriver, chromium |
Provides: | chromedriver, chromium |
Submitter: | ilikenwf |
Maintainer: | JstKddng (networkException) |
Last Packager: | networkException |
Votes: | 354 |
Popularity: | 4.36 |
First Submitted: | 2016-12-19 08:08 (UTC) |
Last Updated: | 2024-11-20 21:14 (UTC) |
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 66 Next › Last »
/usr/lib/chromium/chromium: error while loading shared libraries: libicui18n.so.70: cannot open shared object file: No such file or directory
Since last update, ICU is now at: libicui18n.so.71.1
A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit
--disable-features=UseChromeOSDirectVideoDecoder
--enable-hardware-overlays
@fcolecumberri i don't seem to have that flag in my /etc/makepkg.conf file...
the -fvar-tracking-assignments problem can be solved by removing that flag from the /etc/makepkg.conf file (which makes sense since it's a g++ only flag and ungoogled-chromium uses clang++ to compile).
Please bump the package. icu
just got updated.
$ chromium
/usr/lib/chromium/chromium: error while loading shared libraries: libicui18n.so.70: cannot open shared object file: No such file or directory
@monarc99
yeah, it's in chromium's PKGBUILD and I'm trying to maintain this with the least possible changes to it.
@JstKddng
do you need the debug flag in the PKGBUILD?
... options=('debug' '!lto') ...
maybe it is easier to switch to '!debug' than fixing the DEBUG_CFLAGS of all users. ;)
@mrturcot
Have you edited /etc/makepkg.conf accordingly? If so, maybe you have a makepkg.conf file in your home directory somewhere not letting you build.
Yeah no dice it still has same error as before and build fails almost right away after it starts...
Pinned Comments
JstKddng commented on 2022-05-06 14:37 (UTC) (edited on 2022-06-27 13:48 (UTC) by JstKddng)
A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit
JstKddng commented on 2020-07-19 06:34 (UTC)
You can get prebuilt binaries here:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads
seppia commented on 2018-12-12 21:34 (UTC)
Please do NOT flag this package as out of date in relation to official chromium releases.
This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.
Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.
Thanks