Package Details: chromium-vaapi 74.0.3729.157-1

Git Clone URL: (read-only)
Package Base: chromium-vaapi
Description: Chromium with VA-API support to enable hardware acceleration
Upstream URL:
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (maximbaz)
Last Packager: maximbaz
Votes: 66
Popularity: 3.220646
First Submitted: 2016-07-09 09:44
Last Updated: 2019-05-15 08:33

Dependencies (47)

Required by (44)

Sources (10)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

kureta commented on 2019-01-30 18:05

maximbaz canyou come to #archlinux or #archlinux-aur? We are cluttering the comment section here.

kureta commented on 2019-01-30 17:50

I have fixed everything. Can you create a patch that changes the line I mentioned in third_party/webrtc/modules/desktop_capture/linux/ It is necessary, because memset is in <string.h> not <string>.

I have created a patch containing all my changes using git diff master here.

But compilation is not finished yet. So be careful.

maximbaz commented on 2019-01-30 17:29

This PKGBUILD is based on extra/chromium, so all the patches are coming from there, I trust foutrelis on this :) The vaapi patch is coming from the infamous PR, folks here are helping me to keep the patch in a working state so that it can be applied to the current chromium source code. And the cfi-vaapi-fix.patch can probably be removed now, I believe it was merged upstream.

Right now the vaapi patch doesn't apply cleanly, if someone fixes line numbers, please share the patch here ;)

kureta commented on 2019-01-30 17:12

I have changed one line in third_party/webrtc/modules/desktop_capture/linux/ and the compilation continues. #include <string> to #include <string.h>.

By the way, I looked at gentoo's patches and saw this line: "Stolen from Arch basically." :) So I guess I'll not take the patches from there.

kureta commented on 2019-01-30 16:38

Of course maximbaz :) But I am getting a compile error related to webrtc. I am now trying to see if that's because I messed up something with the patches. By the way, what are the sources of your .patch files? Did you write them yourself? chromium-dev package gets some of its patches from gentoo. Should I look into that so our patches also stay up-to-date?

maximbaz commented on 2019-01-30 16:17

Could you please share the fixed patches kureta? :)

kureta commented on 2019-01-30 15:20

I have fixed patch files and started building v72.0.3626.81. Some of these patches were already applied upstream, so I have deleted those files.

ukbeast commented on 2019-01-26 18:04

Libva has been updated

It is broken on my amdgpu, could anyone else please test to see if it still works?

It broke for me, and am now using FFMPEG decoder.

flygoat commented on 2019-01-25 06:59

[1739:1739:0125/] vaQueryConfigProfiles returned: 14 [1739:1739:0125/] vaQueryConfigProfiles returned: 14

vainfo: VA-API version: 1.3 (libva 2.3.0) vainfo: Driver version: Mesa Gallium driver 18.3.2 for AMD RAVEN (DRM 3.27.0, 4.19.16-1-MANJARO, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc

Not working : - (

wooque commented on 2019-01-07 13:07

Fedora included VAAPI patch in their official Chromium package.