After disabling/stopping the system-wide mpd instance, a user mpd will
be started on login provided an .mpdconf can be found
** Changed in: mpd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
my bad. mpd is running as a dedicated user, not as the login user.
--
no other-sound when switching user
https://bugs.launchpad.net/bugs/469441
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
mpd DOES run per-user. If reporter's experience is anything like my
own, what's actually happening is mpd is trying and failing to setup
pulse audio and falling back to alsa. this prevents other users with
pulseaudio from accessing the soundcard.
--
no other-sound when switching user
https://bu
I think there is a philosophical problem between mpd and pulseaudio. How can a
systemwide mpd use a user pulseaudio server without having any troubles at all
??? Two solution come in mind:
* Configure pulseaudio systemwide, which is definitely not recommended by its
devs.
* Configure mpd to be a
