Hi John, On Thu, Jun 27, 2013 at 11:01:56AM -0500, John McMonagle wrote: > Package: pulseaudio > Version: 2.0-6.1 > Severity: important > > Using pulsaudio in ltsp. > I'm upgrading the ltsp-client to wheezy from squeeze. > Under squeeze it worked fine. squeeze uses pulseaudio 0.9.21-3+squeeze1. > > This is the code that starts pulseaudio on the clent: > ............................ > PULSE_DETECT=module-udev-detect > PULSE_VOLUME_RESTORE=module-stream-restore > /usr/bin/pulseaudio --system \ > --exit-idle-time=-1 \ > --disable-shm \ > --no-cpu-limit \ > --resample-method=trivial \ > --high-priority \ > --log-target=syslog \ > -L $PULSE_DETECT \ > -L "module-native-protocol-tcp auth-anonymous=1" \ > -L $PULSE_VOLUME_RESTORE \ > -L module-rescue-streams \ > -L "module-native-protocol-unix auth-anonymous=1" \ > -n & > ..................................... > > Some applications work: > paplay > mplayer > dragon > > The following fail: > vlc > kde system sounds. > > When it fails pactl list will show the source as SUSPENDED. > >>From that point nothing works.
Does this mean that after the first failure no more audio comes out? Would you please attach the output of: Adding the -vvvv flag to pulseaudio exec line (change the log target to file:/tmp/something to get the log) The output of pactl list > > If I kill pulseaudio and start pulseaudio in user mode all aplications works. > > Is this an inherent limitation in system mode or a bug? Looks like a bug, yes. > > I have tested this betwwen 2 wheezy boxes using the script above to start > pulseaudio and have the same issues. Lets try to figure this one out. By the way, do you really need system mode? I'm not quite sure what ltsp is, but I suspect that is why you want system mode? -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
