<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BDW] [Bisected] VAAPI not working on Broadwell with mesa 17.2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102774#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [BDW] [Bisected] VAAPI not working on Broadwell with mesa 17.2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102774">bug 102774</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop@maximbaz.com" title="freedesktop@maximbaz.com">freedesktop@maximbaz.com</a>
</span></b>
<pre>This bug also affects Chromium compiled with VA-API patch to use hardware video
acceleration. We have at least 6 people using ArchLinux confirming this so far.
Chromium sometimes just renders videos as a black rectangle, sometimes freezes
entirely, and once even crashed X.
Someone reported, that reverting the same change as @alim mention fixes the
issue.
Non-exhaustive list of affected Intel CPUs: i7-6500U, i7-7500U, i7-7820HQ.
If this can't / shouldn't be reverted, is there a way to compile Chromium in a
different way so that we don't experience this issue?
How we compile Chromium with VA-API today:
<a href="https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=chromium-vaapi">https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=chromium-vaapi</a>
History of comments discussing this issue:
<a href="https://aur.archlinux.org/packages/chromium-vaapi">https://aur.archlinux.org/packages/chromium-vaapi</a>
I'll ask affected people to CC to this bug, so you can better see the number of
affected people.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>