If the mpd init script only "use"s alsasound, alsasound may be stopped before it is. However, this will cause mpd to die messily. If that happens, the state file may not be properly saved, so it will totally lose its functionality. Reproducible: Always Steps to Reproduce: 1. Shutdown or reboot your system. Actual Results: MPD's state may not be properly saved. eg. music will not resume playing on restart, or it may play when it had not been on the last restart. Expected Results: it should be allowed to die nicely [i.e. before its sound drivers are removed] I happen to be using media-sound/mpd-0.11.5.
*** Bug 102092 has been marked as a duplicate of this bug. ***
anything can be done with that? it's rather old...
"after alsasound" doesn't make mpd service stop when alsasound service is being stopped, we need "need alsasound" for that. Probably the only viable solution is to add it to the newly installed initscript, if the alsa USE flag is enabled. I did that in the mpd-svn package, and it has worked nicely for quite some time now. This has been added to the 0.11.5 ebuild, as well as new (unstable) 0.11.5-r1 ebuild. Resync your portage tree in few hours. Thanks for reporting, and for the patience.
Thank you kindly, Sir, for fixing it. The wait was not a problem.
