There is an official github repo for the Arch PKGBUILD and an AUR package, but building ungoogled-chromium can take a long time on average or old hardware, which is why an official package would be highly appreciated.

ungoogled-chromium is what I would consider an essential piece of software, as it is the only project offering a privacy respecting version of Chromium without the attempt to create just another Chromium-based browser.


there's a -bin aur package.



...there is also a private repo:


[ungoo] Server = https://arch.scrumplex.net/$repo/os/x86_64

More info here

this saves you from compiling

1 Like

@steanne and @banjo

I'm hesitant on using third-party binaries and would rather build it myself, but that's why I was suggesting an official binary package with would make so much more sense.

To be more precise about the original intent, the PKGBUILD from jstkdng's fork at github is what I'm currently more interested in because it includes the VA-API patch for hardware acceleration.

Adding another browser to the repos is a lot of work.

I don't use it, so it's a "no" from me.

1 Like

Read your own link, the guy has a private repo.

You can also use my repository. I added some additional patches and I try to update this as soon as Eloston releases a new version. To use it first import my gpg key to your pacman keyring:

$ sudo pacman-key -r 3DEA62513C8035383A245A12E5786B42E8E5D565 $ sudo pacman-key --lsign-key 3DEA62513C8035383A245A12E5786B42E8E5D565

And edit your /etc/pacman.conf adding this lines:

Server = https://repo.vin.ovh/arch/$arch


1 Like

Isnt that some unrelated person who forked it ?

Is Ungoogled Chromium a better solution than Brave, which did make it into the community repo after one user complained?

I don't use Brave, I don't package it, and personally I wouldn't have added it to the repos, but that's me. I have opinions of my own. Just because I say "I won't package this" doesn't mean someone else won't.

However, Brave is a binary package so it requires no compilation time so at least it's quicker to package for the repos.

This is also part of a wider discussion about a fourth "non-free" (or similarly named) repo for binary packages like Brave, Sublime Text, FreeOffice, etc.


Well, it's not a TU.

No .. I meant that git repo is forked from the actual project. The author/maintainer of that fork has 1 or 2 other projects on github, but is not related to ungoogled-chromium in any way (as far as I can tell) .. they forked it and added that text about their personal repo .. but its just 'some dude' .. its not ungoogled authors repo.

To be trustable, jstkdng recently uses "openSUSE's obs" for building, I'm not sure what "openSUSE's obs" is exactly, but it seems like openSUSE's offical auto building system, if it is true, then by checking the PKGBUILD with source codes (instead of bin) is helpful for trusting. If Manjaro got such an auto building system, it'll be great.

+1 for this package to be adopted in the Majaro's repo: it's the only really alternative to firefox and, due to the fact that the "-bin" version of this package is not allowed on AUR (for reasons I don't know) and the build time is HUGE, having it available on Manjaro's repo would be really great.

Using chromium-vaapi (or ungoogled-chromium) from the archlinuxcn repo is not a very pleasant experience on a Manjaro Stable machine: these packages are kept up with Arch updates so, for example, just this month chromium-vaapi earlier was not working because of an icu update and now it's not working because of a re2 update.

I also think that if Brave was let into the official repos (btw i still am not able to find the correct topic where it was explained why it was let into the official repos), at least one of ungoogled-chromium or chromium-vaapi should be too.

Another possibility would be the existence of an alternative repo similar to archlinuxcn, but specifically for Manjaro Stable users, because for these big packages the AUR and Arch-centric repos are obviously not good for us.

As I already said earlier in the thread:

Brave is a binary package, there's no effort required.

Any build of Chromium will take at least two hours, if not six, and it potentially needs to be done for each branch. That's a lot of time and effort when there are already multiple browsers available in the repos, and these alternative Chromium-based browsers are already in the AUR.

Unless one of the Manjaro packagers uses this browser then it's not going to end up in the repos - it's just too much work.

Forum kindly sponsored by