Re: Where is pulseaudio started?
Some people had asked to keep this thread going so here is what I've found so far. (Note That I'm using GNOME and GDM so I started with GDM. There is, no doubt, something for equivalent KDE) For those who want the short version, I still don't have it figured out yet but I now think that the autostart of the xdg directory *.desktop files is called from within gnome-session. I found this page: http://library.gnome.org/admin/gdm/2.26/gdm.html This describes how GDM executes a number of scripts during the login process: Init PostLogin PreSession Xsession The Init script is located in /etc/gdm/Init/Default and has nothing to do with PA which I sort of already knew as PA gets started during the login process not before it The PostLogin script would be called would be called /etc/gdm/PostLogin/Default if one existed but on my system it has been renamed to Default.sample and is empty. The PreSession script is located in /etc/gdm/PreSession/Default and this also has nothing to do with PA. Section 5.3 of the html doc above says There is also an Xsession script located at etc/gdm/Xsession which is called between the PreSession and the PostSession scripts. ...This script is run as the user, and it will run whatever session was specified by the Desktop session file the user selected to start. Looking at this script you can see that it is indeed this file that starts the gnome-session. The web page above has a section called Autostart Configuration which says The share/gdm/autostart/LoginWindow directory contains files in the format specified by the FreeDesktop.org Desktop Application Autostart Specification. Standard features in the specification may be used to specify programs should auto-restart or only be launched if a GConf configuration value is set, etc. Any .desktop files in this directory will cause the associated program to automatically start with the login GUI greeter. # ls -g /usr/share/gdm/autostart/LoginWindow -rw-r--r-- 1 root 2250 2008-12-18 18:31 at-spi-registryd-wrapper.desktop -rw-r--r-- 1 root 2570 2008-12-18 18:31 gdm-simple-greeter.desktop -rw-r--r-- 1 root 4835 2008-12-18 18:31 gnome-mag.desktop -rw-r--r-- 1 root 4440 2008-12-18 18:31 gnome-power-manager.desktop -rw-r--r-- 1 root 2302 2008-12-18 18:31 gnome-settings-daemon.desktop -rw-r--r-- 1 root 4986 2008-12-18 18:31 gok.desktop -rw-r--r-- 1 root 1333 2008-12-18 18:31 metacity.desktop -rw-r--r-- 1 root 6449 2008-12-18 18:31 orca-screen-reader.desktop -rw-r--r-- 1 root 171 2008-11-17 15:52 plymouth-log-viewer.desktop (The -g is just to keep the lines shorter) So, as you can see, no pulseaudio.desktop here. My conclusion so far is that pulseaudio is started by autostart and that the /etc/xdg/autostart/*.desktop files are called from within gnome-session. I need to research gnome-session next. Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Tuesday 01 September 2009 15:56:30 Steve Blackwell wrote: Some people had asked to keep this thread going so here is what I've found so far. (Note That I'm using GNOME and GDM so I started with GDM. There is, no doubt, something for equivalent KDE) [snip] My conclusion so far is that pulseaudio is started by autostart and that the /etc/xdg/autostart/*.desktop files are called from within gnome-session. I need to research gnome-session next. The actual pulseaudio binary is executed by the script /etc/pulse/default.pa (at the very first line), so maybe you can do a full-text search on gnome config files and scripts to find out where is this script being invoked. I don't use gnome, so can't help much on that. And yes, keep the thread going. As for me, I don't want to disable pulseaudio (it Just Works on my machine), but am interested in understanding the details of its invocation and interaction with the rest of the system. HTH, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
At 14:49 on 27 Aug 2009, Steve Blackwell wrote: On Fri, 28 Aug 2009 00:12:39 +0930 Tim ignored_mail...@yahoo.com.au wrote: On Thu, 2009-08-27 at 10:12 -0400, Steve Blackwell wrote: I'd like to know where (which file) the information is stored in and what program starts it. gdm? gnome? gconf? A hint for finding out things like that: Change a setting, and search for a very recently changed file. Interesting. I had already found a directory called ~/.config/autostart but there was no hint of anything pulseaudio related in there. Then I followed your suggestion and disabled its autostart and searched for recently changed files. Now there is a file called ~/.config/pulseaudio.desktop. That is backward to what I would have expected and if I enable pulseaudio again, the file is removed. Come on, it's not exactly rocket-science. Perhaps you could start by reading what you've posted: The pulseaudio.desktop file contains this: [Desktop Entry] snip X-GNOME-Autostart-enabled=false Look also in /etc/xdg/autostart/ and at http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html -- Mark Knoop -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Fri, 28 Aug 2009 10:10:47 +0100 Mark Knoop m...@opus11.net wrote: At 14:49 on 27 Aug 2009, Steve Blackwell wrote: On Fri, 28 Aug 2009 00:12:39 +0930 Tim ignored_mail...@yahoo.com.au wrote: On Thu, 2009-08-27 at 10:12 -0400, Steve Blackwell wrote: I'd like to know where (which file) the information is stored in and what program starts it. gdm? gnome? gconf? A hint for finding out things like that: Change a setting, and search for a very recently changed file. Interesting. I had already found a directory called ~/.config/autostart but there was no hint of anything pulseaudio related in there. Then I followed your suggestion and disabled its autostart and searched for recently changed files. Now there is a file called ~/.config/pulseaudio.desktop. That is backward to what I would have expected and if I enable pulseaudio again, the file is removed. Come on, it's not exactly rocket-science. Well, I'm not exactly a rocket scientist. Perhaps you could start by reading what you've posted: The pulseaudio.desktop file contains this: [Desktop Entry] snip X-GNOME-Autostart-enabled=false Even mere non-rocket-scientist-mortals like me can read. It's not the fact that there is a line disabling autostart that puzzled me, it was the fact that the file was removed altogether when PA did get autostarted so then what caused start-pulseaudio-x11 to be run? Look also in /etc/xdg/autostart/ and at http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html This provides the answer. If $XDG_CONFIG_HOME and $XDG_CONFIG_DIRS are not set and the two files /etc/xdg/autostart/foo.desktop and ~/.config/autostart/foo.desktop exist then only the file ~/.config/autostart/foo.desktop will be used because ~/.config/autostart/ is more important than /etc/xdg/autostart/ So when ~/.config/pulseaudio.desktop is removed, /etc/xdg/autostart/pulseaudio.desktop is used instead and this file contains the start-pulseaudio-x11. Do you have any links to more information about autostart? For instance, how does it interact with GDM? Thanks, Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Wed, Aug 26, 2009 at 13:03, Jonathan Ryshpan jonr...@pacbell.net wrote: On Wed, 2009-08-26 at 09:25 +0200, Roberto Ragusa wrote: stan wrote: If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. Isn't autospawn activated by default in /etc/pulse/client.conf? That means you can have pulseaudio started by who knows what. I don't think so. On my system (Fedora-11 vanilla) autospawn is commented out. autospawn is the default setting. They listed in the file anyway for documentary purposes. In order to disable it, you would un-comment that line and set it manually. -Ryan -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Thu, Aug 27, 2009 at 02:49:15PM -0400, Steve Blackwell wrote: On Fri, 28 Aug 2009 00:12:39 +0930 Tim ignored_mail...@yahoo.com.au wrote: [stuff about /etc/xdg/autostart/pulseaudio] I'm struggling to turn off pulseaudio as well and tackled the pulseaudio.desktop file by removing pulseaudio-module-x11. This also removes kde-settings-pulseaudio, which is ok by me. I seem to be able to get KDE to not launch pulseaudio well enough. As soon as I invoke gnome-control-center, pulseaudio starts up again. The dialog boxes and setting options from gnome-control-center do not make much sense to me - where is my option to choose ALSA and explicitly turn off everything else? I resorted to going to the Startup Applications box and turning off everything. The other thing I did was removed: /etc/alsa/pulse-default.conf and also moved /usr/share/alsa/alsa.conf to /etc/alsa/ which got me part of the way there. Please keep this thread going. We need a complete guide that explains how to turn off pulseaudio without breaking RPM dependencies. Good luck. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Thursday 27 August 2009 05:16:33 Steven W. Orr wrote: Marko, I thank you for your help. I had read the pa material before but I did not realize that removing it from the system was really not an option. After reading your reply, I upgraded to kde-4.3.0 and that actually made a huge difference. Time will tell, but so far, I do not seem to be getting syslog messages constantly at a rate of about 26 per second. The messages now seem to be only happening when I do something that causes a sound to be generated, and it stops after a second or two with a rate of about 13/second. This is a substantial improvement. I *might* not be feeling so grateful if your answer had not coincided with an upgrade that showed such an improvement ;-) but since it worked out as well as it did, I say we declare victory and withdraw. There's a beer waiting for you if you get to the Boston area. :-) That's good news, I'm glad you got it working better! :-) Best, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Thu, 27 Aug 2009 09:40:24 +0100 Marko Vojinovic vvma...@gmail.com wrote: On Thursday 27 August 2009 05:16:33 Steven W. Orr wrote: Marko, I thank you for your help. I had read the pa material before but I did not realize that removing it from the system was really That's good news, I'm glad you got it working better! :-) Ahem! Can we get back to the subject line? So far we've established that pulsaaudio is started when you log in and that you can turn it off by going to System-Preferences-Personal-Sessions if you have F10 and System-Preferences-Startup Applications if you have F11. I'd like to know where (which file) the information is stored in and what program starts it. gdm? gnome? gconf? Thanks, Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On 09-08-27 10:12:44, Steve Blackwell wrote: ... ... I'd like to know where (which file) the information isstored in and what program starts it. gdm? gnome? gconf? Look in ~/.config. See http://library.gnome.org/devel/autostart-spec/ -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Fri, 28 Aug 2009 00:12:39 +0930 Tim ignored_mail...@yahoo.com.au wrote: On Thu, 2009-08-27 at 10:12 -0400, Steve Blackwell wrote: I'd like to know where (which file) the information is stored in and what program starts it. gdm? gnome? gconf? A hint for finding out things like that: Change a setting, and search for a very recently changed file. Interesting. I had already found a directory called ~/.config/autostart but there was no hint of anything pulseaudio related in there. Then I followed your suggestion and disabled its autostart and searched for recently changed files. Now there is a file called ~/.config/pulseaudio.desktop. That is backward to what I would have expected and if I enable pulseaudio again, the file is removed. The pulseaudio.desktop file contains this: [Desktop Entry] Version=1.0 Encoding=UTF-8 Name=PulseAudio Sound System Comment=Start the PulseAudio Sound System Exec=start-pulseaudio-x11 Terminal=false Type=Application Categories= GenericName= Name[en_US]=PulseAudio Sound System Comment[en_US]=Start the PulseAudio Sound System X-GNOME-Autostart-enabled=false /usr/bin/start-pulseaudio-x11 is a script: comments snipped set -e # Exit without running pulseaudio daemon if this is a remote desktop session [ -n $PULSE_SERVER ] exit 0 /usr/bin/pulseaudio --start $@ if [ x$DISPLAY != x ] ; then /usr/bin/pactl load-module module-x11-publish display=$DISPLAY /dev/null if [ x$SESSION_MANAGER != x ] ; then /usr/bin/pactl load-module module-x11-xsmp display=$DISPLAY session_manager=$SESSION_MANAGER /dev/null fi fi So my remaining questions are what reads the pulseaudio.desktop file and how does pulseaudio get started if it does not exist. Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
Hi; On Thu, 2009-08-27 at 14:49 -0400, Steve Blackwell wrote: On Fri, 28 Aug 2009 00:12:39 +0930 Tim ignored_mail...@yahoo.com.au wrote: The pulseaudio.desktop file contains this: [Desktop Entry] Version=1.0 Encoding=UTF-8 Name=PulseAudio Sound System Comment=Start the PulseAudio Sound System Exec=start-pulseaudio-x11 Terminal=false Type=Application Categories= GenericName= Name[en_US]=PulseAudio Sound System Comment[en_US]=Start the PulseAudio Sound System X-GNOME-Autostart-enabled=false /usr/bin/start-pulseaudio-x11 is a script: comments snipped set -e # Exit without running pulseaudio daemon if this is a remote desktop session [ -n $PULSE_SERVER ] exit 0 /usr/bin/pulseaudio --start $@ if [ x$DISPLAY != x ] ; then /usr/bin/pactl load-module module-x11-publish display=$DISPLAY /dev/null if [ x$SESSION_MANAGER != x ] ; then /usr/bin/pactl load-module module-x11-xsmp display=$DISPLAY session_manager=$SESSION_MANAGER /dev/null fi fi So my remaining questions are what reads the pulseaudio.desktop file and how does pulseaudio get started if it does not exist. Steve I have been following this thread with a great deal of interest. When you finally get it figured out would you please be sure to let us all know. -- Regards Bill Fedora 11, Gnome 2.26.3 Evo.2.26.3, Emacs 23.1.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Thu, 27 Aug 2009 15:24:51 -0400 William Case billli...@rogers.com wrote: I have been following this thread with a great deal of interest. When you finally get it figured out would you please be sure to let us all know. Don't hold your breath! Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
stan wrote: If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. Isn't autospawn activated by default in /etc/pulse/client.conf? That means you can have pulseaudio started by who knows what. -- Roberto Ragusamail at robertoragusa.it -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Wed, 2009-08-26 at 09:25 +0200, Roberto Ragusa wrote: stan wrote: If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. Isn't autospawn activated by default in /etc/pulse/client.conf? That means you can have pulseaudio started by who knows what. I don't think so. On my system (Fedora-11 vanilla) autospawn is commented out. jon -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On 08/26/09 13:03, quoth Jonathan Ryshpan: On Wed, 2009-08-26 at 09:25 +0200, Roberto Ragusa wrote: stan wrote: If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. Isn't autospawn activated by default in /etc/pulse/client.conf? That means you can have pulseaudio started by who knows what. I don't think so. On my system (Fedora-11 vanilla) autospawn is commented out. jon Ok. Why do you think it's commented out? I'm looking at my copy and the comments in the top of the file begin with a #sign but the config lines begin with a semi;colon. So right now I have no idea what's a comment and what's required syntax. Can pulseaudio be simply shut OFF? This thing really stinks. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Wed, 2009-08-26 at 13:39 -0400, Steven W. Orr wrote: On 08/26/09 13:03, quoth Jonathan Ryshpan: On Wed, 2009-08-26 at 09:25 +0200, Roberto Ragusa wrote: stan wrote: If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. Isn't autospawn activated by default in /etc/pulse/client.conf? That means you can have pulseaudio started by who knows what. I don't think so. On my system (Fedora-11 vanilla) autospawn is commented out. jon Ok. Why do you think it's commented out? I'm looking at my copy and the comments in the top of the file begin with a #sign but the config lines begin with a semi;colon. So right now I have no idea what's a comment and what's required syntax. Can pulseaudio be simply shut OFF? This thing really stinks. A comment near the top of /etc/pulse/client.conf reads: ## Configuration file for PulseAudio clients. See pulse-client.conf(5) for ## more information. Default values a commented out. Use either ; or # for ## commenting. I too am interested in not having pulseaudio start at login time, which is why I'm following this thread. jon -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
Steven W. Orr wrote: On 08/26/09 13:03, quoth Jonathan Ryshpan: On Wed, 2009-08-26 at 09:25 +0200, Roberto Ragusa wrote: stan wrote: If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. Isn't autospawn activated by default in /etc/pulse/client.conf? That means you can have pulseaudio started by who knows what. I don't think so. On my system (Fedora-11 vanilla) autospawn is commented out. jon Ok. Why do you think it's commented out? I'm looking at my copy and the comments in the top of the file begin with a #sign but the config lines begin with a semi;colon. So right now I have no idea what's a comment and what's required syntax. Can pulseaudio be simply shut OFF? This thing really stinks. It works for most people, Steven. Some people (myself included) have had issues with it, but that doesn't mean it really stinks. It's started in your session. If you're using Gnome, go to System-Preferences-Startup Applications and scroll down the list. You can uncheck the box next to PulseAudio Sound System to not have it start up, or delete it entirely. There's undoubtedly a similar thing for KDE, but since I'm not a KDE user, I don't know where it is. Someone else want to chime in? -- - Rick Stevens, Systems Engineer ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - If it's stupid and it works...it ain't stupid! - -- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Wed, 26 Aug 2009 10:03:08 -0700 Jonathan Ryshpan jonr...@pacbell.net wrote: On Wed, 2009-08-26 at 09:25 +0200, Roberto Ragusa wrote: stan wrote: If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. Isn't autospawn activated by default in /etc/pulse/client.conf? That means you can have pulseaudio started by who knows what. I don't think so. On my system (Fedora-11 vanilla) autospawn is commented out. jon It's commented out in my F10 system too. I really didn't think that this was going to be a difficult question! I'm assuming that where pulseaudio is started can change from distribution to distribution which is why I'm asking on this list. I don't want to disable pulseaudio, I just want to understand what it does and how it works om my system a little better. Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Wed, 26 Aug 2009 12:21:20 -0700 Rick Stevens ri...@nerd.com wrote: It's started in your session. If you're using Gnome, go to System-Preferences-Startup Applications and scroll down the list. Ah-ha! There's the answer. On my F10 system it is System-Preferences-Personal-Sessions but there is an entry for PA. Now, what I'd like to know is where is the file that stores this info and what reads it when I login. Back in the day it used to be Xsession or something like that. Thanks Rick, Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On 08/26/09 15:21, quoth Rick Stevens: Steven W. Orr wrote: On 08/26/09 13:03, quoth Jonathan Ryshpan: On Wed, 2009-08-26 at 09:25 +0200, Roberto Ragusa wrote: stan wrote: If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. Isn't autospawn activated by default in /etc/pulse/client.conf? That means you can have pulseaudio started by who knows what. I don't think so. On my system (Fedora-11 vanilla) autospawn is commented out. jon Ok. Why do you think it's commented out? I'm looking at my copy and the comments in the top of the file begin with a #sign but the config lines begin with a semi;colon. So right now I have no idea what's a comment and what's required syntax. Can pulseaudio be simply shut OFF? This thing really stinks. It works for most people, Steven. Some people (myself included) have had issues with it, but that doesn't mean it really stinks. You're right. I apologize. I'm sure that for some people it might smell like roses. For some people it may be consuming huge amounts of disk space and system resources and they might not even be aware of it. And yet this thing that really stinks for me has been doing its thing for over 1.5 years generating ~50M syslog entries per week. Unfortunately, I am running KDE-4.2.4 and if there's a way to shut the little stinker off, I'd be grateful to know how. I'm not running a laptop. This is my personal home server. It's where I do all my work and run public server stuff. email, web, sshd, etc. I have no idea what it is that pulseaudio is supposed to actually do that I'm supposed to like about it. I used to have sound. I still have sound. (Not everyone can say that I guess.) But with the syslog thrashing at 50Meg/week and the processes usually sitting at 10% of the cpu just from pulseaudio, I, sincerely, would really like to shut the stinker off. I wish everyone else in the world the very best and that if other people are not having problems then they should continue to not have problems. No one has suggested anything to me to help me fix it and now I'm asking if there's a way to shut the thing off. rpm -ql was of no help. And when it comes to kde-4.2, I love it but it's not all that intuitive a system when it comes to making mods. Please find it in your hearts to dig into your wallets. All I ask is for $30,000 to help me buy the DeLuxe Executive Version of PulseAudio The Gold Edition. I promise that when the free version gets better I will re-enable it and tell everyone how wonderful it is. Or please tell me how to shut it off. Thanks. :-) It's started in your session. If you're using Gnome, go to System-Preferences-Startup Applications and scroll down the list. You can uncheck the box next to PulseAudio Sound System to not have it start up, or delete it entirely. There's undoubtedly a similar thing for KDE, but since I'm not a KDE user, I don't know where it is. Someone else want to chime in? -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
Ok Steven, let me do a google search on pulseaudio home page, follow the
first link which reads www.pulseaudio.org, click on the documentation link,
scroll down to KDE and read http://www.pulseaudio.org/wiki/PerfectSetup#KDE
for you here. It says:
quote
KDE 4 uses Phonon as the main audio interface. The Xine backend of Phonon
should eventually use PulseAudio automatically, but at the time of writing the
pulse plugin for Xine is too unreliable, so it's disabled by default. While
waiting for that to get better, Phonon uses Alsa. Therefore, to get Phonon to
use PulseAudio, you have to edit your ~/.asoundrc or /etc/asound.conf.
/quote
So when your favorite KDE app tries to play some sound, it talks to Phonon,
which either uses xine backend to talk to pulseaudio directly, or uses alsa.
Now let me scroll back to the top of the page and read
http://www.pulseaudio.org/wiki/PerfectSetup#ALSAApplications for you:
quote
If the PulseAudio plugin for alsalibs is installed all applications with
support for the ALSA API should be able to access a PulseAudio server. You
need version 1.0.12 or newer of the ALSA packages for the PulseAudio plugin to
be included.
To activate the driver edit /etc/asound.conf or ~/.asoundrc and add:
pcm.pulse {
type pulse
}
ctl.pulse {
type pulse
}
Now you you can access the PulseAudio server under the virtual ALSA device
pulse:
% aplay -Dpulse foo.wav
% amixer -Dpulse
If you want to make the PulseAudio driver the default, use something like this
in the ALSA configuration files:
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
/quote
Now let me take a look at /etc/asound.conf and ~/.asoundrc instead of you, and
find that this is precisely how a default Fedora system is configured.
So how does it work? Open your favorite sound app, and ask it to play some
music. If it is a typical KDE app, it will utilize Phonon, which redirects to
ALSA, where pulseaudio plugin for alsa takes over, checks if the pulseaudio
binary is already running and transfers audio handling to it. If it is not
running, the plugin launches /etc/pulse/default.pa, which is an equivalent of
an userland init script for pulseaudio. It launches the actual binary. Look
at the first line:
#!/usr/bin/pulseaudio -nF
This is where it actually gets executed. (I hope you are familiar with the
sha-bang syntax.)
Now, once executed, pulseaudio starts receiving signals to be played from all
apps that try to use it natively, or try to use ALSA or ESD or Phonon or
whatever. All these signals get mixed and sent to ALSA sound driver which
talks to actual hardware to play the sound.
So in a nutshell, whatever your app tries to use as a sound interface, it gets
eventually rerouted to pulseaudio, which gets executed if it is not running
already. If it doesn't get rerouted to pulseaudio, something is broken
(typically the app itself), and you don't get any sound from that app by
default. File a bug against it.
Can pulseaudio be simply shut OFF?
I don't think so, at least not so easily. As you can see above, it is way too
much integrated in the system. There is no single place where it is invoked
and where it could be shut off. You need to uninstall it altogether and let
every app find it's own way to fallback to alsa.
Unfortunately, I am running KDE-4.2.4 and if there's a way to shut the
little stinker off, I'd be grateful to know how.
AFAICS, KDE is using Xine backend by now, which talks to pulseaudio natively.
I don't think that you can find an option to shut it down and use alsa. But do
take a look at systemsettings - Multimedia, maybe there you can set
preferences the way you like. Here I talk about the latest KDE 4.3, you should
probably yum update.
I have no idea what it is that pulseaudio is supposed to actually do that
I'm supposed to like about it. I used to have sound. I still have sound.
Let me read the very first sentence from http://www.pulseaudio.org/ for you:
quote
PulseAudio is a sound server for POSIX and Win32 systems. A sound server is
basically a proxy for your sound applications. It allows you to do advanced
operations on your sound data as it passes between your application and your
hardware. Things like transferring the audio to a different machine, changing
the sample format or channel count and mixing several sounds into one are
easily achieved using a sound server.
/quote
Then let me click on About pulseaudio link and read
http://www.pulseaudio.org/wiki/AboutPulseAudio#Details for you:
quote
PulseAudio is a networked sound server, similar in theory to the Enlightened
Sound Daemon (EsounD). PulseAudio is however much more advanced and has
numerous features.
A sound server can serve many functions:
* Software mixing of multiple audio streams, bypassing any restrictions
the hardware has.
* Network transparency, allowing an application to play back or record
audio on a different machine than the one it is running
Re: Where is pulseaudio started?
On Wed, 2009-08-26 at 13:39 -0400, Steven W. Orr wrote: I'm looking at my copy and the comments in the top of the file begin with a #sign but the config lines begin with a semi;colon. So right now I have no idea what's a comment and what's required syntax. For some files, they're both considered comments (others use different prefixes for comments). The dual comment technique is used in some files to differentiate between comments you read, and settings that you might want to play with. -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On 08/26/09 20:45, quoth Marko Vojinovic:
Ok Steven, let me do a google search on pulseaudio home page, follow the
first link which reads www.pulseaudio.org, click on the documentation link,
scroll down to KDE and read http://www.pulseaudio.org/wiki/PerfectSetup#KDE
for you here. It says:
quote
KDE 4 uses Phonon as the main audio interface. The Xine backend of Phonon
should eventually use PulseAudio automatically, but at the time of writing
the
pulse plugin for Xine is too unreliable, so it's disabled by default. While
waiting for that to get better, Phonon uses Alsa. Therefore, to get Phonon to
use PulseAudio, you have to edit your ~/.asoundrc or /etc/asound.conf.
/quote
So when your favorite KDE app tries to play some sound, it talks to Phonon,
which either uses xine backend to talk to pulseaudio directly, or uses alsa.
Now let me scroll back to the top of the page and read
http://www.pulseaudio.org/wiki/PerfectSetup#ALSAApplications for you:
quote
If the PulseAudio plugin for alsalibs is installed all applications with
support for the ALSA API should be able to access a PulseAudio server. You
need version 1.0.12 or newer of the ALSA packages for the PulseAudio plugin
to
be included.
To activate the driver edit /etc/asound.conf or ~/.asoundrc and add:
pcm.pulse {
type pulse
}
ctl.pulse {
type pulse
}
Now you you can access the PulseAudio server under the virtual ALSA device
pulse:
% aplay -Dpulse foo.wav
% amixer -Dpulse
If you want to make the PulseAudio driver the default, use something like
this
in the ALSA configuration files:
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
/quote
Now let me take a look at /etc/asound.conf and ~/.asoundrc instead of you,
and
find that this is precisely how a default Fedora system is configured.
So how does it work? Open your favorite sound app, and ask it to play some
music. If it is a typical KDE app, it will utilize Phonon, which redirects to
ALSA, where pulseaudio plugin for alsa takes over, checks if the pulseaudio
binary is already running and transfers audio handling to it. If it is not
running, the plugin launches /etc/pulse/default.pa, which is an equivalent of
an userland init script for pulseaudio. It launches the actual binary. Look
at the first line:
#!/usr/bin/pulseaudio -nF
This is where it actually gets executed. (I hope you are familiar with the
sha-bang syntax.)
Now, once executed, pulseaudio starts receiving signals to be played from all
apps that try to use it natively, or try to use ALSA or ESD or Phonon or
whatever. All these signals get mixed and sent to ALSA sound driver which
talks to actual hardware to play the sound.
So in a nutshell, whatever your app tries to use as a sound interface, it
gets
eventually rerouted to pulseaudio, which gets executed if it is not running
already. If it doesn't get rerouted to pulseaudio, something is broken
(typically the app itself), and you don't get any sound from that app by
default. File a bug against it.
Can pulseaudio be simply shut OFF?
I don't think so, at least not so easily. As you can see above, it is way too
much integrated in the system. There is no single place where it is invoked
and where it could be shut off. You need to uninstall it altogether and let
every app find it's own way to fallback to alsa.
Unfortunately, I am running KDE-4.2.4 and if there's a way to shut the
little stinker off, I'd be grateful to know how.
AFAICS, KDE is using Xine backend by now, which talks to pulseaudio natively.
I don't think that you can find an option to shut it down and use alsa. But
do
take a look at systemsettings - Multimedia, maybe there you can set
preferences the way you like. Here I talk about the latest KDE 4.3, you
should
probably yum update.
I have no idea what it is that pulseaudio is supposed to actually do that
I'm supposed to like about it. I used to have sound. I still have sound.
Let me read the very first sentence from http://www.pulseaudio.org/ for you:
quote
PulseAudio is a sound server for POSIX and Win32 systems. A sound server is
basically a proxy for your sound applications. It allows you to do advanced
operations on your sound data as it passes between your application and your
hardware. Things like transferring the audio to a different machine, changing
the sample format or channel count and mixing several sounds into one are
easily achieved using a sound server.
/quote
Then let me click on About pulseaudio link and read
http://www.pulseaudio.org/wiki/AboutPulseAudio#Details for you:
quote
PulseAudio is a networked sound server, similar in theory to the Enlightened
Sound Daemon (EsounD). PulseAudio is however much more advanced and has
numerous features.
A sound server can serve many functions:
* Software mixing of multiple audio streams, bypassing
Re: Where is pulseaudio started?
On Mon, 24 Aug 2009 18:07:00 -0700 stan gr...@q.com wrote: On Sun, 23 Aug 2009 11:25:09 -0400 Steve Blackwell zep...@cfl.rr.com wrote: I am not a pulse expert, but will take a stab at this as I have been wrestling with it for a while. I can't find any reference to pulseaudio in any init file Not init. You can configure it to start a systemwide server, which I suspect is started by X. Well the PID of Xorg on my system is $ ps -ef | grep Xorg root 16848 16841 0 Aug22 tty1 00:27:53 /usr/bin/Xorg :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-e1NCi1/database -nolisten tcp vt1 so if Xorg started pulseaudio then I would expect the PPID of pulseaudio to be 16848 but it's not. $ ps -ef | grep pulseaudio steve30603 1 0 Aug23 ?00:07:25 /usr/bin/pulseaudio --start --log-target=syslog The PPID is 1 which is the PID of init. $ ps -ef | grep init root 1 0 0 Aug13 ?00:00:02 /sbin/init So where does it get started? If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. No representation as to validity of the above, might contain wild supposition and unsubstantiated misinformation. If you want pulse information, go to the horses mouth http://www.pulseaudio.org/ That what got me started looking into this. There have been so many problems reported with pulseaudio, I decided I needed to look into how it worked a little closer. Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is pulseaudio started?
On Sun, 23 Aug 2009 11:25:09 -0400 Steve Blackwell zep...@cfl.rr.com wrote: I am not a pulse expert, but will take a stab at this as I have been wrestling with it for a while. I can't find any reference to pulseaudio in any init file Not init. You can configure it to start a systemwide server, which I suspect is started by X. So where does it get started? If you are using the default Fedora setup, you have your own version of pulse started when you log in. I notice that it also can be started by programs that need its services, and that seems to be gconf-helper. No representation as to validity of the above, might contain wild supposition and unsubstantiated misinformation. If you want pulse information, go to the horses mouth http://www.pulseaudio.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
