Bug#1108913: handbrake-cli: Intel QSV/i915 not working with trixie
Package: handbrake-cli
Version: 1.9.2+ds1-1
Severity: normal
X-Debbugs-Cc: caperry@edolnx.net
Dear Maintainer,
I am using handbrake-cli from Trixie and finding it does not have Intel
QSV (i915) support working. This is working in other packages on my system
(ffmpeg) and if I use the handbrake-cli compiled by the automatedrippingmachine
project (https://github.com/automatic-ripping-machine/automatic-ripping-machine)
builds from source in a similar way but seems to work correctly while the
Trixie package does not. I'm unsure if this is a problem with handbrake-cli
or libavcodec61, but I could not find a bug in either. My apologies if I
opened this bug in the wrong project.
-- System Information:
Debian Release: 13.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.33+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages handbrake-cli depends on:
ii libass9 1:0.17.3-1+b1
ii libavcodec-extra61 [libavcodec61] 7:7.1.1-1+b1
ii libavfilter10 7:7.1.1-1+b1
ii libavformat61 7:7.1.1-1+b1
ii libavutil59 7:7.1.1-1+b1
ii libbluray2 1:1.3.4-1+b2
ii libc6 2.41-9
ii libdvdnav4 6.1.1-3+b1
ii libdvdread8t64 6.1.3-2
ii libjansson4 2.14-2+b3
ii libsvtav1enc2 2.3.0+dfsg-1
ii libswresample5 7:7.1.1-1+b1
ii libswscale8 7:7.1.1-1+b1
ii libtheoradec1 1.2.0~alpha1+dfsg-6
ii libtheoraenc1 1.2.0~alpha1+dfsg-6
ii libturbojpeg0 1:2.1.5-4
ii libva-drm2 2.22.0-3
ii libva2 2.22.0-3
ii libvorbis0a 1.3.7-3
ii libvorbisenc2 1.3.7-3
ii libvpl2 1:2.14.0-1+b1
ii libx264-164 2:0.164.3108+git31e19f9-2+b1
ii libx265-215 4.1-2
handbrake-cli recommends no packages.
handbrake-cli suggests no packages.
-- no debconf information
Reply to: