One way to go around this without using network access is to edit
daemon.conf and client.conf (usually in /etc/pulse) and have them use a
pulse-cookie file. The way I did it before was to get that file saved as
/etc/pulse-cookie, set it g+w for 'pulse-access' group, for example, and add
'mpd'
I thought I'd give xubuntu 9.10 a try, and it seems to use pulseaudio now.
I'm having a bit of trouble getting mpd to work with it. When mpd tries to
play, it launches its own pulseaudio instance. This works fine as far as
mpd is concerned - it's able to play to it - but there's no sound. I
Yeah, I thought of this, and network access, and system-wide pulseaudio.
Uninstalling pulseaudio works pretty well too. Just wondering if there's a
non-workaround solution.
On Sat, Oct 31, 2009 at 11:35 AM, Matt Wheeler m...@funkyhat.org wrote:
Perhaps not a wonderful solution, but my
On 2009/10/31 17:40, Jeffrey Middleton jefr...@gmail.com wrote:
Yeah, I thought of this, and network access, and system-wide pulseaudio.
Uninstalling pulseaudio works pretty well too. Just wondering if there's a
non-workaround solution.
Running MPD as your user is usually not a good idea.
None of these are really good options:
* run mpd as your user - security
* network access to pulseaudio - kludge at best
* system-wide pulseaudio daemon - tons of problems:
http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode
I guess it's just not meant to be! Fortunately I don't really have
