Your message dated Tue, 8 Apr 2025 13:20:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#1101881: mpv: 0.40.0-2 no longer correctly uses VAAPI
but VAAPI-copy instead
has caused the Debian Bug report #1101881,
regarding mpv: 0.40.0-2 no longer correctly uses VAAPI but VAAPI-copy instead
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 [email protected]
immediately.)
--
1101881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101881
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mpv
Version: 0.40.0-2
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
Mpv 0.39.0 in Trixie worked with my AMD Polaris card correctly using
`hwdec=auto-safe`, it selected VAAPI as the hardware decoder. 0.40.0-2 selects
VAAPI-copy which is inferior. I have found a related issue on Github that
points to a problem with 0.40.0-2 not being built with the dmabuf-interop-gl
feature: https://github.com/mpv-player/mpv/issues/16108
Thanks.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.20-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mpv depends on:
ii libarchive13t64 3.7.4-1.1
ii libasound2t64 1.2.13-1+b1
ii libass9 1:0.17.3-1+b1
ii libavcodec61 7:7.1.1-1+b1
ii libavdevice61 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-6
ii libcaca0 0.99.beta20-5
ii libcdio-cdda2t64 10.2+2.0.2-1+b1
ii libcdio-paranoia2t64 10.2+2.0.2-1+b1
ii libcdio19t64 2.1.0-5
ii libdisplay-info2 0.2.0-2
ii libdrm2 2.4.124-1
ii libdvdnav4 6.1.1-3+b1
ii libegl1 1.7.0-1+b2
ii libgbm1 25.0.2-1
ii libjack-jackd2-0 [libjack-0.125] 1.9.22~dfsg-4
ii libjpeg62-turbo 1:2.1.5-3.1
ii liblcms2-2 2.16-2
ii liblua5.2-0 5.2.4-3+b3
ii libmujs3 1.3.6-1
ii libpipewire-0.3-0t64 1.4.1-1
ii libplacebo349 7.349.0-3
ii libpulse0 17.0+dfsg1-2+b1
ii librubberband2 3.3.0+dfsg-2+b3
ii libsdl2-2.0-0 2.32.2+dfsg-2
ii libsixel1 1.10.5-1
ii libsndio7.0 1.10.0-0.1
ii libswresample5 7:7.1.1-1+b1
ii libswscale8 7:7.1.1-1+b1
ii libuchardet0 0.0.8-1+b2
ii libva-drm2 2.22.0-3
ii libva-wayland2 2.22.0-3
ii libva-x11-2 2.22.0-3
ii libva2 2.22.0-3
ii libvdpau1 1.5-3+b1
ii libvulkan1 1.4.309.0-1
ii libwayland-client0 1.23.1-3
ii libwayland-cursor0 1.23.1-3
ii libwayland-egl1 1.23.1-3
ii libx11-6 2:1.8.12-1
ii libxext6 2:1.3.4-1+b3
ii libxkbcommon0 1.7.0-2
ii libxpresent1 1.0.1-1+b2
ii libxrandr2 2:1.5.4-1+b3
ii libxss1 1:1.2.3-1+b3
ii libxv1 2:1.0.11-1.1+b3
ii libzimg2 3.0.5+ds1-1+b2
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
Versions of packages mpv recommends:
ii xdg-utils 1.2.1-2
ii yt-dlp 2025.03.26-1
Versions of packages mpv suggests:
pn libcuda1 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2025-04-08 09:16:32 +0000, [email protected] wrote:
>
> I am away from the computer that was giving me the issue and using another
> machine that does not have the same problem, it has an Intel built in GPU,
> MPV 0.40.0-2 shows up as VAAPI without problem. I think the issue is with my
> new Trixie install missing some driver on my original machine, so please
> close this issue (I am afraid I can't seem to find how to do that). Cheers!
Closing
Cheers
--
Sebastian Ramacher
--- End Message ---
