[pulseaudio-tickets] [PulseAudio] #575: PA doesn't work in r/o $HOME.
PulseAudio
trac-noreply at tango.0pointer.de
Tue Jun 9 18:34:02 PDT 2009
#575: PA doesn't work in r/o $HOME.
--------------------------+-------------------------------------------------
Reporter: knightk | Owner: lennart
Type: enhancement | Status: new
Milestone: | Component: daemon
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Comment(by knightk):
I'll work on a patch for compatibility for r/o $HOME.
PACAT's stream_read_callback() not called
-----------------------------------------
I have successfully used arecord to capture audio on my ARMv6 target so I
know my hardware is good. When I attempt to use pacat -r -v I do not see
any calls to stream_read_callback(pa_stream *s, size_t length, void
*userdata)! Connection is established and the stream successfully created,
also the time_event_callback is called repeatedly.
On my laptop I don't even need a module-alsa-source loaded to get
stream_read_callback() to get called repeatedly. It is sufficient for me
to launch pulseaudio, load modules module-native-protocol-unix and module-
alsa-sink (would'nt work without the sink!).. then pacat -r -v
paplay "Failed to open file STDIN"
---------------------------------
The other issue is that when attempting to pipe anything to paplay on my
target I get a 'Failed to open file STDIN'. Why paplay can't accept chars
from another app is another puzzle. E.g. madplay -o wave:- file.mp3 |
paplay produces a STDIN issue. madplay -o wave:- file.mp3 fills the screen
with lots of chars... so I know madplay is OK.
Any hints would be very welcome. Thanks
--
Ticket URL: <http://pulseaudio.org/ticket/575#comment:3>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
More information about the pulseaudio-bugs
mailing list