[Pkg-mpd-maintainers] Bug#933301: mpd: systemd service doesn't use user configured UNIX socket since last update

Florian Schlichting fsfs at debian.org
Thu Nov 7 10:34:03 GMT 2019


Hi Simon,

On Tue, Oct 01, 2019 at 04:14:40PM +0200, kaliko wrote:
> On Sun, 28 Jul 2019 17:14:08 -0400 Simon Désaulniers <sim.desaulniers at gmail.com> wrote:
> > […] 
> > After upgrading from 0.21.5-3 to 0.21.11-1, systemd's mpd service doesn't seem
> > to use the UNIX socket configured from my mpd configuration located at
> > /home/simon/.config/mpd/mpd.conf.
> > […]
> 
> I did not manage to reproduce the issue.
> I'll try again later on a freshly installed VM upgraded to testing, but so far I have
> not been able to reproduce the issue (tested also with mpd 0.21.15).
> 
> Maybe someone from MPD team is willing to give it a shot.

with version 0.21.8, mpd gained a _user_ mpd.socket unit, which defines

    ListenStream=%t/mpd/socket
    ListenStream=6600

and is enabled by default. My feeling is that this is responsible for
your observed differences between using systemctl and manually launching
mpd. Did mpd.socket get stopped/restarted in your testing?

HTH,
Florian



More information about the Pkg-mpd-maintainers mailing list