Package Details: ungoogled-chromium-ozone 80.0.3987.163-1

Git Clone URL: https://aur.archlinux.org/ungoogled-chromium-ozone.git (read-only, click to copy)
Package Base: ungoogled-chromium-ozone
Description: A lightweight approach to removing Google web service dependency with patches for wayland support via Ozone
Upstream URL: https://ungoogled-software.github.io/
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: lfleischer
Maintainer: JstKddng
Last Packager: JstKddng
Votes: 3
Popularity: 0.54
First Submitted: 2019-11-23 15:07
Last Updated: 2020-04-09 01:10

Dependencies (53)

Required by (64)

Sources (20)

Latest Comments

1 2 Next › Last »

JstKddng commented on 2020-04-09 01:03

Last time I tested, vaapi didn't work under ozone. Only under X11. That could have changed, who knows.

hedgepigdaniel commented on 2020-04-08 23:23

I can see that there are patches included for VAAPI support. To what extent do they work?

JstKddng commented on 2020-02-15 14:58

@kris7t iris is still unstable, wouldn't recommend using it as a daily driver. Regarding the last part, yeah, ozone is still not 100% stable.

kris7t commented on 2020-02-15 12:46

Fails for me using the iris mesa driver with

$ /usr/bin/chromium
[6067:6067:0215/134202.078486:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[6067:6067:0215/134202.241963:ERROR:gl_surface_egl.cc(690)] EGL Driver message (Error) eglCreateSyncKHR: _eglCreateSync
[6067:6067:0215/134202.244318:ERROR:gl_surface_egl.cc(690)] EGL Driver message (Error) eglDestroySyncKHR: _eglDestroySync
[6116:1:0215/134202.579726:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[6187:6187:0215/134202.730316:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[6187:6187:0215/134202.784552:ERROR:gl_surface_egl.cc(690)] EGL Driver message (Error) eglCreateSyncKHR: _eglCreateSync
[6187:6187:0215/134202.786186:ERROR:gl_surface_egl.cc(690)] EGL Driver message (Error) eglDestroySyncKHR: _eglDestroySync
[6212:6212:0215/134203.255775:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[6212:6212:0215/134203.295823:ERROR:gl_surface_egl.cc(690)] EGL Driver message (Error) eglCreateSyncKHR: _eglCreateSync
[6212:6212:0215/134203.297597:ERROR:gl_surface_egl.cc(690)] EGL Driver message (Error) eglDestroySyncKHR: _eglDestroySync
[6037:6050:0215/134203.625845:ERROR:browser_gpu_channel_host_factory.cc(138)] Failed to launch GPU process.
[1]    6037 segmentation fault (core dumped)  /usr/bin/chromium

Setting MESA_GLSL_CACHE_DISABLE=true and MESA_LOADER_DRIVER_OVERRIDE=i965 gets rid of the error.

However, chromium and sway seem to crash an awfully lot if chromium uses Wayland. This can be worked around with --ozone-platform=x11, at the expense of losing Wayland support.

JstKddng commented on 2020-02-13 16:51

Just fixed the linking problem, it should be working now. And now just wait for Eloston to merge the 80.0.3987.100 changes.

JstKddng commented on 2020-02-13 11:36

@samako I'd agree with you if the chromium package was having the same problem as ungoogled-chromium :/

samako commented on 2020-02-13 00:09

It looks like OpenJPEG 2.3.1 doesn't have those symbols anymore. I was able to compile by linking to an old library from 2.3.0, so downgrading openjpeg2 to 2.3.0 may allow this to compile as it stands.

JstKddng commented on 2020-02-12 15:23

@kris7t yeah same, I'm trying to figure out why is that.

kris7t commented on 2020-02-10 16:28

Linking fails for me with

[37065/37065] LINK ./chrome
FAILED: chrome
clang++ -Wl,--version-script=../../build/linux/chrome.map -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,-O1,--sort-common,--as-needed,-z,relro,-z,now -o "./chrome" -Wl,--start-group @"./chrome.rsp"  -Wl,--end-group  -latomic -ldl -lpthread -lrt -licui18n -licuuc -licudata -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -lcups -lfontconfig -ldbus-1 -lresolv -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lz -lwebpdemux -lwebpmux -lwebp -lfreetype -ljpeg -lexpat -lharfbuzz-subset -lharfbuzz -ldrm -lm -lopus -lavcodec -lavformat -lavutil -lvpx -lX11 -lX11-xcb -lxcb -lXcomposite -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lXrandr -lxkbcommon -lre2 -lwayland-egl -lwayland-client -lgbm -lpangocairo-1.0 -lpango-1.0 -lcairo -lpci -lasound -lpulse -lsnappy -lva -lxml2 -lFLAC -lminizip -lgmodule-2.0 -lgtk-3 -lgdk-3 -latk-1.0 -lcairo-gobject -lgdk_pixbuf-2.0 -lgthread-2.0 -lxslt -llzma -llcms2 -lopenjp2
ld.lld: error: /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/9.2.1/../../../../lib64/libopenjp2.so: undefined reference to __exp_finite
ld.lld: error: /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/9.2.1/../../../../lib64/libopenjp2.so: undefined reference to __exp2_finite

JstKddng commented on 2020-01-20 18:33

@GraveDigger

A lightweight approach, not a lightweight browser. Chromium is big af, no wonder it took a lot of time to install this for you.