Package Details: ungoogled-chromium 83.0.4103.116-2

Git Clone URL: (read-only, click to copy)
Package Base: ungoogled-chromium
Description: A lightweight approach to removing Google web service dependency
Upstream URL:
Keywords: blink browser privacy web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: ilikenwf
Maintainer: seppia (JstKddng)
Last Packager: JstKddng
Votes: 156
Popularity: 11.89
First Submitted: 2016-12-19 08:08
Last Updated: 2020-07-01 15:41

Dependencies (51)

Required by (69)

Sources (18)

Pinned Comments

JstKddng commented on 2020-06-23 14:59

You can get built binaries for this package and derivatives on my repository. Instructions are here:

You can also get them from the OBS but that doesn't work sometimes.

At least until upstream figures out how to create official binaries.

seppia commented on 2018-12-12 21:34

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 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.


Latest Comments

1 2 3 4 5 6 ... Next › Last »

Sattaxt commented on 2020-07-03 08:55

I get a linking error with the latest update (.116). I ran LD with -v, and this is the output:

[7677/7677] LINK ./chrome FAILED: chrome clang++ -Wl,--version-script=../../build/linux/ -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -fuse-ld=lld -Wl,--icf=all -Wl,--color-diagnostics -flto=thin -Wl,--thinlto-jobs=8 -Wl,--thinlto-cache-dir=thinlto-cache -Wl,--thinlto-cache-policy,cache_size=10\%:cache_size_bytes=10g:cache_size_files=100000 -Wl,--lto-O0 -fwhole-program-vtables -m64 -Wl,-O2 -Wl,--gc-sections -rdynamic -fsanitize=cfi-vcall -fsanitize=cfi-icall -pie -Wl,--disable-new-dtags -Wl,-O3,--sort-common,--as-needed,-z,relro,-z,now,-v -o "./chrome" -Wl,--start-group @"./chrome.rsp" -Wl,--end-group -latomic -ldl -lpthread -lrt -lX11 -lX11-xcb -lxcb -lxcb-dri3 -lXcomposite -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lgmodule-2.0 -lglib-2.0 -lgobject-2.0 -lgthread-2.0 -licui18n -licuuc -licudata -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups -lfontconfig -ldbus-1 -lz -lresolv -lgio-2.0 -lwebpdemux -lwebpmux -lwebp -lfreetype -ljpeg -lexpat -lharfbuzz-subset -lharfbuzz -ldrm -lm -lopus -lavcodec -lavformat -lavutil -lvpx -lXrandr -lre2 -lpci -lgbm -lXss -lasound -lpulse -lsnappy -lpangocairo-1.0 -lpango-1.0 -lcairo -lva -lxml2 -latspi -lFLAC -lminizip -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 -lxslt LLD 10.0.0 (compatible with GNU linkers) clang-10: error: unable to execute command: Terminated clang-10: error: linker command failed due to signal (use -v to see invocation) ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting... error making: %!s(func() string=0x55a8623fce80)

Update: Has nothing to do with package. I had setup LTO wrong, and that caused a link error. For anybody that also has the same problem, take a look at your LTO options or just disable it.

JstKddng commented on 2020-07-02 15:51


well, the makepkg logs would be nice to have.

I also triggered a rebuild on the OBS just in case and it was succesful.

Jojii commented on 2020-07-02 13:45

@JstKddng I have no idea where I should look for helpful logs. I don't remove those containers but I don't get much information from them too.

JstKddng commented on 2020-07-02 12:18


I'm gonna need some logs before I can help. Are you immediately deleting the docker container after building?

Jojii commented on 2020-07-02 11:19

@JstKddng nope I can't find any log where I could get more informations from

JstKddng commented on 2020-07-02 11:11


Depends on how much cores/threads you have. I'd recommend to have swap, at least a swapfile during compilation.


Do you have an error message?

Jojii commented on 2020-07-02 08:26

My VM where I compile this inside a docker container shuts down/crashes after some time compiling this package :(

followait commented on 2020-07-02 00:26

@JstKddng without swap, 16G memory not enough?

JstKddng commented on 2020-07-01 15:51


probably you ran out of memory. You can continue compilation if you run makepkg -e without starting all over again.

followait commented on 2020-07-01 15:18

After building for about 75%, error occurs, no detail. It takes about one and a half hours. It's sad. I don't known why.