Package Details: chromium-vaapi 75.0.3770.142-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: 76
Popularity: 8.083364
First Submitted: 2016-07-09 09:44
Last Updated: 2019-07-16 16:02

Dependencies (48)

Required by (47)

Sources (11)

Pinned Comments

maximbaz commented on 2019-07-18 13:19

This package is compiled with 'use_vaapi=true', but you need to pass --ignore-gpu-blacklist if you want to enable hardware video acceleration using VA-API.

Latest Comments

« First ‹ Previous ... 32 33 34 35 36 37 38 39 40 41 42 ... Next › Last »

bmg1001 commented on 2017-09-15 17:21

I've been having the black/no video issues too and downgrading mesa worked for me as well.

My laptop is running an Intel Core i7-6500U with the Intel HD 520 iGPU.

maximbaz commented on 2017-09-15 15:30

Yeah, usually I get black screen, but sometimes Chromium freezes, and even once the entire X crashed. So see @alim115, there is enough people affected :)

enihcam commented on 2017-09-15 15:22

@maximbaz @alim115 My GPU is Intel Gen5. The bug causes the chrome tabs totally freeze.

Bonnee commented on 2017-09-15 10:02

I get black videos after mesa 17.2 as well. I'm running an i7-7500u so skylake/kabylake is confirmed to be broken. Disabling the acceleration flags works fine

maximbaz commented on 2017-09-15 09:44

@alim115 thanks for doing this! It is not exactly right that nobody else is commenting on this, @enihcam and @stove have already mentioned that they have the same issue, which makes it 4 of us now.

I'll try to see if I can compile mesa later today, but please go ahead and submit the issue with mesa. For reference, I have i7-7820HQ processor with Intel HD Graphics 630.

alim115 commented on 2017-09-15 04:52

I did a bisect on mesa 17.2 and tracked down the change that broke vaapi. The change is specific to Gen8+ GPUs. It affects Broadwell GPUs for sure and possibly Skylake+ GPUs.

@maximbaz If you have time to make your own mesa-17.2 build, can you try reversing the patch (only the third block needs to be backed out: brw_state_upload.c)? No one else commenting that they have the issue.

It fixes the vaapi problem on my laptop and doesn't seem to break anything else.

olive commented on 2017-09-14 07:38

@alim115 I wasn't asking for a screenshot, I was asking for a precise link to a video that shows the problem. Anyway, the link was visible on the screenshot, so I have tested it ( For me, there is hardware acceleration (with the h264ify extension) with both my Desktop graphic card (discrete Radeon HD6570) and my laptop (integrated GPU on a Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz (sandybridge, the graphic ship is presumably HD3000). Does vaapi works at all? What's the output of vainfo? What happens if you try to play videos with mpv (mpv -vo=vaapi -hwdec=vaapi

Edit: you already have tested vaapi with mpv and have experienced problems. Look at the output of vainfo. If vaapi is broken, then the cause of your problems is not chromium. By the way, are you using Xorg or Wayland?

alim115 commented on 2017-09-13 19:56

@olive There isn't much to show at all. Its just a black frame. My hardware does not support vp9 acceleration either.

First screenshot is the vp9 codec using the VpxVideoDecoder. Works fine.

Second screenshot is the h264 codec using the FFmpegVideoDecoder. Works fine. h264ify extension is running with the hardware-accelerated video flag disabled.

Third screenshot is the h264 codec using the GpuVideoDecoder. Black frame. No video. Audio works. h264ify extension is running with the hardware-accelerated video flag enabled.

It affects all media decoded with GpuVideoDecoder. Youtube, etc.

agm28011997 commented on 2017-09-13 19:49

i have no problems with hd 4600 intel and apu 5xxx of amd, 2 pc's with smplayer and mpv and chromium and last packages of mesa, no problems

olive commented on 2017-09-13 06:19

@alim115 For me it works correctly with my Radeon HD6570 and also with my laptop that has Sandybridge i5-2450 (I think the graphic chipset is HD3000).

Could you post a precise link of a video showing the problem? Does it appear with all youtube videos? Note that in my case I have no VP9 hardware acceleration (which is expected, it is not supported by my hardware), but well with the hd264ify extension.