You are not logged in.
In case anyone else finds that mpd stopped working with latest updates.
In /var/log/mpd/mpd.conf I found:
Oct 05 19:28 : output: Failed to open "My ALSA Device" [alsa]: Failed to open ALSA device "default": Connection refused
I solved it by (as root):
mv /etc/asound.conf /etc/asound.conf.trash
After a restart of mpd it should work again.
Offline
nice tip, thx for sharing!
Offline
In case anyone else finds that mpd stopped working with latest updates.
In /var/log/mpd/mpd.conf I found:
Oct 05 19:28 : output: Failed to open "My ALSA Device" [alsa]: Failed to open ALSA device "default": Connection refusedI solved it by (as root):
mv /etc/asound.conf /etc/asound.conf.trashAfter a restart of mpd it should work again.
But do you know what you actually did?
Offline
frodoontop wrote:In case anyone else finds that mpd stopped working with latest updates.
In /var/log/mpd/mpd.conf I found:
Oct 05 19:28 : output: Failed to open "My ALSA Device" [alsa]: Failed to open ALSA device "default": Connection refusedI solved it by (as root):
mv /etc/asound.conf /etc/asound.conf.trashAfter a restart of mpd it should work again.
But do you know what you actually did?
If you have pulse installed a) use it or b) disable its autospawn feature...
for a) install pulseaudio-alsa and set up mpd to use it. for b) use google. its something like autospawn=no in some pulseaudio config file
He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.
Douglas Adams
Offline
I solved this problem by changing the user of the mpd deamon to myself (the one who run pulseaudio via gnome 3). Doing that you also need to change the owner of the files that mpd write to (defined in /etc/mpd.conf).
Offline