--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: mpv: Can't play directory of zip files after ffmpeg bump
- From: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
- Date: Fri, 03 Jan 2025 15:10:30 +0100
- Message-id: <173591343066.106320.9567454159508987264.reportbug@probook>
Package: mpv
Version: 0.39.0-1
Severity: normal
Hi,
recently, one of my scripts for playing music broke:
$ mpv --shuffle ~/music/tracked/modarchive
Failed to recognize file format.
Exiting... (Errors when loading file)
The modarchive directory in this example contains (subdirectories with)
zip files that individually play just fine.
Based on timing, this was was probably the 0.39.0 update of mpv, and
0.38.0 was fine. I've manually built mpv 0.37.0, and it's also broken,
so I suspect the culprit to be:
* debian/contrl: Bump ffmpeg dependencies to 7:6.1
How to reproduce:
# go to a new directory
cp /usr/share/sounds/alsa/*.wav . # get example files
mpv . # works, MPV plays files in directory
for i in *; do zip $i.zip $i; done # zip all files
rm *.wav # remove unzipped files
mpv Front_Center.wav.zip # zipped file still plays
mpv . # "Failed to recognize file format." - previously this worked.
Best regards,
-- jn
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.6-amd64 (SMP w/12 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 mpv depends on:
ii libarchive13t64 3.7.4-1.1
ii libasound2t64 1.2.12-1+b1
ii libass9 1:0.17.3-1+b1
ii libavcodec61 7:7.1-3+b1
ii libavdevice61 7:7.1-3+b1
ii libavfilter10 7:7.1-3+b1
ii libavformat61 7:7.1-3+b1
ii libavutil59 7:7.1-3+b1
ii libbluray2 1:1.3.4-1+b2
ii libc6 2.40-4
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-4.2+b1
ii libdrm2 2.4.123-1
ii libdvdnav4 6.1.1-3+b1
ii libegl1 1.7.0-1+b2
ii libgbm1 24.2.8-1
ii libjack-jackd2-0 [libjack-0.125] 1.9.22~dfsg-4
ii libjpeg62-turbo 1:2.1.5-3+b1
ii liblcms2-2 2.16-2
ii liblua5.2-0 5.2.4-3+b3
ii libmujs3 1.3.5-1
ii libpipewire-0.3-0t64 1.2.7-1+b1
ii libplacebo349 7.349.0-3
ii libpulse0 17.0+dfsg1-1
ii librubberband2 3.3.0+dfsg-2+b3
ii libsdl2-2.0-0 2.30.10+dfsg-1
ii libsixel1 1.10.3-3+b2
ii libsndio7.0 1.10.0-0.1
ii libswresample5 7:7.1-3+b1
ii libswscale8 7:7.1-3+b1
ii libuchardet0 0.0.8-1+b2
ii libva-drm2 2.22.0-1+b1
ii libva-wayland2 2.22.0-1+b1
ii libva-x11-2 2.22.0-1+b1
ii libva2 2.22.0-1+b1
ii libvdpau1 1.5-3+b1
ii libvulkan1 1.3.296.0-1
ii libwayland-client0 1.23.0-1+b1
ii libwayland-cursor0 1.23.0-1+b1
ii libwayland-egl1 1.23.0-1+b1
ii libx11-6 2:1.8.10-2
ii libxext6 2:1.3.4-1+b2
ii libxkbcommon0 1.7.0-2
ii libxpresent1 1.0.1-1+b1
ii libxrandr2 2:1.5.4-1+b2
ii libxss1 1:1.2.3-1+b2
ii libxv1 2:1.0.11-1.1+b2
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 2024.12.23-1
Versions of packages mpv suggests:
pn libcuda1 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: mpv
Version: 0.40.0-3
thanks
Hi Jonathan,
thanks for reporting, I'm marking as fixed in 0.40.0-3 and close this
bug
Regards,
Lorenzo
On Fri, 11 Apr 2025 12:50:34 +0200 =?utf-8?Q?J=2E_Neusch=C3=A4fer?=
<j.neuschaefer@gmx.net> wrote:
> As of today, this works again on my system!
>
> Version information:
>
> $ mpv --version
> mpv v0.40.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
> libplacebo version: v7.349.0
> FFmpeg version: 7.1.1-1+b1
> FFmpeg library versions:
> libavcodec 61.19.101
> libavdevice 61.3.100
> libavfilter 10.4.100
> libavformat 61.7.100
> libavutil 59.39.100
> libswresample 5.3.100
> libswscale 8.3.100
>
>
> Big thanks to everyone who worked on fixing this (possibly without
> even reading this bug report).
>
>
--- End Message ---