* [ISSUE] Corrupted (pink) video decoding in Chromium 77
@ 2019-10-07 22:46 voidlinux-github
2019-10-08 6:01 ` voidlinux-github
` (9 more replies)
0 siblings, 10 replies; 11+ messages in thread
From: voidlinux-github @ 2019-10-07 22:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
New 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.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
@ 2019-10-08 6:01 ` voidlinux-github
2019-10-12 6:08 ` voidlinux-github
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: voidlinux-github @ 2019-10-08 6:01 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
New comment by owindsor on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-539349112
Comment:
Seeing the same issue here Ryzen 7, RX 580;
Void 5.2.19_1 x86_64 AuthenticAMD uptodate rrrmFFFFFF
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
2019-10-08 6:01 ` voidlinux-github
@ 2019-10-12 6:08 ` voidlinux-github
2019-10-12 6:22 ` voidlinux-github
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: voidlinux-github @ 2019-10-12 6:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
New comment by obunden on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-541289876
Comment:
So this doesn't happen if you use youtube for example and the vp9 codec is active?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 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
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: voidlinux-github @ 2019-10-12 6:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
New comment by obunden on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-541290912
Comment:
Might be worth trying to replicate this in other software that use va-api like vlc and mpv. Bugs with colors seem to be pretty common when amd hardware / drivers are involved. The acceleration in chromium is not enabled by default so it's bound to cause issues. I think we manually enable it in the build template. Not 100% sure tho ...
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
` (2 preceding siblings ...)
2019-10-12 6:22 ` voidlinux-github
@ 2019-10-13 6:13 ` voidlinux-github
2019-10-27 15:12 ` voidlinux-github
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: voidlinux-github @ 2019-10-13 6:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
New comment by foxlet on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-541389994
Comment:
VP9 is unaffected. VAAPI is enabled in our package (not in upstream) even though it's known to be experimental.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
` (3 preceding siblings ...)
2019-10-13 6:13 ` voidlinux-github
@ 2019-10-27 15:12 ` voidlinux-github
2019-11-02 14:08 ` voidlinux-github
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: voidlinux-github @ 2019-10-27 15:12 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
New comment by StreetStrider on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-546703543
Comment:
I may have related issue, as my chromium does not start at all due to some VA-API error. I tried both void repo's chromium and standalone edge chrome and I have `libva` installed.
I started with minimal Void distribution, so I may lack some required packages.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
` (4 preceding siblings ...)
2019-10-27 15:12 ` voidlinux-github
@ 2019-11-02 14:08 ` voidlinux-github
2019-11-02 17:53 ` voidlinux-github
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: voidlinux-github @ 2019-11-02 14:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 3445 bytes --]
New comment by StreetStrider on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-549047131
Comment:
I tried to start current chromium with `--disable-gpu` and got error:
```
Failed to load /usr/lib/chromium/swiftshader/libGLESv2.so: /usr/lib/chromium/swiftshader/libGLESv2.so
```
Without this option I got a bunch of libva-, gpu- related errors:
```
[21155:21155:1102/170707.519429:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519516:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileMPEG2Simple and entrypoint 1
[21155:21155:1102/170707.519528:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519551:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileMPEG2Main and entrypoint 1
[21155:21155:1102/170707.519559:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519564:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileMPEG4Simple and entrypoint 1
[21155:21155:1102/170707.519570:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519576:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileMPEG4AdvancedSimple and entrypoint 1
[21155:21155:1102/170707.519583:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519589:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileH264Baseline and entrypoint 1
[21155:21155:1102/170707.519595:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519608:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint 1
[21155:21155:1102/170707.519622:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519629:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint 1
[21155:21155:1102/170707.519636:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519642:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileVC1Simple and entrypoint 1
[21155:21155:1102/170707.519656:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519673:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileVC1Main and entrypoint 1
[21155:21155:1102/170707.519689:ERROR:vaapi_wrapper.cc(788)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[21155:21155:1102/170707.519703:ERROR:vaapi_wrapper.cc(678)] FillProfileInfo_Locked failed for va_profile VAProfileVC1Advanced and entrypoint 1
[21155:21155:1102/170707.519719:ERROR:vaapi_wrapper.cc(509)] GetConfigAttributes failed for va_profile VAProfileH264Baseline
[21155:21155:1102/170707.519733:ERROR:vaapi_wrapper.cc(509)] GetConfigAttributes failed for va_profile VAProfileH264Main
[21155:21155:1102/170707.519739:ERROR:vaapi_wrapper.cc(509)] GetConfigAttributes failed for va_profile VAProfileH264High
```
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
` (5 preceding siblings ...)
2019-11-02 14:08 ` voidlinux-github
@ 2019-11-02 17:53 ` voidlinux-github
2019-12-26 7:06 ` voidlinux-github
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: voidlinux-github @ 2019-11-02 17:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
New comment by StreetStrider on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-549066461
Comment:
My issue was fixed by removing Chromium profile from previous installation, located in `~/.config/chromium`, possibly it had GPU settings which are mismatched for the new system.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
` (6 preceding siblings ...)
2019-11-02 17:53 ` voidlinux-github
@ 2019-12-26 7:06 ` voidlinux-github
2020-02-25 10:19 ` [ISSUE] [CLOSED] " xtraeme
2020-02-25 10:19 ` xtraeme
9 siblings, 0 replies; 11+ messages in thread
From: voidlinux-github @ 2019-12-26 7:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
New comment by jeuvaessen on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-568994949
Comment:
I disabled in the Settings "Use hardware acceleration when available".
After relauch of Chromium the colours were normal.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
` (8 preceding siblings ...)
2020-02-25 10:19 ` [ISSUE] [CLOSED] " xtraeme
@ 2020-02-25 10:19 ` xtraeme
9 siblings, 0 replies; 11+ messages in thread
From: xtraeme @ 2020-02-25 10:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 203 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/issues/15222#issuecomment-590792176
Comment:
Stalled for a while, please reopen if the issue still exists
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ISSUE] [CLOSED] Corrupted (pink) video decoding in Chromium 77
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 voidlinux-github
` (7 preceding siblings ...)
2019-12-26 7:06 ` voidlinux-github
@ 2020-02-25 10:19 ` xtraeme
2020-02-25 10:19 ` xtraeme
9 siblings, 0 replies; 11+ messages in thread
From: xtraeme @ 2020-02-25 10:19 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2020-02-25 10:19 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-07 22:46 [ISSUE] Corrupted (pink) video decoding in Chromium 77 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 ` [ISSUE] [CLOSED] " xtraeme
2020-02-25 10:19 ` xtraeme
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).