Created attachment 143292 [details]
video (with issue) properties
Seeing visual corruption in totem after installing amdgpu 18.50 in Ubuntu 18.04.1. Not present with default OS provided video driver.
I've just tested opening a specific video when my Ubuntu 18.04.1 LTS system does not have the amdgpu driver installed from AMD, and AFTER the driver is installed.
The video is fine when the default (Ubuntu provided) video driver is used. After the latest (18.50) AMD video driver (amdgpu) is installed (and computer is rebooted) this attached/linked video displays in bright colors.
See attached example screenshot of video issue/properties. I will try to attach more pics if possible.
If I add the following to the /etc/drirc, the issue disappears. The word is that this indicates there is an issue with rgb10 support (10 bit RGB or 10bpc ? )
<option name="allow_rgb10_configs" value="false"/>
Created attachment 143293 [details]
video (no issues) properties
It seems like this issue is maybe the same as this one associated with Intel driver here - https://bugs.freedesktop.org/show_bug.cgi?id=104536
But I may be misunderstanding.
I will say that the AMDgpu drivers appear to have usability issues in Ubuntu 18.50, as my primary intent is gaming, and there is almost no possible configuration without major side effects. I did try amdgpu-pro, which caused a whole other set of issues.
I also edit videos almost daily. So I notice issues immediately.
Let me know what detail you require to proceed. I'm not sure where the issue could be, but mesa was mentioned in a similar bug report (https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312).
Most of the time, if disabling allow_rgb10_configs works around an issue like this, it's a bug in the application or a higher level library above Mesa.
However, some people are claiming this is a Mesa issue (something about not (correctly) supporting some VA-API functionality, resulting in the application using a pixel format that can't work).
It most certainly isn't a kernel driver issue, so reassigning to Mesa for now.
Please attach the output of vainfo when the problem occurs.
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Mesa Gallium driver 18.2.0-rc3 for Radeon 550 Series (POLARIS12, DRM 3.27.0, 4.15.0-45-generic, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
AMD's Leo Liu confirmed this is a gstreamer-vaapi bug, and posted a description of the problem and a suggestion for a possible fix to the gstreamer development mailing list.
*** Bug 106490 has been marked as a duplicate of this bug. ***