vainfo requires a nvidia sofile not in repositories

Bug #1890815 reported by Patola
This bug affects 22 people
Affects Status Importance Assigned to Milestone
libva-utils (Ubuntu)

Bug Description

$ vainfo
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
$ ls -la /usr/lib/x86_64-linux-gnu/dri/
ls: cannot access '/usr/lib/x86_64-linux-gnu/dri/': No such file or directory
$ apt-file search

The bug report interface does not allow me to say it's in the 'vainfo' package, so I had to use what ubuntu-bug made me use, libva-utils.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vainfo 2.6.0+ds1-1
Uname: Linux 5.6.0-19.1-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ICEWM
Date: Fri Aug 7 14:21:03 2020
InstallationDate: Installed on 2018-01-08 (942 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: libva-utils
UpgradeStatus: Upgraded to focal on 2020-05-01 (97 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-12-08T09:39:42.468905

Revision history for this message
Patola (patola) wrote :
Revision history for this message
Matt McDonald (gardotd426) wrote :

Yeah the package missing is vdpau-va-driver, which is in previous releases of Ubuntu, but for some reason was dropped for Canonical.

This breaks numerous things on 20.04 when using the Nvidia proprietary drivers.

What's crazy is that this actually isn't Nvidia's fault, Ubuntu dropped the package.

Can you guys please add the package to the repositories for Focal like you have for previous versions?

Link to the files for the package in the bionic repos:

That package does not exist on Focal.

Revision history for this message
Patola (patola) wrote :

Incredible. More than one week later, this bug report has not been touched and it's still unassigned. What happened with Canonical?

Revision history for this message
Goro Daimon (gorodaimon71113) wrote :

When will they fix this error?

Revision history for this message
Patola (patola) wrote :

For anyone looking at this bug report, if you use debian's packages it works. It's vdpau-va-driver:

64 bits:

32 bits:

Install both. Then run vainfo.

Revision history for this message
Patola (patola) wrote :

And this bug is left unattended for 42 days now. Is this a new record or something? Congratulations for the incompetence in dealing even with the most basic and easy to fix bugs, Canonical. Just for the sake of it, I opened a bug in Arch Linux stating the same thing, even referencing this one. The result? Assigned and closed with the solution in less than one hour and a half.

Learn how to deal with bugs, Canonical. You don't just let them lingering around.

Revision history for this message
Goro Daimon (gorodaimon71113) wrote :

Canonical doesn't even care about its users. This is a bad support.

Revision history for this message
nukedathlonman (areginato) wrote :

Well, still broken....Or rather a key package is MIA. Trying to configuring up my new HTPC and this was one of the major headaches I was having with getting the video card operating properly. But thanks to Patola, I pulled the missing package (vdpau-va-driver_0.7.4-7_amd64.deb) from Debian - yes everything is functioning properly now.

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

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

Changed in libva-utils (Ubuntu):
status: New → Confirmed
Revision history for this message
Srijan Kumar Sharma (raja-srijan) wrote :

I'm facing same issue. This is not the only package missing in 20.04 I has issues install some other packages too.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers