|
Ok so even opening QasMixer will currently get PA to spawn when it wasn't previously running. I see Pulse is listed under Mixer Devices, plus it also appears very likely that is the mixer currently set as my Default from looking at the layout.
Is there some configuration to Alsa I should do to prevent this when not using PA? Dale. From: dj_kaza@xxxxxxxxxxx To: len@xxxxxxxxxxxxx CC: linux-audio-user@xxxxxxxxxxxxxxxxxxxx Subject: RE: Ubuntu Studio 14.04 Pulse removal question Date: Tue, 12 Aug 2014 06:59:24 +0000 *(PA) definitely was still loading at startup* I just had a thought as to the cause of this. I think I might have still had my Volume widget in my Panel showing the control from PA at that point and since changed it to display amixer's. From what you say this likely would have caused PA to start, even though I had disabled it in Autostart. Hope you forgive me for not confirming this was the cause right now :) Dale. From: dj_kaza@xxxxxxxxxxx To: len@xxxxxxxxxxxxx CC: linux-audio-user@xxxxxxxxxxxxxxxxxxxx Subject: RE: Ubuntu Studio 14.04 Pulse removal question Date: Tue, 12 Aug 2014 06:40:59 +0000 > Date: Mon, 11 Aug 2014 23:20:05 -0700 > From: len@xxxxxxxxxxxxx > To: dj_kaza@xxxxxxxxxxx > CC: linux-audio-user@xxxxxxxxxxxxxxxxxxxx > Subject: RE: Ubuntu Studio 14.04 Pulse removal question > > On Tue, 12 Aug 2014, Kaza Kore wrote: > > > As far as I know and can tell -k stands for Kill. if you run it twice it > > informs you PA is not running! > > Yes but pulse is configured respawn by default, it does take some time to > restart, but does so as soon as you kill it. Doesn't seem to be respawning now, definitely was still loading at startup before I added the pulseaudio -k command to jack options but my laptop has been running all night, so up for maybe 16 hours since last reboot and this is my output from trying to kill pulseaudio in terminal. $ pulseaudio -k E: [pulseaudio] main.c: Failed to kill daemon: No such process Clearly not respawned itself in all that time. But the fact it will do if any program requests it is quite a good hint for me, and hopefully I will see a change if it pops up again when I try and use something. > > > > As I stated I had unchecked the all Pulse related options in the Autostart > > settings and it still starts on reboot! > > That could be... all it takes is something asking via D-bus if pulse is > there... and then it is. > > My personal solution has been to unload module-jackdbus-detect when I do > not want pulse connected to jack. pulse takes almost no cpu that way. The > command to unload the module is: > > pactl unload-module module-jackdbus-detect Once I'm totally sure nothing is trying to access pulse any more I might add this line. Is there any difference between adding it to rc.local and adding it as an Autostart option, like I did with qjackctl? > > The package pulseaudio-module-jack can be removed to make this more > permanent, but if you will not use pulse maybe just: > > sudo chmod -x /usr/bin/pulseaudio And then this when even more confident ;) > > There may be depends problems if you remove the pulseaudio package > itself... for example you browser may be removed as well. Debian depends > are there to protect dummys. > Yeah I worried and thought I had heard there could be problems with removing. So I aim to fully ensure it's never running and I can be happy with that :) > -- > Len Ovens > www.ovenwerks.net > Dale. |
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
