Package: mpv Version: 0.42.0-2 Severity: minor Hi.
I'm still often not using Pipewire (PW) and thus don't have it installed on those machines either, mpv is just configured to use Alsa. Note that in Debian anyway, mpv thankfully does not depend on the entire PW kit, only on libpipewire which in turn merely suggests PW. Spurious warnings about "client.conf" missing were seen in older versions, though usually only in syslog. I don't remember when but at some point those stopped which made a lot of sense to me, the presence of PW should be easily obtainable by other means. If it's not there, no use telling users about missing config files they do not in fact miss. With 0.42.0-2 the trouble has unfortunately returned, although now it's also printing (W+E) on the terminal where mpv is running, "can't load config client.conf...", the output in fact overlapping with hence garbling mpv's relevant stdout. Which even though cosmetic is unacceptable and considered a bug. Mpv isn't least renowned for its minimalism, it runs fine with nothing available but alsa (and of course, with no audio), it should not complain about optional components. At the very least we should have some means or an option to silence this that's more specific and conservative than --msg-level. What doesn't work is simply placing an empty client.conf in $HOME/.config/pipewire. Oliver

