vlc no longer displays certain streams since update vdpau

Bug #1707393 reported by paul janssen
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Display was fine until apdate of vdpau was applied.
Vlc codec info from stream:
Video
MPEG-4 Video (mp4v)
Resolution: 640x480
Framerate: 1000
Decode format: planar 4:2:0 YUV

Previous recordings of this stream will also do not display anymore, while the standard Videos apllication does play them back fine.
New recordings via vlc cannot be played back by both the vlc and Videos application.

Console output while starting the stream:
VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
[0000000001589088] core libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[00007f86a00009b8] core input error: ES_OUT_RESET_PCR called
[00007f86b00092d8] vdpau_avcodec generic error: decoder profile not supported: 12
[00007f86b0007ac8] vdpau_avcodec generic error: decoder profile not supported: 12
[00007f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies.
[mpeg4 @ 0x7f869803dfa0] warning: first frame is no keyframe
[00007f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies.
[00007f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies.
[00007f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies.
[00007f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vlc 2.2.2-5ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul 29 15:02:01 2017
InstallationDate: Installed on 2017-06-17 (42 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
SourcePackage: vlc
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
paul janssen (pauluswaulus) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in vlc (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastian Ramacher (s-ramacher) wrote :

So this sound like a driver bug then. What VDPAU driver do you use and which packages were upgraded?

Changed in vlc (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Sebastian Ramacher (s-ramacher) wrote :

Reporter of #1710503 uses mesa-vdpau-driver. Re-assigning accordingly.

affects: vlc (Ubuntu) → mesa (Ubuntu)
Revision history for this message
Dimitri Papadopoulos (dimitri-papadopoulos) wrote :

As a workaround switching the "Output" parameter from "Automatic" to "X11 video output (XCB)" restores video.

But then vlc keeps printing these error messages:

[00007ff124060808] core blend error: blending YUVA to VDV0 failed
[00007ff124060808] blend blend error: no matching alpha blending routine (chroma: YUVA -> VDV0)

Revision history for this message
Dimitri Papadopoulos (dimitri-papadopoulos) wrote :
Download full text (3.7 KiB)

About the packages that were upgraded. This bug appeared a few days before it was reported here on 2017-07-29. I can remember I tried to investigate for a few days before finding and confirming this bug report.

From my file/var/log/apt/history.log.2.gz on my own computer I see that I installed "vdpauinfo" on 2017-07-27, probably in order to investigate this bug:

Start-Date: 2017-07-27 22:30:56
Commandline: apt install vdpauinfo
Requested-By: dimitri (1000)
Install: vdpauinfo:amd64 (1.0-1)
End-Date: 2017-07-27 22:31:01

So the updates responsible for this bug probably occurred hours to days before that. I think this update is responsible:

Start-Date: 2017-07-27 21:32:51
Commandline: aptdaemon role='role-commit-packages' sender=':1.93'
Install: libllvm4.0:amd64 (1:4.0-1ubuntu1~16.04.1, automatic), libllvm4.0:i386 (1:4.0-1ubuntu1~16.04.1, automatic), libwayland-bin:a
md64 (1.12.0-1~ubuntu16.04.1, automatic), libinput-bin:amd64 (1.6.3-1ubuntu1~16.04.1, automatic), libsensors4:i386 (1:3.4.0-2, automatic)
Upgrade: libgles2-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libdrm-nouveau2:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-nouveau2:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libwacom-common:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), libegl1-mesa-dev:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libglapi-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libglapi-mesa:i386 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), gnome-software:amd64 (3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1, 3.20.5-0ubuntu0.16.04.5), xfonts-utils:amd64 (1:7.7+3, 1:7.7+3ubuntu0.16.04.2), libxatracker2:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libwacom-bin:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), libegl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgbm1:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libwayland-client0:amd64 (1.9.0-1, 1.12.0-1~ubuntu16.04.1), x11proto-core-dev:amd64 (7.0.28-2ubuntu1, 7.0.31-1~ubuntu16.04.1), libdrm-amdgpu1:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-amdgpu1:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libwayland-dev:amd64 (1.9.0-1, 1.12.0-1~ubuntu16.04.1), ubuntu-software:amd64 (3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1, 3.20.5-0ubuntu0.16.04.5), libwayland-egl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libxfont1:amd64 (1:1.5.1-1, 1:1.5.1-1ubuntu0.16.04.1), libdrm2:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm2:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libgl1-mesa-dri:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-dri:i386 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-glx:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-glx:i386 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libdrm-intel1:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-intel1:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libwacom2:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), libdrm-radeon1:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-radeon1:i386 (2.4.70-1~ubuntu16....

Read more...

Revision history for this message
Seb Bonnard (sebma) wrote :

Hi, I also have the same pb.

Revision history for this message
Roland Seuhs (rseuhs) wrote :

This bug also appears on a fresh install of Kubuntu 16.04 which was then immideately upgraded to Kubuntu 18.04 Ubuntu Bionic Beaver (development branch).

Changed in mesa (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.