Arch Linux User Repository

FAQ: - Does VAAPI work? No

Hi, testing Version 78.0.3904.108 (Official Build) Arch Linux (64-bit).

Trying to bookmark any page with drag and drop from the URL bar into Bookmarks bar completely crash the browser - happens every time.

Various site tooltips also do not work, showing only black rectangles in completely random positions on the page.

I'm currently testing @jstkdng's ungoogled-chromium-ozone 78.0.3904.108-1 from here:

https://build.opensuse.org/package/show/home:justkidding/ungoogled-chromium-ozone

and discovered that the thumb mouse buttons for forward/back (5-buttons-mouse) are not working, neither is password import (with --enable-features=PasswordImport flag set in chromium-flags.conf).

Can that be related to the ozone build? Can someone here confirm if these two things are working with chromium-ozone 78.0.3904.108-1?

The VAAPI patches for the X11 builds are not compatible because Ozone uses a significantly different codepath for video decoding generally.

I don't believe the Igalia team working on this have made desktop VAAPI a priority, although it seems they have video acceleration via v4l2 working for embedded devices: https://github.com/OSSystems/meta-browser/tree/master/recipes-browser/chromium

I've personally tried to make it work. A minor fox is required to make it build with the use_vaapi flag, but then I couldn't find a combination of minigbm, libdrm etc that made the video acceleration actually happen.

@hedgepigdaniel

Can you please explain why VAAPI does not work? Is the VAAPI-patch incompatible or is there another reason?

Any chance of adding a binary version as AUR package chromium-ozone-bin?

What I'm looking for is an ungoogled-chromium with VAAPI and Wayland support. If I only had the knowledge and time...

@osandov I just saw this: https://bugs.chromium.org/p/chromium/issues/detail?id=988396

The window title is fixed on the current master branch.

@osandov I suspect that is on the TODO list (along with the fact that the close button has no effect). Check the existing list of bugs first.

FAQ: - Does VAAPI work? No

Does anyone else have the issue that Chromium windows in GNOME are titled "Unknown"? I'm planning on opening a bug upstream but I wanted to make sure it's not just something about my setup.

Getting the following errors while building. Is there anything I can do to fix these?

clang++: error: unable to execute command: Killed
clang++: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 10.0.0 (https://github.com/llvm/llvm-project/ 8455294f2ac13d587b13d728038a9bffa7185f2b)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: ../../third_party/llvm-build/Release+Asserts/bin
clang++: note: diagnostic msg: PLEASE submit a bug report to https://crbug.com and run tools/clang/scripts/process_crashreports.py (only works inside Google) which will upload a report and include the crash backtrace, preprocessed source, and associated run script.
clang++: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang++: note: diagnostic msg: ../../tools/clang/crashreports/browser_jumbo_2-0a253f.cpp
clang++: note: diagnostic msg: ../../tools/clang/crashreports/browser_jumbo_2-0a253f.sh
clang++: note: diagnostic msg: 

********************
[17799/20462] CXX obj/content/browser/browser/browser_jumbo_7.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
Error making: chromium-ozone

ah lol. should be fixed now :)