Package Details: iridium-rpm 96.0-4

Git Clone URL: https://aur.archlinux.org/iridium-rpm.git (read-only, click to copy)
Package Base: iridium-rpm
Description: Iridium browser - rhel/centos build altered for arch
Upstream URL: https://iridiumbrowser.de/
Licenses: BSD
Conflicts: chromium, iridium
Provides: iridium
Submitter: necklace
Maintainer: necklace
Last Packager: necklace
Votes: 14
Popularity: 0.129046
First Submitted: 2020-01-27 21:01 (UTC)
Last Updated: 2022-02-20 10:27 (UTC)

Latest Comments

lupo2010 commented on 2022-02-28 08:55 (UTC)

@necklace Problem solved with the last update on manjaro, thank you.

necklace commented on 2022-02-21 11:30 (UTC) (edited on 2022-02-21 11:46 (UTC) by necklace)

@lupo2010 Manjaro has not updated their x264 package to 164, they are still on 163: https://discover.manjaro.org/package/x264

In your case the main manjaro ffmpeg package is still on 4.4.1 (https://discover.manjaro.org/package/ffmpeg) whereas the arch main ffmpeg package is on 5.0 (which is why this package now depends on ffmpeg4.4, a different package).

A quick fix for you is to either edit the PKGBUILD to use ffmpeg instead of ffmpeg4.4 or switch to manjaro unstable.

Perhaps I could make some sort of conditional dependency; either ffmpeg so long as the version is 4.4 or ffmpeg4.4, I'll see what I can do.

lupo2010 commented on 2022-02-20 23:56 (UTC)

@necklace Hello, I can't update. I have this:

could not satisfy dependencies: - unable to satisfy dependency 'libx264.so=164-64' required by ffmpeg4.4 - unable to satisfy dependency 'ffmpeg4.4' required by iridium-rpm

baldric commented on 2022-02-20 22:45 (UTC)

@necklace @CodeWithAlex Thank you! Just updated and it started right up!

necklace commented on 2022-02-20 10:31 (UTC)

@baldric @CodeWithAlex Aha, so it was a side-effect as I had ffmpeg4.4 installed without knowing about it.

I've added ffmpeg4.4 as a dependency and patched to major versions.

Hopefully it works for everyone now!

CodeWithAlex commented on 2022-02-20 02:44 (UTC)

@baldric

The problem for me is that I have libavcodec.so version 59 installed as the default.

What worked for me is to fix it in the PKGBUILD:

patchelf "${pkgdir}/usr/lib/chromium/chrome" --replace-needed "libavcodec.so.58.134" "libavcodec.so.58"
patchelf "${pkgdir}/usr/lib/chromium/chrome" --replace-needed "libavformat.so.58.76" "libavformat.so.58"
patchelf "${pkgdir}/usr/lib/chromium/chrome" --replace-needed "libavutil.so.56.70" "libavutil.so.56"

These files are provided by the ffmpeg4.4 package

baldric commented on 2022-02-19 20:19 (UTC) (edited on 2022-02-19 20:20 (UTC) by baldric)

Thank you @necklace. I ran the upgrade and got this: warning: could not get file information for usr/lib/libavcodec.so.58.134, also libavformat.so.58.76 and libavutil.so.56.70

I restarted and ran iridium and it failed with: /usr/bin/iridium: /usr/lib/libavformat.so: version 'LIBAVFORMAT_58' not found (required by /usr/bin/iridium) /usr/bin/iridium: /usr/lib/libavcodec.so: version 'LIBAVCODEC_58' not found (required by /usr/bin/iridium) /usr/bin/iridium: /usr/lib/libavutil.so: version 'LIBAVUTIL_56' not found (required by /usr/bin/iridium) (edit for formatting)

necklace commented on 2022-02-18 19:50 (UTC) (edited on 2022-02-18 19:51 (UTC) by necklace)

@baldric Normally I would just symlink the missing library (in the previous PKGBUILD I symlinked libavcodec.so.58.134 to libavcodec.so.58.134.100), but in this instance - since it is a major version upgrade, even if I do that it complains with /usr/lib/libavformat.so.58.76: version 'LIBAVFORMAT_58' not found.

So instead, I have patched the binary using patchelf to use libavcodec.so instead of libavcodec.so.58.134 (and the same for libavformat and libavutil).

It works for me now, hopefully that isn't a side effect of some other testing I did, give me a heads up if it doesn't work!

baldric commented on 2022-02-18 19:24 (UTC)

Getting this since yesterday (Feb 17): "/usr/bin/iridium: error while loading shared libraries: libavcodec.so.58.134: cannot open shared object file: No such file or directory". This SO is provided by dependency package ffmpeg, which was updated yesterday and no longer provides libavcodec.so.58, now it's on to so.59. Is this something we fix ourselves or does the packager fix it? I tried downgrading ffmpeg per Pacman wiki but I hit a dependency snag right away. I'm on Arch. Thank you.

baldric commented on 2022-01-08 20:32 (UTC)

Thank you!

lupo2010 commented on 2022-01-08 20:31 (UTC) (edited on 2022-01-08 20:33 (UTC) by lupo2010)

@necklace I confirm it's worked on my old laptop thursday (but 10 minutes to build) and when I tried to build it in my current laptop yesterday I had this failed checksum (both on manjaro).

necklace commented on 2022-01-08 19:44 (UTC)

It's really weird - almost suspect - that they would change the file after publishing it and keep the same filename. The previous hash was working when I pushed on Thursday.

lupo2010 commented on 2022-01-08 15:32 (UTC)

@DrJ thank you it solved the checksum error and installed iridium without problem.

DrJ commented on 2022-01-08 14:09 (UTC)

Fix for checksum error: If you change the PKGBUILD file and set the correct checksum the installation finishes smoothly.

For 2021.12.96.0 the checksum needs to be: 41a7256fefa04f0fec0f80ea4839bc4478aa285a643609aa65c5b38617f610fd

Source: Repository description (https://downloads.iridiumbrowser.de/openSUSE_Leap_15.3/repodata/13b27882749c6eca6e85bce2a1df1c790436414bfae2bcc854e65aa3a5f79541-primary.xml.gz)

baldric commented on 2022-01-07 20:59 (UTC)

I am also getting the failed validity check error. I'm on Arch.

lupo2010 commented on 2022-01-07 09:14 (UTC)

Hello, thanks for the update. But I can't build the package with pamac ( I am on manjaro). I have this :

Building iridium-rpm... ==> Making package: iridium-rpm 96.0-1 (ven. 07 janv. 2022 10:05:33) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found iridium-browser-2021.12.96.0-bp153.1636.1.x86_64.rpm ==> Validating source files with sha256sums... iridium-browser-2021.12.96.0-bp153.1636.1.x86_64.rpm ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build iridium-rpm

Rajalolxd commented on 2021-12-06 19:46 (UTC)

missing deps: snappy, minizip

necklace commented on 2021-11-10 12:54 (UTC) (edited on 2021-11-10 12:54 (UTC) by necklace)

Version 2021.10 is out, but they built the Tumbleweed version with GLIBC 2.34 which Arch doesn't have for whatever reason (it has 2.33).

Used the Leap version as source instead, though that one didn't have the iridium-browser command, so I temporarily symlinked it to the iridium command. At least the harfbuzz 2.9.1 dependency is gone now.

necklace commented on 2021-09-28 21:39 (UTC) (edited on 2021-09-28 21:40 (UTC) by necklace)

@DrJ: Welp, that's fun. Thanks for notifying me.

Here's what I've done to temporarily fix it:

Works for me™, tell me if it doesn't work for you guys.

Hopefully a build built on 3.0.0 is released soon.

DrJ commented on 2021-09-25 08:59 (UTC) (edited on 2021-10-01 19:17 (UTC) by DrJ)

Edit:

The problem described here has been addressed by the recent version in AUR. (Thank you very much for that, necklace!) I can confirm that an upgrade to iridium-rpm 91.0-4 resolves the problem.

Originial posting:

A recent update included the harfbuzz libraries (note the plural) being upgraded from 2.9.1 to 3.0.0. That broke iridium. A symbol was missing:

/usr/lib64/chromium/chromium: symbol lookup error: 
/usr/lib64/chromium/chromium: undefined symbol: hb_subset_input_set_retain_gids

Following the discussion here: https://bbs.archlinux.org/viewtopic.php?pid=1994511#p1994511

I managed to fix it by downloading the packages harfbuzz and harfbuzz-icu in version 2.9.1 (https://archive.archlinux.org/packages/h/harfbuzz/harfbuzz-2.9.1-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/h/harfbuzz-icu/harfbuzz-icu-2.9.1-1-x86_64.pkg.tar.zst) and extracted the contents of its lib folders to a separate folder ($HOME/opt/harfbuzz-2.9.1).

Using LD_LIBRARY_PATH fixed the problem.

LD_LIBRARY_PATH=$HOME/opt/harfbuzz-2.9.1 iridium

One could also suggestion in the thread quoted above and downgrade harfbuzz by the help of pacman but I preferred keeping the old version along with the current one.

Just my 5 cts.

foobaz commented on 2021-07-29 07:11 (UTC)

Please add re2 to depends. The browser does not launch without it.

frcl commented on 2021-07-20 07:10 (UTC)

The package is now in conflict with chromium from extra. Consider adding that to conflicts.

DrJ commented on 2021-07-17 08:46 (UTC)

I encountered an error message saying that libpipewire-0.3.so was missing. That was resolved by installing pipewire 0.3 manually.

Furthermore the executable is now called irdium instead of iridium-browser.

necklace commented on 2021-04-08 23:16 (UTC)

@MagusZ After some testing I've found some problems

  • The Leap_15.2 build doesn't work at all, crashes with undefined symbol after manually having to symlink some .so files
  • The Tumbleweed build works after manually symlinking some .so files, but it doesn't uninstall the previously installed version and uses "iridium" (symlinked to "chromium") in the command line instead of "iridium-browser", it also uses /usr/lib/chromium instead of /usr/lib/iridium-browser. So now we get both 88 and 85 (if you had 85 installed previously).

So I'm not really sure what to do, sure we could hack together a solution that creates the necessary symlinks and moves chromium/ to iridium-browser/ but if a fedora build is in the pipeline I'd personally wait for that.

It also uses pipewire, so that's a new dependency, but I'm guessing chromium uses that by default now.

MagusZ commented on 2021-04-07 22:13 (UTC)

There's a new build that is based off of Chromium 88, but its only for OpenSUSE. Would this package be updated for that or would it still strictly stick to the Fedora/CentOS builds?

frcl commented on 2021-02-26 11:51 (UTC)

@benvosper I had the same problem and "--use-gl=desktop" made it worse for me. I had more luck with creating some symlinks to the egl libs:

# ln -s /usr/lib/iridium-browser/swiftshader/libEGL.so /usr/lib/iridium-browser/libEGL.so
# ln -s /usr/lib/iridium-browser/swiftshader/libGLESv2.so /usr/lib/iridium-browser/libGLESv2.so

Seems that iridium is looking for those in the wrong place.

benvosper commented on 2020-12-07 12:19 (UTC)

If anyone's having issues with hardware acceleration using the new Chromium 85 version despite using the "Override software rendering list" flag enabled, I've found I can enable it again by adding "--use-gl=desktop" to /etc/iridium-browser/iridium.default.

Without that flag, chrome://gpu/ just said "gpu-compositing" was disabled. With it on, everything works fine.

necklace commented on 2020-04-18 22:34 (UTC)

Thanks, @stavrakis. Should be fixed now.

stavrakis commented on 2020-04-18 22:13 (UTC)

Needs to be updated for the 2020.04.80-1 release as the source is no longer at this URL.

tom commented on 2020-03-13 21:40 (UTC)

works, thanks!

necklace commented on 2020-03-13 18:12 (UTC)

Thanks, @tom. Seems they removed the previous v78 build when they released v79 for some reason. I do notice a v80 build there as well though, so I decided to use that, though that might also disappear.

tom commented on 2020-03-11 23:44 (UTC)

:: Parsing SRCINFO (1/1): iridium-rpm ==> Erstelle Paket: iridium-rpm 78.0-1 (Do 12 Mär 2020 00:39:53 CET) ==> Empfange Quellen... -> Lade iridium-browser-2019.11.78-1.el8.x86_64.rpm herunter... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found ==> FEHLER: Fehler beim Download von https://downloads.iridiumbrowser.de/epel8/iridium-browser-2019.11.78-1.el8.x86_64.rpm Breche ab... Error downloading sources: iridium-rpm

necklace commented on 2020-01-27 21:18 (UTC)

Since the .deb release for iridium is over a month late, I've made this experimental package using the .rpm release instead.

I haven't tested it entirely, and I might need to add some dependencies (though it worked out of the box for me™), but at least it's "up to date" (in quotes, since latest chrome version is already 79).

You might still probably need to do some sort of fix by setting kernel.unprivileged_userns_clone, see https://aur.archlinux.org/packages/iridium-deb/ Do note that doing this is a security risk, as is continuing to use an outdated browser.

To be honest I've actually given up and switched to firefox. You can get it close-ish to chrome with a bunch of user.js tweaks. Or you could use ungoogled-chromium if you like compiling or you trust the binary builds at https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/archlinux/