From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Corrupted (pink) video decoding in Chromium 77
Date: Tue, 25 Feb 2020 11:19:04 +0100 [thread overview]
Message-ID: <20200225101904.DaBEptD_tMFqKt8_lrV4fmVEosEp3V0DDg3-TVEhQus@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15222@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
Closed issue by foxlet on void-packages repository
https://github.com/void-linux/void-packages/issues/15222
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: Void 5.2.18_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFF
* package: chromium 77.0.3865.90
### Expected behavior
Correct video decoding.
### Actual behavior
Corrupted video decoding (red/yellow/pink output with little discernible detail).
![Chromium output](https://i.imgur.com/wYXU1Lf.png)
### Steps to reproduce the behavior
Play any H.264 video in-browser.
There is a potential VA-API bug that prevents proper decoding on AMD hardware (Ryzen 5 + R9 270x in this case). #14862 seems like a likely culprit.
next prev parent reply other threads:[~2020-02-25 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 22:46 [ISSUE] " voidlinux-github
2019-10-08 6:01 ` voidlinux-github
2019-10-12 6:08 ` voidlinux-github
2019-10-12 6:22 ` voidlinux-github
2019-10-13 6:13 ` voidlinux-github
2019-10-27 15:12 ` voidlinux-github
2019-11-02 14:08 ` voidlinux-github
2019-11-02 17:53 ` voidlinux-github
2019-12-26 7:06 ` voidlinux-github
2020-02-25 10:19 ` xtraeme [this message]
2020-02-25 10:19 ` xtraeme
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200225101904.DaBEptD_tMFqKt8_lrV4fmVEosEp3V0DDg3-TVEhQus@z \
--to=xtraeme@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).