[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#923080: marked as done (libva error: va_getDriverName() failed with Wayland)

Your message dated Thu, 29 Dec 2022 11:50:22 +0000
with message-id <E1pArQU-004n8g-KM@fasolo.debian.org>
and subject line Bug#923080: fixed in libva 2.17.0-1
has caused the Debian Bug report #923080,
regarding libva error: va_getDriverName() failed with Wayland
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
923080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923080
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: chromium
Version: 72.0.3626.109-1
Severity: wishlist

Dear Debian folks,
Decoding videos on the GPU using VA-API does not seem to work after bugs reports #856255 [1] and #919762 [2] were fixed. 

The messages below are shown during start.

```
$ chromium
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) [28239:28239:0223/215051.751645:ERROR:vaapi_wrapper.cc(324)] vaInitialize failed: unknown libva error [28239:28239:0223/215051.795078:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process. 
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
```

VA-API is installed properly though.

```
$ vainfo
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.4 (libva 2.4.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Broadwell - 2.3.0
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264MultiviewHigh      :	VAEntrypointVLD
      VAProfileH264StereoHigh         :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileVP8Version0_3          :	VAEntrypointVLD
```

So it looks like, some piece is still missing for working VA-API support.


Kind regards,

Paul


[1]: https://bugs.debian.org/856255
[2]: https://bugs.debian.org/919762

--- End Message ---
--- Begin Message --- 
Source: libva
Source-Version: 2.17.0-1
Done: Sebastian Ramacher <sramacher@debian.org>

We believe that the bug you reported is fixed in the latest version of
libva, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 923080@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher <sramacher@debian.org> (supplier of updated libva package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 29 Dec 2022 12:39:32 +0100
Source: libva
Architecture: source
Version: 2.17.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Sebastian Ramacher <sramacher@debian.org>
Closes: 923080
Changes:
 libva (2.17.0-1) unstable; urgency=medium
 .
   * New upstream version 2.17.0
     - Add support for DRI3 (Closes: #923080)
   * debian/control:
     - Add provides for new driver ABI
     - Bump Standards-Version
     - Add new BDs: libx11-xcb-dev, libxcb-dri3-dev, libxcb1-dev
   * debian/libva2.symbols: Remove internal symbols
   * debian/copyright: Update for 2.17.0
Checksums-Sha1:
 d13c0fa97126be2d970808e2ad34e8ed00272e2e 2450 libva_2.17.0-1.dsc
 5e252956d9dedd8711def786218dbc730c49937e 276993 libva_2.17.0.orig.tar.gz
 89e561079855292f5eca6b46ba91746a7db104f3 12060 libva_2.17.0-1.debian.tar.xz
Checksums-Sha256:
 3cf91a923dd7ad70c1c169a8b623b5ffa020804a7fb992ce848ba88b8152ee60 2450 libva_2.17.0-1.dsc
 8940541980ef998a36cd8f6ad905e81838ea4ddf56dc479ed2bebd12711e6001 276993 libva_2.17.0.orig.tar.gz
 f9413175899831df8b72ba78e7294e7363f11ae9af4b2863613497ffd97a7319 12060 libva_2.17.0-1.debian.tar.xz
Files:
 5fd06ffb19c65bc6ab440976469279ec 2450 libs optional libva_2.17.0-1.dsc
 0ac769fc61c2f7c1dd0916f12794549d 276993 libs optional libva_2.17.0.orig.tar.gz
 26273087670646564a812e62df8cbd21 12060 libs optional libva_2.17.0-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmOtfSwACgkQafL8UW6n
GZNlvA//a+31eRnJxwZ1aXL7dVYvfILVY3i0UmRn6L3pOTFXUYlXB5rk/yBlBwZN
c7f2UzFrZG7wiFeaciJ5ZST8SPhZbKM2DTmoFfypXJIEUt3fH81Vnlj3eFqKM+4K
a8r+SZzTPKXR9AvxOwtS4afGMSrny9ckt3fv0BZaK0xqXrrjcpZcOxNOOmWPis6M
8cIhoQr9QvkWd9Mh/PxPcZWuvi+6jirzqO6GKlTrGF3H6L5fU6bv2Gtz9gE4BTbG
LBusIgifwsa74Ux0Hs63GahW9bdi0sTVid4sU/1VvkrzPiZrN2d+Ewpt93tScZVW
nsYf42UcnGJj/tsr64MiuJSwNn/xpjCGsznuCx0yrkl4o1bGTP/9tdi0b/OhVkJN
H3THEfPxyPSNAzIGVXCmxePzaTjZmX1rFoBzlZ0RjznMrclbisgNsPiWMu+S8IS5
mUDq7rq1MgGZpLTKJaBHELY8WRKnIJVY4aiQOmi2i1xAgMYrKA/dgsoytuqjZCFS
pINPVdp1uRwrYbk9jKgqSzxN/Z6fqELQJIvFhzXPYmiNLVaT9yBnqQjTOo3bnOWK
Rpz8SrTwUlnh/Yig7TuvTMIBvE0RxxajSUmPnreFn0lHJDcVRLF2sYSAoEuhomNs
oC6x0zCL38grkV5J9GUBLV837xLkxxuS5syit4VQ/YQiNuJKYzA=
=sv0s
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: