'Twas brillig, and Ng Oon-Ee at 24/04/09 10:42 did gyre and gimble:
I'm part-way to a solution, but am not sure whether I'm doing things
right, please comment.
Currently, I notice the variables PULSE_SERVER and the like are not set
on my Arch Linux install. Setting them did not make a difference,
initially, until I did further things.
Basically, I changed pulseaudio to a system-wide instance (starting as
root with --system), copied the /var/run/pulse/.pulse-cookie to
/etc/pulse-cookie in the 32-bit chroot, did the appropriate chown to
pulse:pulse-access and chmod 640 to the cookie, and was able to play
sound using paplay -s localhost. It also works with PULSE_SERVER=localhost.
As I understand it, what I'm doing is using pulseaudio over a network
(though the chroot is actually on the same machine). All I'd have to do
now is set the PULSE_SERVER environment variable to get sound working.
Is this the right way to do it? Seems overly complicated for a
single-machine setup to me. Please advise.
I'd very much advise *against* using a system wide pulseaudio. It's only
really appropriate in certain special circumstances and this isn't one
of them :)
You should not need to set your PULSE_SERVER env var as it should be
worked out automatically.
I'd double check Lennart's reply as his comment about ensureing /tmp is
shared in and out of the chroot is probably the point at which your
original setup is failing.
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
_______________________________________________
pulseaudio-discuss mailing list
[email protected]
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
