Duplicate pulsaudio process
GoogleCodeExporter opened this issue · 2 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. Start Ubuntu 14.04 - one pulseaudio running
teo@Kodi:~$ ps -ef | grep -e "pulse" -e "squeezelite"
teo 1522 1147 0 12:30 ? 00:00:00 /usr/bin/pulseaudio --start
--log-target=syslog
teo 1603 1522 0 12:30 ? 00:00:00
/usr/lib/pulseaudio/pulse/gconf-helper
teo 2645 2018 0 12:32 pts/2 00:00:00 grep --color=auto -e pulse -e
squeezelite
2.Start Squeezelite with -o pulse as user teo
sudo start-stop-daemon --start --quiet -b -m -p /var/run/squeezelite.pid
--chuid teo --exec /usr/bin/squeezelite-x86-64 -- -o pulse -n Obývák
3. Second pulseaudio process is out there fighting for HW with first one!!!
teo@Kodi:~$ ps -ef | grep -e "pulse" -e "squeezelite"
teo 1522 1147 0 12:30 ? 00:00:00 /usr/bin/pulseaudio --start
--log-target=syslog
teo 1603 1522 0 12:30 ? 00:00:00
/usr/lib/pulseaudio/pulse/gconf-helper
teo 2934 1 2 12:33 ? 00:00:00 /usr/bin/squeezelite-x86-64 -o
pulse -n Obývák
teo 2939 1 5 12:33 ? 00:00:01 /usr/bin/pulseaudio --start
--log-target=syslog
teo 2941 2939 0 12:33 ? 00:00:00
/usr/lib/pulseaudio/pulse/gconf-helper
after trying play from Rhytmbox
tail /var/log/syslog
Dec 29 12:41:45 Kodi pulseaudio[1522]: [alsa-sink-HDMI 0] alsa-sink.c: Error
opening PCM device hdmi:0: Zařízení nebo zdroj jsou používány
What is the expected output? What do you see instead?
Be able to play by squeezelite and desktop sounds same time and avoid failures
to open hw device
What version of the product are you using? On what operating system?
Ubuntu 14.04
Squeezelite v1.6.5
Thank you!
Original issue reported on code.google.com by tomas.vr...@gmail.com on 29 Dec 2014 at 11:46
GoogleCodeExporter commented
Squeezelite does not do anything specific for pulse audio it it just opens the
output device using alsa api calls. It is likely the problem is with your
startup script? Note squeezelite won't understand the -- option you have on
the command string though.
Original comment by trio...@btinternet.com on 29 Dec 2014 at 12:26
GoogleCodeExporter commented
It's a problem with pulseaudio - set autospawn=no in /etc/pulse/client.conf.
It's apparently different than the commented out autospawn=yes that's already
there.
Original comment by connor....@gmail.com on 26 Apr 2015 at 6:02