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

Bug#1100151: marked as done (vainfo failed to initialize display drm)

Your message dated Tue, 11 Mar 2025 23:20:17 +0000
with message-id <E1ts8tV-006tiw-RX@fasolo.debian.org>
and subject line Bug#1100151: fixed in libva-utils 2.22.0+ds1-2
has caused the Debian Bug report #1100151,
regarding vainfo failed to initialize display drm
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.)


-- 
1100151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100151
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: vainfo
Version: 2.22.0+ds1-1
Severity: normal
X-Debbugs-Cc: twx@fastmail.com

Hello Maintainers,

The current vainfo release does not support 'drm' as display driver, which fails on Debian headless/server installations:

| vainfo
| Trying display: wayland
| Trying display: x11
| error: can't connect to X server!
| error: failed to initialize display
|
| vainfo --display drm
| error: failed to initialize display 'drm'

apt installs 'libdrm2' but it seems 'libva-drm2' is no longer installed as dependency (on bookworm it did).
I did the following to compile and install a local vainfo with drm display support:

| apt install build-essential libtool pkg-config git libdrm-dev libva-dev
| git clone https://salsa.debian.org/multimedia-team/libva-utils.git
| cd libva-utils
| ./autogen.sh
| make && make install 

ldd drm from vainfo (apt) and vainfo (local):

| ldd /usr/bin/vainfo | grep drm
| libdrm.so.2 => /lib/x86_64-linux-gnu/libdrm.so.2 (0x00007f14bbaaf000)
|
| ldd /usr/local/bin/vainfo | grep drm
| libdrm.so.2 => /lib/x86_64-linux-gnu/libdrm.so.2 (0x00007f17fcd50000)
| libva-drm.so.2 => /lib/x86_64-linux-gnu/libva-drm.so.2 (0x00007f17fcd4b000)

Output from vainfo (local):

| vainfo
| Trying display: wayland
| Trying display: drm
| libva info: VA-API version 1.22.0
| libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
| libva info: Found init function __vaDriverInit_1_22
| libva info: va_openDriver() returns 0
| vainfo: VA-API version: 1.22 (libva 2.22.0)
| vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 25.1.2 ()
| vainfo: Supported profile and entrypoints
| ...

I'm not sure whether this is actually a bug or if DRM display support was intentionally left out. However, for those running Debian headless, having DRM display support would be useful.

Best regards,
Tom Wijnroks

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.17-amd64 (SMP w/18 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vainfo depends on:
ii  libc6               2.40-7
ii  libva-wayland2      2.22.0-3
ii  libva-x11-2         2.22.0-3
ii  libva2              2.22.0-3
ii  libwayland-client0  1.23.1-3
ii  libx11-6            2:1.8.10-2

vainfo recommends no packages.

vainfo suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Source: libva-utils
Source-Version: 2.22.0+ds1-2
Done: Sebastian Ramacher <sramacher@debian.org>

We believe that the bug you reported is fixed in the latest version of
libva-utils, 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 1100151@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-utils 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: Tue, 11 Mar 2025 23:07:39 +0100
Source: libva-utils
Architecture: source
Version: 2.22.0+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Sebastian Ramacher <sramacher@debian.org>
Closes: 1100151
Changes:
 libva-utils (2.22.0+ds1-2) unstable; urgency=medium
 .
   * debian/control:
     - Bump Standards-Version
     - Add libdrm-dev to BD (Closes: #1100151)
Checksums-Sha1:
 bc0c9a44f09a024608fa9437f0805641fb6ab2ba 1474 libva-utils_2.22.0+ds1-2.dsc
 6a285c2ed3ac48a68556cf46028ba41b6a558aa6 7564 libva-utils_2.22.0+ds1-2.debian.tar.xz
 1ebad2703a4a8f43dc6a5a7c55e75c9fedab8086 8406 libva-utils_2.22.0+ds1-2_source.buildinfo
Checksums-Sha256:
 4ac8784270af1026f9149e72ffcf60d3803a03f31ef0d06d0b07228a5d102401 1474 libva-utils_2.22.0+ds1-2.dsc
 9b005fb22206e16159945e3575bc04fb86dde1dea204c671fc4592df716f3dfb 7564 libva-utils_2.22.0+ds1-2.debian.tar.xz
 b0b66c4409de3b8944f6e8e205c8bc891f9a54554e31d4981d370cc47e2b79d8 8406 libva-utils_2.22.0+ds1-2_source.buildinfo
Files:
 571d4551ef64aee40f3c96b8005256ba 1474 utils optional libva-utils_2.22.0+ds1-2.dsc
 00d9976f597ff72e4db0ee0e60b1a84c 7564 utils optional libva-utils_2.22.0+ds1-2.debian.tar.xz
 4d266778d85587c35701b82998503459 8406 utils optional libva-utils_2.22.0+ds1-2_source.buildinfo


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

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZ9C0RwAKCRAhk2s2YA/N
iR5WAQDFJy9F5caPh/rAkwc/eCBgzXdkvLGZi5D4umAQOrofwQEAn74g1r10ymRA
/rpMifZoJIAljuoz6fyVFAsEsRUlrgg=
=2UkS
-----END PGP SIGNATURE-----

Attachment: pgpUXMhgCKWbc.pgp
Description: PGP signature


--- End Message ---
Reply to: