[SOLVED] MPD doesn't consistently save the player state.

Beelzebud · 2014-03-20 02:21:23

I'm not sure what exact version this cropped up in, but I've noticed for the past 2 weeks that most of the time when I start my Linux machine MPD will begin playing something from the previous session. It seems to be saving the state during a session, but not when the session is being closed. Anyone else getting this behavior? I've checked my mpd.state file for permissions, and everything seems like it should be.

Last edited by Beelzebud (2014-04-13 17:30:09)

o_caino · 2014-03-20 11:53:20

Same for me.

Beelzebud wrote:

MPD will begin playing something from the previous session

Yes, sometimes not necessarily last song played.

Psykorgasm · 2014-03-20 12:08:15

I've had it also within the past 2/3 weeks, something else too though;

I've had it completely clear my playlist and ncmpcpp just open up completely empty or maybe only load songs up to a certain artist a few letters in to the alphabet, at first I thought it was mpd auto_update which (most likely by luck/coincidence) stopped it for about a week but then it happened again.

Rasi · 2014-03-20 23:20:41

We also had some complain about state file not properly being saved on reboots in the irc channel. Sadly they were not able to provide a git bisect.
If one of you could provide one, I would appreciate this, since I wasn't able to reproduce this issue.

My guess tho is, that this is something in systemd, since a) everyone who was complaining also used systemd and b) it only happened on reboots.

Last edited by Rasi (2014-03-20 23:26:07)

curson · 2014-03-20 23:32:39

I'm having this issue as well. The ~/.config/mpd/mpdstate file is devour of playlist information most of the time and my client of choice starts, of course, with an empty playlist. I still haven't figured out what is triggering this behaviour, and while easy to solve, it really seems to happen in a very unpredictable and totally random ways.

Glad, in a way, I'm not the only one experiencing this, but as the others (few) in this thread have stated, I have no clues on how to solve this.

o_caino · 2014-03-21 00:17:37

I don't know if this is relevant, but even though I use systemd I don't have mpd.service enabled, I just start mpd in my user's .xinitrc

Psykorgasm · 2014-03-21 09:53:47

o_caino, I too do not use the service, I start mpd myself from a terminal and a friend of mine with the same issue also starts mpd via his xinitrc.

It swear it came with the last update to mpd or the at a stretch the one previous because it was working fine before that for as long as I can remember. As much as I would love to do some bisects of git I just dont have the time to try reproduce it that much, at least not now

Last edited by Psykorgasm (2014-03-21 09:54:17)

Rasi · 2014-03-21 14:57:07

But does it only happen with reboots or is stopping and starting mpd by hand also causing it?

Last edited by Rasi (2014-03-21 14:57:18)

Beelzebud · 2014-03-21 17:31:42

Forgive me for being absent, I haven't had much time.

I'm starting MPD from an autostart script in KDE's autostart folder. I just killed mpd and restarted it a few times, and it seemed to work fine. This only happens on a restart. The weird thing, is that like someone else mentioned, it won't even begin from the last thing that was played, just some random point from the previous session.

It's almost like the state file will get saved once during a session, and then it doesn't save again.

Last edited by Beelzebud (2014-03-21 17:32:34)

Psykorgasm · 2014-03-21 18:18:19

Rasi, only on a new boot but since I don't stop mpd after starting it... who knows.
It wasn't every boot or reboot though, when I was messing with some new kernels I had a failure rate (for lack of a better term) once every probably 4 or 5 starts from memory and the failure were a random mix of OP's and the ones I detailed extra.

Rasi · 2014-03-21 22:10:16

so i stick to my point. in all your cases its the init system that kills mpd. as soon as you cleanly shut it down yourself everything works fine. seems like a systemd issue to me

But again, without a bisect this is a useless discussion

Last edited by Rasi (2014-03-21 22:10:40)

Raynman · 2014-03-21 22:42:38

I think you're right Rasi, I've also started to lose zsh history from instances that I didn't exit before shutting down.

curson · 2014-03-31 06:35:49

My problem about starting mpd.service through systemd, has always been the inability to by-pass the permission problem on Pulseaudio. Launching mpd through my .xinitrc has worked flawlessly for a long time, but it's now clear that mpd doesn't update/save the mpdstate file anymore, as I have random problems with playlist disappearing, play state being either play/stop and so on.

Is there a straightforward way to make mpd work through systemd without running in the permission problems for the audio device? Because if the culprit lies with .xinitrc (and the fact that mpd doesn't feel it's closed properly anymore), then it's worth a try.

Rasi · 2014-04-01 22:25:43

curson wrote:

My problem about starting mpd.service through systemd, has always been the inability to by-pass the permission problem on Pulseaudio. Launching mpd through my .xinitrc has worked flawlessly for a long time, but it's now clear that mpd doesn't update/save the mpdstate file anymore, as I have random problems with playlist disappearing, play state being either play/stop and so on.
Is there a straightforward way to make mpd work through systemd without running in the permission problems for the audio device? Because if the culprit lies with .xinitrc (and the fact that mpd doesn't feel it's closed properly anymore), then it's worth a try.

[Unit]
After=network.target
After=sound.target

[Service]
User=YOUR_USER
PAMName=system-local-login
ExecStart=/usr/bin/mpd --no-daemon

[Install]
WantedBy=multi-user.target

curson · 2014-04-02 09:58:02

Yep, after posting that, I kind of figured out what I was doing wrong with that, and managed to use systemd user session to start mpd. So far, it seems that might have fixed the issue for me, but I need to give it some more tries just to be sure.

Anyway, thank you for your reply Rasi

Beelzebud · 2014-04-13 17:29:39

Again, apologies for not keeping up with this, I've been busy. Last night mpd had an update, and afterwards I noticed that it was starting with systemd by default now, and it all seems to be working fine. I haven't had any weirdness with state saves after a couple of test restarts, so I'm going to label this solved.

Arch Linux

#1 2014-03-20 02:21:23

[SOLVED] MPD doesn't consistently save the player state.

#2 2014-03-20 11:53:20

Re: [SOLVED] MPD doesn't consistently save the player state.

#3 2014-03-20 12:08:15

Re: [SOLVED] MPD doesn't consistently save the player state.

#4 2014-03-20 23:20:41

Re: [SOLVED] MPD doesn't consistently save the player state.

#5 2014-03-20 23:32:39

Re: [SOLVED] MPD doesn't consistently save the player state.

#6 2014-03-21 00:17:37

Re: [SOLVED] MPD doesn't consistently save the player state.

#7 2014-03-21 09:53:47

Re: [SOLVED] MPD doesn't consistently save the player state.

#8 2014-03-21 14:57:07

Re: [SOLVED] MPD doesn't consistently save the player state.

#9 2014-03-21 17:31:42

Re: [SOLVED] MPD doesn't consistently save the player state.

#10 2014-03-21 18:18:19

Re: [SOLVED] MPD doesn't consistently save the player state.

#11 2014-03-21 22:10:16

Re: [SOLVED] MPD doesn't consistently save the player state.

#12 2014-03-21 22:42:38

Re: [SOLVED] MPD doesn't consistently save the player state.

#13 2014-03-31 06:35:49

Re: [SOLVED] MPD doesn't consistently save the player state.

#14 2014-04-01 22:25:43

Re: [SOLVED] MPD doesn't consistently save the player state.

#15 2014-04-02 09:58:02

Re: [SOLVED] MPD doesn't consistently save the player state.

#16 2014-04-13 17:29:39

Re: [SOLVED] MPD doesn't consistently save the player state.

Board footer