On Mon, Mar 24, 2014 at 11:46:49AM +0100, David Coppa wrote: > On Mon, Mar 24, 2014 at 11:41 AM, Landry Breuil <[email protected]> wrote: > > On Mon, Mar 24, 2014 at 11:28:46AM +0100, Landry Breuil wrote: > >> On Mon, Mar 24, 2014 at 11:15:04AM +0100, David Coppa wrote: > >> > On Mon, Mar 24, 2014 at 11:11 AM, Landry Breuil <[email protected]> > >> > wrote: > >> > > On Mon, Mar 24, 2014 at 10:25:14AM +0100, David Coppa wrote: > >> > >> On Mon, Mar 24, 2014 at 1:59 AM, Bryan Linton <[email protected]> > >> > >> wrote: > >> > >> > On 2014-03-23 22:48:28, Landry Breuil <[email protected]> wrote: > >> > >> > >> > >> >> - for some reason here mpd inexplicably stops playing after ending > >> > >> >> a > >> > >> >> track, and 'mpc play' or telnetting to 6600 and issuing 'play' > >> > >> >> doesnt > >> > >> >> resume it, it still seems to think it's playing. I need to kill it > >> > >> >> and > >> > >> >> restart it for another track to properly play. Anyone experiencing > >> > >> >> this ? > >> > >> >> Tried with/without random/consume modes. > >> > >> >> > >> > >> >> Please test this.. > >> > >> >> > >> > >> > > >> > >> > I think I'm seeing the same bug here: > >> > >> > >> > >> Can you try if the attached patch helps? > >> > >> > >> > >> From: http://bugs.musicpd.org/view.php?id=3860 > >> > > > >> > > Nope, no change. I'm also seeing weird mpd internal state, the > >> > > currently > >> > > played track is not the one given by the currentsong command - as brian > >> > > said. > >> > > > >> > > Tried disabling sndiod, only using the libao output, only the httpd > >> > > output - no luck. I still need to kill mpd and start it again to make > >> > > it > >> > > play one track. > >> > > > >> > > >> > So, we're in the same boat with FreeBSD: > >> > > >> > http://bugs.musicpd.org/view.php?id=3944 > >> > >> Nice.. can you pile on to ensure this is properly handled/debugged ? > >> Setting log_level to verbose doesnt give much more information... > > > > After looking a wee bit more, the /var/spool/mpd/mpdstate file has a > > weird entry: > > time: -2147483648 > > > > with 0.17.6 and a new playlist i have 'time: 259' > > > > Maybe that's related.. > > Uhm... 64bit time_t fuckup?
Fwiw, after moving away the mpdstate file with the weird time entry, and recreating my playlist, i havent had any issues with 0.18.9. Maybe in some circumstances mpd gets confused with its internal state (as brian linton described in his STRs), but so far i've monitored the time: entry in the current mpdstate file and it stayed at 'normal' values.. Landry
