Ubuntu 9.04 Jaunty distribution release date draws near. Pulseaudio – the future is coming up as well. I admit that it works better compare to Intrepid, however, I still want to stick to the no-frills ALSA for my Intel on board card. If Pulseaudio works for you, by all means stick to it. I merely give you another option to choose. By the way, I manage to get my mic working 🙂 This guide will help you to kind of disable pulseaudio from starting / avoid pulseaudio to hog the sound hardware. It also solves the problem of every boot, the master channel is turned all the way down and muted.
The Environments: Firstly, I upgrade my Intrepid to Jaunty RC 32bits PC through ‘update-manager -d’. I have only one laptop so I can’t test the vanilla Jaunty RC version. Though, I will try to match the configuration as best as I can. Secondly, I have a built-in mic. Thirdly, the soundcard is an onboard Intel STAC9200 and I don’t have 2nd soundcard. For the uninitiate, the $ in front just denote your shell, after that is the command.
Required Packages: alsa-oss; libasound2; libasound-plugins; sysv-rc-conf (optional)
$ sudo apt-get install alsa-oss libasound2 libasound2-plugins sysv-rc-conf
The Procedure:
Step 1:
When I upgrade to Jaunty, it doesn’t install any new ’70pulseaudio’ file in Xsession. If there is no such file, safely ignore this step. If it is present, move it to somewhere safe. The command below sends it to your home root folder.
$ sudo mv /etc/X11/Xsession.d/70pulseaudio ~/
Step 2:
Disable Pulseaudio service from run level. Watch out for the dot at the end. Else you can use sysv-rc-conf GUI.
$ sudo update-rc.d pulseaudio stop 50 2 3 4 5 .
Unset Pulseaudio from system and set my card from ‘asoundconf list’
$ asoundconf unset-pulseaudio $ asoundconf set-default-card Intel
Make sure your libao.conf is using alsa. Use gedit if you like. For the uninitiate, to save in nano, press Ctrl + x.
$ sudo nano /etc/libao.conf default_driver=alsa
Navigate from the menu: System – Preferences – Sound, make sure yours looks like the one in the screenshots below:
So far so good. Cos those steps are similar to my previous guide. Now come to the more tricky part.
Prevent Pulseaudio from daemonize. Open ‘/etc/pulse/client.conf’ with your editor again. Look for this line ‘autospawn = yes’ then change it to ‘autospawn = no’.
This folliwng step is thanks to one of my reading of Sonal Santan on the mailing list last time, but now in Jaunty then it can shine. If the just above step doesn’t work properly. Open ‘/etc/pulse/default.pa’ in an editor. Look for lines similar to the following two commented out lines:
#load-module module-alsa-sink
#load-module module-alsa-source device=hw:1,0
Add the following two lines just after these two lines:
load-module module-alsa-sink device=dmix
load-module module-alsa-source device=dsnoop
The above change will force PA not to take exclusive control of sound hardware.
This step is similar to my old guide. Open ‘/usr/share/alsa/alsa.conf’ in an editor. Comment out the line which says ‘/usr/share/alsa/pulse.conf‘ by inserting a # in the beginning. After the change, the @hooks section would look something like the following.
@hooks [ { func load files [ # "/usr/share/alsa/pulse.conf" "/usr/share/alsa/bluetooth.conf" "/etc/asound.conf" "~/.asoundrc" ] errors false } ]
The above procedure will make sure ALSA is use system-wise. 🙂
OPTIONAL (But recommended anyway): Go to this link, https://help.ubuntu.com/community/HdaIntelSoundHowto look at this section Manually Specify Module Parameters and do yourself a favour 🙂
Step 3:
Application specific issue is discuss here. Mplayer only at the moment.
MPlayer: 10 second wait before audio start playing.
—> Edit ‘/etc/mplayer/mplayer.conf‘, change the order to the order below (original pulse,alsa)
# Specify default audio driver (see -ao help for a list).
ao=alsa
Step 4:
THE MIC WORKS 🙂 ! This step might need the optional step Manually Specify Module Parameters above.
I will give you a short tutorial on `alsamixer` which is required to get the elusive mic to work. Open alsamixer by type ‘alsamixer’ in the terminal. In alsamixer, using Tab to change View property. To MUTE/UNMUTE press m. To move the slider, use up and down key. To move to another property of same view, use right and left button. And the spacebar…
Now guys, you see the box right below the slider? [ 00 ] == unmuted, [MM] == muted. Check before you keep whining that there is no damn sound.
For the Mic to work, make sure (look at the screenshot, that’s how your should looks like)
Capture and Digital properties are not muted / not zero db. 67 is a good value. Capture should look like in my screenshot . If your capture looks like, —– then press space bar once to change it to L R Captur.
Mux should be at zero.
Select your Input Source to Mic. Fire up your gnome-sound-recorder, choose Capture the voila. The capturing quality is better than M$ Windows with noise cancellation. Bleh 🙂
Step 5:
Check that you didn’t miss any step. Reboot (don’t be lazy) and make sure the damn sound is not muted =.=” .
Cheers and don’t disturb me for at least 3 weeks 🙂 Let me be at peace with my exams.
TROUBLESHOOTING
If you get the message as below
“audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Could not open audio device for playback.”
You need todo the following to resolve it. Backup .asoundrc first =)
‘sudo /etc/init.d/alsa-utils restart’
OR/AND
‘rm ~/.asoundrc’
Btw, I set up twitter @ http://twitter.com/idyllic_tux to further disseminate any tips if I have in the future.
Re: Step 4-
Hmmm, doesn’t the default (GUI) mixer in the system-tray work too?
I’m really interested to follow this guide and wipe PA, but I’m being adviced against it all the time. How’s your experience after using this guide, bumped into any oddities/annoyances etc?
You don’t wipe it at all. Uninstalling is not what we want to achieve. We merely to reduce its interference/hogging the sound device to itself. Nothing undesirable on my system yet. I used this method since Intrepid. Feel free to check the post/comments associated with it in the archive.
Furthermore, to reverse back to ur old configuration is easy, provided you back up all your configuration/files involved in the process.
I followed this guide and its working well so far, gj! you should however suggest the user to run asoundconf list
at step 2 and not just use intel. think of us who’re using nvidia mobos!
Hi xalo!
Lose the fear and do it! I’ve now removed PulseAudio from my Dell desktop running Ubuntu 9.04 and my Acer Aspire One netbook running 9.04 Netbook Remix and have encountered not a single problem.
Audacity and Skype work perfectly on the desktop. Even my “Shike” brand USB headset required no extra tweaking – I just plugged it in and it worked. Skype also works perfectly on the netbook, recognising the built-in mic.
I’ve tolerated unreliable audio in Ubuntu since Dapper – and I now realise that PulseAudio was the source of all the problems.
This is /the/ definitive guide to removing PulseAudio from your Ubuntu machine.
Once again, a hearty thank you to idyllic_tux!
I followed all the steps on two machines and when i get to the alsamixer part I get:
alsamixer: function snd_ctl_open failed for default: No such device
Now what?
1) Make sure you are in group plugdev.
2) Make sure you set-default-card
3) Try Google the error
hey, thank’s for this guide; it helped me last time with 8.10 and also now with 9.04 the new one works great. Skype is running perfect after following your guidance; and yes, for this issue you need a microphone input, so you can speak with the called 😉
hi there,
thank you very much for this guide. i just struggled through and now everything seems to be fine.
unbelievable, that it is so complicated to get rid of pulse audio. i really like ubuntu, but that is a no-go!
hausen
This post is freaking great!!!
Clear an to the point.
My mixer does not look exactly like yours, but I worked it out.
My main concern was to deactivate pulseaudio.
Thanks,
Miguel.
Thanks for the great guide, you saved my ass the second time!
😉
Very very helpful. Works wonders. Thanks 🙂
Thanks for the guide, sorted out the issues I had been having!
I finally found what I have been looking for. This worked great on xubuntu 9.04 and I thank you for the time that you put into this. The developers didn’t do a very good job on Pulseaudio with this release. I listen to a lot of internet radio, so thanks again for the article.
Bill
Thank you very much. Great guide. It was very uncomfortable switching between external and onboard sound with Pulseaudio. After disabling it is very easy with “asounfconf-gtk”. Hopefully Pulseaudio will be better integrated within the next releases. 😉
Thank you again. Now I have sound in all applications blasting from my external soundcard. The Ubuntu-people really need to clear out all this problems, ALSA should be default in every way possible with the option for Pulseaudio. I experience sound related issues after every upgrade! 😦
This is the third time i struggle with sound in Ubuntu and I was almost about to install Windows again, but your guide saved me the pain.
I can’t thank you enough. If I ever meet you, I will buy you a beer. 🙂
[…] And finally, to get the MythTV frontend to run without complaints (it has an aversion to pulseaudio at the moment) I had to disable pulseaudio completely. […]
Hi
Thanx a lot for the tutorial… I only miss a step for surround 5.1 setup… I can’t still configure it.
Hugo
Thanks a MILLION. The fix is a bit daunting but well written, easy to follow and if I couldn’t screw it up no-one else will. Now running on ALSA and no problems. I agree with Psycho Squid – ubuntu should REALLY use ALSA as the default until pulseaudio can work nicely with java and flash.
Thanks! Really helpful to get rid of the pulseaudio vaporware
[…] 1) disabilitato PulseAudio in favore del buon vecchio ALSA (https://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-keeping-the-beast-pulseaudio-at-bay/) […]
Thank you so much for this! I can finally use my speakers again.
Thank you so much. I had the issue where my master volume was muted and at 0% after every boot. This was the only solution I found that fixed it. I tried everything before this.
Yup to most of the above. This is exactly what I needed. Why on EARTH can’t pulseaudio Just Work(TM) with (for example) an alsa emulation front end? Or does it and I’m just missing something?
Thank you for your guide. I only hope I remember this for the next time I upgrade Ubuntu. I’m really disappointed in pulseaudio’s performance on my machine.
Regards,
The Viking
This guide worked almost perfectly for me. I have one problem though, when a notification or message sound is played through pidgin, pidgin crashes even though the sound method is set to alsa. If I mute all sounds, there is no crash. Any suggestions? I’m running 32-bit Jaunty with pulse disabled per this guide.
Thanks, Guy
Hmph, in Pidgin preferences, go to Sound tab. Sound Method -> Automatic. That’s my settings. I have no problem with Pidgin n OSD though =/
I solved the problem by setting preferences>sound>method in Pidgin to command. In the command field, I entered aplay %s. Thanks much for the guide, and good luck with exams.
good job. thanx a lot!
Thanks a lot! Best Pulse-killing tutorial out there!
Thanks a bunch, killing PulseAudio was the key to getting S/PDIF working! It was the same last time on my older computer, but I naively thought a newer Ubuntu would work better out of the box.
Thanks for the guide. Audacity is working fine now! Could someone explain to me what the point of Pulseaudio is?
PulseAudio is supposed to be a sound server and audio device manager. I guess the only real benefit of something like it would be for running remote X desktop sessions on thin clients (with sound).
So why do these desktop environments keep forcing sound servers on us average desktop users who just want stable / responsive sound? – Many probably don’t even know what a remote X session is – (it’s cool though, trust me; ssh -Y).
It would seem logical to make ALSA the default (maybe that’s why ALSA is in the kernel and not PulseAudio!) and let the people who are setting up some exotic network enable PulseAudio along with any of their other configuration changes. It must be a quick & dirty way for them to get massive bug reports from the masses!
I don’t get what is up with the GNU/Linux community at large. What happened to the “Custom Installation” option THAT EVEN MICROSOFT GAVE US?! It seems as though many distributions are so eager to make an install program (al la Microsoft) that you just click OK three times and your in, that they don’t even realize that all of us “power users” are stuck digging through unconventional text files and clicking random check-boxes (gnome is a big pile of crap) trying to make a basic feature just work. At least post an official tutorial similar to this one on Ubuntu’s site.
I consider myself somewhat of a GNU/Linux guru; I have been using it since the 90’s and I have built a GNU/Linux system from raw source code several times. But this really takes the cake – and novice users are subject to this treatment! Come-on!
Sorry about the rant, but seriously.
Checkout Wikipedia’s articles on “PulseAudio” and “sound server” for more precise answer to your question.
Thanks for the reply!
thanks for the tutorial. i use a acer aspire 8930, ubuntu 9.04. i installed the missing packages, fallowed the instructions, but have to skip over the step, where you change the “libao.conf”-file, because i do not have this file on my system. is it very important?
It is located at ‘/etc/libao.conf’ . This file sets the system-wide preference for audio output. You can try to skip this part. If it doesn’t work then try to create the file manually.
Great guide – its fixed *all* of the stuttering issues I had with Jaunty – had tried all of the options with pulseaudio before – none of which worked although all of them had varying degrees of improvement for the stuttering problem.
This guide hit the nail on the head – thank you idyllictux!
You have just saved me from re-installing the box to nail down issues related to an upgrade from intrepid to jaunty.
Having digested all of the information that is out there on the issue, any ideas on when the pulseaudio / kernel latency issue is expected to be fixed?
Thanks, this worked for me. I was having stuttering issues and also multiplexing issues, I couldn’t even play multiple sounds at once without it distorting terribly. These simple steps fixed everything.
I had suspected pulseaudio was giving me grief for some time. I had tried various other methods of disabling it but on 9.04 it seemed like it just wouldn’t die.
And then I tried this and you would not *believe* the number of issues it fixed. All of my broken aps from SIP clients to emulators just magically started working. The implementation of Pulseaudio in Ubuntu is so bad it isn’t even funny and the only reason I can see for it being included is so Canonical can capitalise on all the inevitable customer service calls.
Howdy mate…got afflicted to linux the day I dared to install it on my laptop as part of the experimentation process which tempts any newbie…but now am grateful for the shift to Open Source…Well Ubuntu has been my favourite & your guide helped a lot in solving a cracking sound prob I faced esp. when Pidgin notifies me…I agree Pulse Audio is not meant for those who have a single soundcard/laptop users who have the option of only a single card mostly Intel…so hats off for this crisp & precise tutorial…Regards….
I followed your guide and in fact the volume is no longer muted after Gnome is loaded. Yet the “login sound” has disappeared. Do you have any clue?
Mattia
$ gnome-sound-properties
Then switch to ‘Sounds’ tab. Make sure the sound theme is Ubuntu or whatever you fancy of.
Prior to following this tutorial, the only issue I had was with the mic settings and having intermittent issues with skype (most likely due to settings having issue with reboot). I never had issues with flash going into looped stuttering.
Now after follow the tutorial precisely, it fixes my skype issues, but after a while, flash audio is now in a constant stutter. Does anyone know how to fix this?
The beast is still not exorcised!
chema@chema-laptop:~$ alsamixer
ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect: Connection refused
alsamixer: function snd_ctl_open failed for default: Connection refused
And audacity shows correct input level but no output device options, and sound recorder tells me to run system/sound preferences (which doesn’t exist on my jaunty), and …..
hmph, did you follow step by step? alsamixer only come in after the you disabled of pulseaudio (using the above steps of course).
Try ‘$ pgrep pulseaudio’ to see where the pulseaudio is still running?
Pulseaudio was already off – that’s what the error is saying
I fixed it: I had to rm ~/.asoundrc and follow the instructions in the errors to build a new one to point at NVidia. All working now.
Had alot of problems after deactivating pulseaudio in 9.04 (x86) – alot of freezes in sauerbraten, but also in gnome-desktop itself…
@everybody, Martin, etc
Well I for one, love Pulseaudio.
Have you ever tried to relay one computer’s sound to another computer? Like having a jukebox, a computer with all that MP3/OGG files played by mpd and set it to use Pulseaudio as its output to send that sound to another computer(s)? This is not the same combination like Icecast + Ices/shoutcast for its low latency. With the right configuration you can even held audio conference over LAN with this one.
Anyway.. IIRC in order disable Pulseaudio one can remove it from startup sequence (use update-rc.d), and edit your .asoundrc (or /etc/asound.conf to make it system-wide, but you have to make it yourself if there is none) and make sure these lines are not one of them:
“””
pcm.pulse { type pulse }
ctl.pulse { type pulse }
pcm.!pulse { type pulse } # these two lines will force ALSA to
ctl.!pulse { type pulse } # use PulseAudio as default output
“””
Yes. But we, end-user, will probably never sending sound from one computer to another. So we will be just contented with ALSA. Just my 2 cents.
This is ace!
Thanks a bunch! Finally my sound is working 🙂
And Skype, and Audacity..
Thanks! This worked well and got rid of the pulse beast!
Thank You!
Finally got my mic to work!!!
Read millions os posts before this one. None worked ’cause all were trying to work around pulse. Turning off pulse solve the problem.
[…] Ubuntu 9.04 Jaunty – Keeping the beast Pulseaudio at bay « Tux’s idyllic life. load-module module-alsa-sink device=dmix load-module module-alsa-source device=dsnoop (tags: pulseaudio ubuntu howto tutorial) Comments (0) […]
No luck for me. I finally got the sound to work in Firefox by following these instructions, but I lost the mic, which was working with pulse after some tinkering.
In Sound Preferences all options give me the “could not open audio device for playback” when I try “test” for capture, and Gnome recorder just hangs. For my playback options, I also had to select my soundcard, the option “Intel ICH6 with ALC650F Intel ICH6 (ALSA)”.
One thing I didn’t do is the optional step to “Manually specify module parameters”, because the page linked appears to be for a different kind of sound card I have, and the instructions didn’t work (the Codec finding command seems bogus).
Any idea?
Hi idyllictux,
I followed your instructions and it had terrible consequences. My soundcard became completely out-of order, however until now I had at least sound but the mic didn’t work. After the modification there is no sound and no mic as well, it is not possible to unmute the master.
I tried to make everything back to pulseaudio, and now it shows that the master is unmuted, ut in real there is no any sound and any mic as well.
If you cannot help, could you please help me how to go back to pulseaudio correctly?
Thanks a lot in advance
Lobo
Hi Lobo,
I am sorry to hear that my guide didn’t work out for you. I hope you didn’t follow my guide blindly cos of different hardware. Like in step 2 ($ asoundconf set-default-card Intel ), if you got no on board Intel card, it surely does cause severe consequences. You can try this step suggested by homunq @ https://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-keeping-the-beast-pulseaudio-at-bay/#comment-182 ->` rm ~/.asoundrc `. Do back up the file as well as find out your real sound card.
I don’t know how you tried to revert back to pulseaudio, which might taint my way of reversion.
$ sudo update-rc.d pulseaudio start 50 2 3 4 5 .
$ asoundconf set-pulseaudio
If libao was original on your system and you heeded my advice to back up just replace it back. If it was not on your original system, just delete it. If no back up, then…
$ sudo nano /etc/libao.conf
default_driver=pulse
Navigate from the menu: System – Preferences – Sound, change everything to Pulseaudio
Open ‘/etc/pulse/client.conf’ with your editor again. Look for this line ‘autospawn = no’ then change it to ‘autospawn = yes’. Again if you has backup, just replace the original file.
Open ‘/etc/pulse/default.pa’ in an editor. Remove the 2 lines below, and once again if you has backup, just replace the original file.
load-module module-alsa-sink device=dmix
load-module module-alsa-source device=dsnoop
Open your ‘/usr/share/alsa/alsa.conf’. UnComment out the line which says ‘/usr/share/alsa/pulse.conf‘ by removing the # in the beginning. After the change, the @hooks section would look something like the following. If you got the back up, you won’t have to go through this.
@hooks [
{
func load
files [
“/usr/share/alsa/pulse.conf”
“/usr/share/alsa/bluetooth.conf”
“/etc/asound.conf”
“~/.asoundrc”
]
errors false
}
]
Reboot and you are done.
Ah! Did /etc/init.d/alsa-utils restart and it works. Strange that I had to do this after rebooting..
Your instructions on disabling pulseaudio and enabling alsa for Janty worked well for me on three machines 2 with Intel base audio hardware and one with Nvidia audio hardware. Thank you very much!
Hi Idyllictux,
First of all thank you very much for your kind help anyway. It is not your fault that I have a stupid hardware. My notebook is an acer aspire 5720Z with the following config:
Intel Pentium dual-core processor T2390 (2x 1,86GHz, 533 MHz FSB, 1 MB L2 cache) 1280×800,
Mobil Intel Graphic Media Accelerator X3100 (358 Mb) – Holographic 3D,
3GB DDR2/667MHz (bővíthető) memoria,
15,4” WXGA Acer CrystalBrite LCD (8ms/220-nit)
250GB 5400RPM SATA merevlemez,
8x DVD -RW -Super Multi DL,
802.11b/g WLAN,
Crystal Eye Webcamera (2Mp)
56K modem, 5in1 Card reader, Digital Audio S/PDIF, ExpressCard slot, FireWire I-link, Gigabit LAN, Infra port, S-Video, USB 2.0 (4db), VGA monitor, Webcamera(beépített), Wireless 802.11b/g, Dolby Digital Live, Empowering Technology, 4000 mAh (Lithium-ion)
It has an intel card, so normally it should work with your setup.
Your help to switch back the system are very useful because I couldn’t change back completely without this.
Thanks again and I hope your successfully passed your exams.
Rgds.
Lobo
Thanks dude, you’re a life-saver. Much appreciated.
Hi,
thanks for publishing this. It was the last piece which finally solved my problem with Virtual Box 1.66 and Rhapsody I am running on it … before that playing music crashed pulse after 4-5 songs, no way to get rid of this.
I’ve studied a lot of webpages and noticed the frustration from a lot of people w/ pulse. I do not understand why Ubuntu Jaunty ( and older ) are offering no clean default ‘uninstall’ for pulse.
All the hassle .. to make a point ? Why ? This behavior seems really M$ -ish and does not help end users.
Thanks !
[…] […]
Regard
I say thank personalbisnis.com from that post in your blog to my information.
Good luck
Hi,
it took me some time to figure out the “asoundconf” name of my soundcard in step 2 (asoundconf set-default-card ).
“asoundconf list” did the job (i tried the name as shown in alsamixer but that one differs).
A hint on that would be useful!
Great tutorial – thanks!
Thanks a lot, worked for me on my 64 bits Ubuntu 9.04 desktop.
Willem
Hi, great guide! My games were crashing in wine because of pulseaudio and your solution has helped me stop pulse from ruining my games!
Unfortunately I’ve stumbled accross a problem. My games (wine) work fine, so does rhythmbox, but nothing else. No sound from totem for example.
When i go to gnome sound settings and click ‘test’ I get:
audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Could not open audio device for playback.
😦
If you look through the comments list, 1-2 got the same problem as yours. Their suggested solution as follow. Please back up any file that you are going to delete per instruction below
sudo /etc/init.d/alsa-utils restart
OR/AND
rm ~/.asoundrc
wow it worked! your a legend, thanks!
Why pulse audio was forced down our throats despite all the issues it causes is beyond me.
I also had the same problem. In my case I had to rm /etc/asound.conf to fully get rid of pulse crap
Thank you so much! I was about to lose it with the damn sound issues.
Thanks heaps for this how to – worked a treat for me. I love Ubuntu but….. sound really should not be so hard to get and keep configured through version releases.
hi,
i really hope some can help me on this… so far i have followed the instructions here, but i can’t make changes to the client.conf file… i says that i don’t have the permission:
——————–
Could not save the file /etc/pulse/client.conf.
You do not have the permissions necessary to save the file. Please check that you typed the location correctly and try again.
———————-
what am i doing wrong?
is there anyway to get the permissions?
–
Erik
You need to edit the file as root.
sudo nano /etc/pulse/client.conf
(use Ctrl + X to save)
or
gksudo gedit /etc/pulse/client.conf
[…] […]
hello,
i have an HDA sis966 onboard audio.
after doing the above steps i got:
alsamixer: function snd_ctl_open failed for default: No such device
Using mozilla, my sound works but i cannot get to launch alsamixer and skype won’t detect my audio.
😦
what to do?
thanks in advance
got the solution…
first do
$ asoundconf list | less
the above command should show the detected audio card
then do below:
$ asoundconf set-default-card
replace ” with the displayed value in the first command.
Hello,
Thanks a lot for this posting! I was getting sick with ubuntu since release 8.04, because it prevented me from normal usage of mpd server with the ncmpc client software. I found several bug reports since that release but up to now still no fix to the default mpd.conf. See https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/364475 Finally I’m able to get proper mixing working while using multiple apps which need sound, and I should now be able to use mpd server without a fully loaded X server. Great work!
Thank you very much!. Your post help me to recover the sound in my latitude D520.
In fact it was working correctly, but after to install Skype 2.0 (deb package) all the sound went to the hell. If I play a music file, then you could not play a video after, even sounds through the browser. I try to get a good configuration setting a different combination in sound preference, but no way, finaly I uninstall the skype and return the sound setting, but the damage was made. I want to know what happened.
Muchas Gracias.
I hope that your exams have gone well.
Wow! Thanks ever so much; I’m really grateful you took the effort to write such an accessible guide for idiots like me. My audio hasn’t been working since I upgraded to Ubuntu 9.04 and I promised myself after almost a day of fumbling around I’d go back to Ubuntu 8 if I didn’t manage to get the audio to work by midnight – it’s 23:37 now. (And thanks Slarti for the extra info on how to find the name of the audiocard.)
Next challange: get the mic to work 🙂
Mic works!!!
[…] can never be resolved. The medibuntu package simply doesn’t work for me. I even go as far to uninstall pulseaudio. Unfortunately, even that doesn’t make my skype work. Mic worked for the first […]
Man, you ROCK! THX!
Just another thanks for this clear and detailed solution to the Pulseaudio nightmares. Worked great for me using Linux Mint x64 (Gloria).
Thanks for this post. I though I was becoming crazy after upgrading to Jaunty and could not get Skype to work properly….
However, I still have a minor issue: the volume control on my Dell laptop does not control the master level (although I have selected this option in the volume control preferences in ubuntu).
Fixed 😉 Was just a wrong setting in System/Perf/sound.
.
All seems to be perfect now !
Thanks again
Thanks, this seems to have helped my sound situation out a ton!
Thanks for this good guide!
I can confirm you that it work even on Kubuntu 9.04 and now Flash, Skype (with HW0,default,default as audio settings),Amarok and Wine can live all together playing all the sounds I want! 🙂
Thanks again! 😉
Thanks for the guide!
But after all, I didn’t need it lol. I was getting crazy because it didn’t work, reversed everything and digging into the Volume Control I realized the LFE is muted by default (why may I ask?)
I really dont understand the kernel and/or driver developers, theres a lot of discussion about this, I just dont get it, I’ve found articles from 2007 saying they were going to fix it!
Anyways, thanks for the guide!
Just wanted to add my thanks to the list. I wasted hours with pulse and would have wasted many more without your easy to follow guide. Works for HP Pavilion Tx1000
I’m having a problem with opening ‘/etc/pulse/client.conf’ and saving changes to the ‘autospawn = no’ part. When i open it in the text editor and try to save it, it says i don’t have permission to do that. I’m not very good at these terminal command stuff, but hoping to figure it out. My mic doesn’t work on pulse and i’m dying to change this, but i’m not very good at the code stuff. Please let me know how to get permission to save this ‘client.conf’ text file.
Nevermind, i didn’t check the comment before posting that question. But now i still have the same problem i was trying to solve even after making these changes: i can’t use my mic (the mic is not the computer mic, but a mic plugged into the “mic” slot on my computer) to record in Audacity using Jack. The mic problem is still there even after making these changes. If anyone has an idea about how can i solve this problem, that would be really helpful for suggestions. Thanks.
Run ‘alsamixer’ again, go to ‘Capture’ tab. Select ‘Input Source’, change to ‘Front Mic’ or ‘Line’ (by pressing arrow up or down). Then test again through trial and error. Other than that, I am not sure how to handle this mic problem.
Thanks for this. It’s solved all my sound problems.
I was a little bit hesistant to disable pulseaudio as it technically worka fine (I just need to unmute my master device at each startup, otherwise I don’t have any audio issues) as PulseAudio seems to have been chosen as the next generation sound system for linux and reverting to an older system all the time just delays the switch from one to another.
But this guide was quick and simple and resolved my problem, so a big thanks to the author!
I’m not on an Intel-equipped machine however (running XBMC ontop of an Ubuntu 9.04 on a Zotac ION-ITX-B board), so I had to slightly modify line:
$ asoundconf set-default-card Intel
I ran the command:
$ asoundconf list
Here is a list of available soundcards, mine read:
chk@ION-HTPC:~$ asoundconf list
Names of available sound cards:
NVidia
From there it is easy to modify the line to:
$ asoundconf set-default-card NVidia
Worked like a dream! Now my HTPC has one less kink, thanks a lot for a comprehensive and easy-too-follow guide to resolve this annoying problem!
Thanks for your guide, so far so good…
I have tried before to leave pulseaudio as it is because almost every apps (wine, xine, skype) already work, only the muted master volume at login and embedded midi in web page that still bothers me. (Killing pulseaudio with killall pulse audio solve the embedded midi page partially (I said partially, because if I ran other application concurrently with midi like exult or xu4 then the later will have no sound)
But last pulseaudio update from synaptic leaves totem xine with no sound.
That’s it ! I have enough…. I follow your guide and only encounter one problem :
– embedded midi in webpage now have no sound although I have killall pulseaudio. (I use mozplugger and timidity for playing midi in web page)
After checking what process is called (ps -ef | grep midi) and consult timidity manual, I manage to edit /etc/mozpluggerrc to use -Os (output to alsa) instead -Od (output to default audio device) in the timidity command line.
Now midi work ok in webpage and I even can run other program concurrently that use midi also (exult and xu4)
Thankyou to one and all, this has been a lifesaver!
[…] This guide will help you to kind of disable pulseaudio from starting / avoid pulseaudio to hog the sound hardware. It also solves the problem of every boot, the master channel is turned all the way down and muted. This entry was posted on Wednesday, September 2nd, 2009 at 3:08 pm and is filed under Linux, Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. […]
Just another “Thank you very much!!!” . Works flawlessly and now my Logitech USB Sounddevice works again.
I also vote to make it optional, as it take much resources and it’s imho a special interest thing. Hope they are not going to overload the os like other companys have done.
once again, thanks for sharing
bw
jesterday
[…] […]
Your guide worked flawlessly and resolved my annoying pulseaudio problem. Thanks!
Idyllictux, thanks for the guide! Being a user who doesn’t know practically anything about sound management, I carefully followed the steps – and it worked! Now, I did have my sound with pulseaudio, but it wasted a lot of CPU and in some applications like Amiga emulator, caused everything to go slow and in Skype the output constantly stuttered and crackled and I just couldn’t set my microphone properly — despite the mic-boost turned on, it was just way to silent. Now everything works fine, even the Sound Recorder in Applications->Sound&Video.
I only omitted the part where I should have edited libao.conf in /etc/ — I don’t have that .conf file there and (at least on my computer) it works without creating it.
I tried several distros during past two weeks after switching from Kubuntu 8.04 and this whole pulseaudio thing is a great annoyance — every distro has it and (for me) it nowhere works properly. Strangely, on Ubuntu 9.04 it worked least buggy, but buggy nevertheless… it’s such a relief to have it removed so elegantly. Thanks again!
I am very happy to report that the majority of this guide even works in Karmic as of alpha 5. Only thing that does not work is the asoundconf steps, but I don’t think asoundconf is installed in Karmic. Just kind of curious, how do you specify default card if you don’t have asoundconf? For the most part though, I have pulse at bay in Karmic, and am very pleased.
Hey, great to hear from you again, some more it is a good news from you. It works in Karmic alpha! That’s awesome. I just checked the file list for alsa-utils package. asoundconf was remove as of Alpha 5. Perhaps, there will be another convenient macro tool or interface for us. Else I guess we have to resort to manual editing the conf file again =/ Let’s wait 🙂
Great guide! I noticed after follow it that the Flash player plugin has stopped to take the 100% of CPU power (in one of the cores of course).So, I think the reason why the Flash plugin uses too much CPU resources is pulseaudio, and the sound decoding on it.
This looks like something I should try. So far, my solution has been a real kludge.
I have a TerraTec iVinyl, a USB sound capture unit. True enough, the makers don’t promise Linux compatibility, but on the theory that it works on both Windows and Mac without special drivers, it ought to work on Linux as well.
No matter how I set things up in System Preferences, Audacity fails with this device. But if I take Audacity for Windows and run it on Wine on the same Ubuntu system… Yes. It works. (At least it’s still open source all the way…)
welll…..it works…. really really works… now 17 computer to go….what a tiring job…fun though….
Thanks a million, Maximilian! Ehm.. I mean Tux =)
[…] von ubuntu wiederherstellen. Es scheint, als ob das mit pulseaudio zu tun hat und das killen oder Deinstallieren des pulseaudio-Daemon soll abhelfen, ich probiers heute aus. Ach ja, pulseaudio will scheinbar auch […]
[…] Some helpful links: http://ubuntuforums.org/showthread.php?t=789578 https://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-keeping-the-beast-pulseaudio-at-bay/ […]
Hi idyllictux !
many thanks for the guide.
I have already removed the evil from Ubuntu 9.10 Beta
sudo killall pulseaudio
cp /etc/X11/Xsession.d/70pulseaudio ~/
sudo apt-get purge pulseaudio
sudo reboot
How to fix some problems in Ubuntu 9.10 Beta
sudo apt-get install aumix-gtk
sudo apt-get install asoundconf-gtk
Download
alsa-utils_1.0.18-1ubuntu11_i386.deb
here:
http://packages.ubuntu.com/jaunty/alsa-utils
Extract asoundconf from alsa-utils*.deb with Archive Manager
Then install it to the proper place:
sudo cp asoundconf /usr/bin/
Type on Terminal:
asoundconf-gtk
it works now!
Thanks for this HowTo, it worked halfway for me!
After following instructions in detail, I now can enjoy clear sound with Firefox plugins (flash stuff) and also media players that allow choosing alsa directly.
My Problem: Rhythmbox sound is skipping
Unfortunately I experience the error (stated om top):
“audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Could not open audio device for playback.”
Removing .asoundrc doesnt change anything, alsamixer also produces errors (namely that it cant connect to pulse)
(Pulse is killed purged and not running)
I think homunq (5th of June, above) experienced the same problem but could fix it by rebuild .asoundrc directing it to his nvidia card, need help there!
My card is a VIA8235,
Thanks in advance!
try ‘ sudo alsa force-reload ‘ =)
I tried, the output was:
**
lsof: WARNING: can’t stat() fuse.gvfs-fuse-daemon file system /home/home/.gvfs
Output information may be incomplete.
**
when trying to open alsamixer still:
**
ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect: Connection refused
alsamixer: function snd_ctl_open failed for default: Connection refused
**
though the unloading and loading of Alsa modules seemed to be successful, I still experiencing crackling noise during Rhythmbox playback
Thanks for your help!
Maybe try ‘sudo /etc/init.d/alsa-utils restart’ .
Rebuild .asoundrc.conf is a good idea.
$ asoundconf unset-pulseaudio
$ asoundconf set-default-card
Check the pulse.conf in /usr/share/alsa/alsa.conf hook is commented out.
I tried the instruction on an ATI HDMI card recently and it works fine.
Unfortunately, asoundconf has been removed from Karmic Koala: http://mailman.alsa-project.org/pipermail/alsa-devel/2009-May/017241.html
Looking forward to your instructions for removing PulseAudio from Karmic Koala!
In case you missed it (for some reason my first attempt is several posts above this one):
As a stop-gap measure, you can reinstall asoundconf from the Jaunty repositories. Download this file:
http://lug.mtu.edu/ubuntu/pool/main/a/alsa-utils/alsa-utils_1.0.18-1ubuntu11_i386.deb
Use the Archive Manager to extract asoundconf, and stick it in /usr/bin/
Once you’ve done that, everything will work fine.
Thanks Steve, I saw your message. (I’m subscribed to this blog post.)
I ought to have been a bit clearer – sound has continued to work after the upgrade from 9.04 to 9.10. What broke was my Dell laptop front panel volume buttons, which have worked almost perfectly since 7.04. Gnome volume control also broke after the upgrade (“Waiting for Sound System to Respond”).
On an unrelated topic, plenty of other apps and services now spontaneously crash (I get the crash alert dialog twice or three times a session.)
I’m wearily coming around to the idea that I’ll have to do a clean reinstall to get 9.10 working properly again on the laptop. I’m really annoyed about that, because my neophilia caused me to break a beautifully stable 9.04 system. Grrrr. I’m not letting 9.10 anywhere near my netbook or my desktop. Sorry, for the noise, I just had to vent my frustrations!
`Gnome volume control also broke after the upgrade (“Waiting for Sound System to Respond”).`
This is because in 9.10, upstream integration is tight, so the gnome-volume-control is heavily dependent on pulseaudio. It will wait for pulseaudio to spawn before it can be initialized.
Hi idyllictux!
You can easily recompile:
1. “gnome-applets”, using the configure option –enable-mixer-applet
2. “gnome-media” with these options: –disable-pulseaudio –enable-gstmix
The guide is here:
http://linuxinnovations.blogspot.com/2009/08/recompile-debian-packages-with.html
A. Install the recompiled packages, “gnome-applets” and “gnome-media”.
B. Right click on the panel and add Volume Control.
And you get your Gnome Volume Control, the same as that of Ubuntu 9.04.
You can also recompile “gnome-settings-daemon” with the configure option –disable-pulse
After installation of the recompiled “gnome-settings-daemon” you can
remove this hidden folder: ~/.pulse
and this hidden file: ~/.pulse-cookie
There is an easy workaround to get the buttons working again:
Copy the script vom this post:
http://forum.ubuntuusers.de/post/2238686/
Save it somewhere, e.g. “~/volume.sh” and make it executable.
Create some keyboard shortcuts for the volume keys. Use the commands “~/volume.sh up”, “down” and “mute”. If it does not work, check if “libnotify-bin” is installed.
Hi Frank and idyllictux!
It is very simple indeed. No problem at all.
Step 1: Eradicate the evil.
Remove it completely. Otherwise, you may have problems after a security update, or else.
Step 2: Fix asoundconf-gtk
and set the right things.
Step 3: Fix Gnome sound settings.
You need this for Rhythmbox and some other apps.
Type on Terminal:
gconf-editor
This will produce a GUI for you to fix the problem.
You have to set the right things here:
/desktop/gnome/sound
/system/gstreamer/0.10/audio/default
Or you can simply edit such files with gedit:
~/.gconf/system/gstreamer/0.10/default/%gconf.xml
~/.gconf/desktop/gnome/sound/%gconf.xml
Another option is to borrow “gnome-sound-properties” from Ubuntu 9.04 (in a similar way as it was made with “asoundconf”).
Hope you can do this without a detailed instruction.
To make life easier, you can install “esound”.
Good luck!
P.S. Soundcard VT8233 works well with OSS4. Frank’s soundcard, VIA8235, may work too. There is OSS4 driver:
165 oss_via823x pci1106,3059 VIA VT8233/8235/8237
OSS4 seems to be an ideal solution for ancient computers (I have one of 2001 here, with VT8233). Fantastic sound quality. Skype, Adobe Flash, everything is perfect.
https://help.ubuntu.com/community/OpenSound
To fix sound in Totem, you may need to remove “gstreamer0.10-pulseaudio”
sudo apt-get remove gstreamer0.10-pulseaudio
To fix gstreamer settings, you may need this:
sudo apt-get install gstreamer0.10-plugins-bad
Type on Terminal:
gstreamer-properties
this will produce a GUI, see:
http://martinbaselier.wordpress.com/
Hi,
I used your post here a long time back to remove pulse and it was great. Did not have any problems with it at all.
Unfortunately, I was messing around with my settings in Ubuntu and I completely screwed up my sound set-up. Now, I can’t load my sound drivers.
I wrote up a comprehensive outline of my problem here:
http://ubuntuforums.org/showthread.php?t=1300743
Like I say in that post I doubt its the settings you provide that caused my problem. However, they may be the reason I am unable to revert to the original settings.
Any help would be appreciated.
Thanks!
Hmph, you followed 4 guides that make it difficult to rollback to original state.
How about doing an upgrade of alsa?
http://ubuntuforums.org/showthread.php?t=1046137
Or wait a few days then install Karmic Koala?
Hi Abhiroop!
It looks like you have a driver problem.
This might be the meaning of this message:
$ aplay -l
aplay: device_list:217: no soundcards found…
Try to upgrade ALSA, as idyllictux advised.
Karmic Koala is unpredictable about drivers.
Some M-Audio soundcards do not work with ALSA on Ubuntu 9.10, but they work with OSS4.
These soundcards:
M-Audio ICE 1712 chipset – M Audio Delta 66
M-Audio ICE 1724 chipset
These cards have open source Linux drivers (from the producer).
http://en.wikipedia.org/wiki/M-Audio
http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg1748441.html
Hi,
first of all, thank you for this great guide, it really helped. But today I upgraded to Karmic and now I don’t have any sound at all. In the gnome sound settings, there is no sound-card to configure. Is anyone here who has similar issues? I will also try to fix it and post it here, if I found a solution.
But meanwhile, I’m glad for any hint, which could help me.
Thanks a lot!
You can try to follow Demagog’s comment above. Previously, there were several comments on 9.10 Alpha and Beta.
I am only able to install 9.10 next weekend, and Kubuntu instead of Ubuntu. I’ll see how I can help.
Yes, while alsa works on Karmic Koala, gnome-volume-control-and the sound control panel only work with PulseAudio.
Any workarounds? I’m running alsamixer from the command line to control my volume, quite inconvenient!
Hmph, I am using Kubuntu (Karmic) and it uses ALSA by default. No pulsesaudio installed with my KDE.
Maybe you want to store the state first. Try the below command.
sudo alsactl store
EDIT: hold on, the control panel as far as i know is for pulseaudio only. =/
>.< I know this is a bit dumb. But it is an alternative nonetheless, `Kmix`, but it does introduce KDE stuff 😦
Anyway, I tried (fresh-installed) Karmic on my friend laptop. Pulseaudio was working fine, no cracking or noise. I was impressed with pulseaudio nonetheless.
Here is what I did to remove pulse audio in Karmic:
sudo apt-get purge pulseaudio gstreamer0.10-pulseaudio
sudo apt-get autoremove
sudo apt-get install alsa-base alsa-tools alsa-tools-gui alsa-utils alsa-oss linux-sound-base alsamixergui
sudo apt-get install esound esound-clients esound-common libesd-alsa0 gnome-alsamixer
Notes:
-run gstreamer-properties in terminal to set defaults to alsa
-remove gstreamer0.10-pulseaudio to get sound in totem
-gnome-alsamixer is for changing the volume, not an applet but better that nothing
Enjoy!
awesome
@Ben
As a stop-gap measure, you can reinstall asoundconf from the Jaunty repositories. Download this file:
http://lug.mtu.edu/ubuntu/pool/main/a/alsa-utils/alsa-utils_1.0.18-1ubuntu11_i386.deb
Use the Archive Manager to extract asoundconf, and stick it in /usr/bin/
Once you’ve done that, everything will work fine.
Warning.
Asoundconf, which is a script in alsa-utils, is not included with Karmic Koala. There is a move to change that, but right now you have to download the script from the Jaunty repository and install it to /usr/local/bin
Annoying.
Everything is already working on Ubuntu 9.10 (without pilseaudio), except for “pop-up notifications”
http://linuxinnovations.blogspot.com/2009/08/recompile-debian-packages-with.html
Step (N + 2): Borrow “gnome-sound-properties” from Ubuntu 9.04
Download Debian package “gnome-control-center” from Ubuntu 9.04 Repositories
http://packages.ubuntu.com/jaunty/gnome-control-center
Open this Debian package with Archive Manager and extract this file: “gnome-sound-properties”
Step (N + 3): Borrow “sound-properties.glade” from Ubuntu 9.04
Download Debian package “capplets-data” from Ubuntu 9.04 Repositories
http://packages.ubuntu.com/jaunty/capplets-data
Open this Debian package with Archive Manager and extract this file: “sound-properties.glade”
Step (N + 4): Install “gnome-sound-properties” into Ubuntu 9.10
sudo cp gnome-sound-properties /usr/bin/
sudo mkdir /usr/share/gnome-control-center/glade/
sudo cp sound-properties.glade /usr/share/gnome-control-center/glade/
Type on Terminal:
gnome-sound-properties
My thanks to idyllictux for disabling Pulseaudio and to Demagog providing some nifty old tools for use in Ubuntu 9.10 and clearing up my intermittent sound buffering problem.
[…] hatte in 9.04 aus verschiedenen Gründen (nicht zuletzt wegen des störungsfreien Klangs) über diese Anleitung den Pulseaudio Audio Daemon deinstalliert und musste nach dem Upgrade feststellen, dass der […]
Does anyone else have the problem that totem (or gstreamer) does not use alsa? Even if switched to it by gstreamer-properties? The test in gstreamer-properties does work but totem does not even display any volume slider!
I am ashamed… short after my recent reply I uninstalled the package “gstreamer-pulseaudio” and now totem recognises and uses alsa for playing audio…
If anyone misses the volume applet and does use AWN he can use the applet from this.
I just ran the Ubuntu 9.10 upgrade from a nicely working 9.04 install and now my sound does not work at all. Prior to the upgrade I was able to get my USB speakers to work by following the above steps. When I try “asoundconf list” from term I get command unknown – urrrrghghgghhg!!
Also I am unable to open System -> Preferences -> Sound… When I try, I get a message saying “Waiting for Sound System to Respond” and nothing happens.
Has anyone ran into this yet? Does anyone know how to correct the problem?
To get sound working again after the 9.10 upgrade I reinstalled asoundconf:
download this http://lug.mtu.edu/ubuntu/pool/main/a/alsa-utils/alsa-utils_1.0.18-1ubuntu11_i386.deb
extract asoundconf into /usr/bin using archive manager.
$ asoundconf set-default-card snd_usb_audio
Sound was fine after doing this.
People keep saying that asoundconf should be put in:
/usr/bin
That is wrong. Everytime alsa-utils is upgraded, it will wipe out your asoundconf.
Put it in /usr/local/bin instead.
It works the same, and alsa-utils won’t get confused.
Hi idyllictux!
Do you know about this method?
Re: Pulse audio by Daniel Chen on 2009-10-08T12:42:41+00:00
http://www.pubbs.net/ubuntu/200910/12748/
QUOTE:
It has not always been easy to disable PulseAudio, but it certainly remains
straightforward for a savvy user:
touch ~/.pulse-a11y-nostart
echo autospawn = no|tee -a ~/.pulse/client.conf
killall pulseaudio
It was tested here:
How to kill pulseaudio to play pSX in 9.10?
http://ubuntuforums.org/showthread.php?t=1306356
Whatever you do, don’t disable anything to do with sound in System / Preferences / Startup Applications.
I tried that.
It screwed up all my sound, including alsa after I killed pulseaudio.
I have also filed a bug. It shouldn’t do that.
This has been fixed. My above comment is now invalid.
Hi all, well, I took the karmic plunge on my desktop, and my sound is not working at all. For starters, my .asoundrc.asoundconf remained in tact throughout the upgrade, and I do not have X’s by pulseaudio in sys-rc-conf. I have turned off autospawn in my client.conf, and my gnome-alsamixer shows everything all the way up. Can someone please help? Any help would be greatly appreciated. Thanks in advance.
You’re my Hero 🙂
it’s been months I struggle with that Pulse shit , a total nightmare, hundreds of stupid crashes & crackling sound.
…
and now it runs smoothly, I can open half a dozen flash windows + any mp3 player + spotify and it doesn’t even blink 😉
also Nvidia mixer here on my Asus card so I went for
asoundconf set-default-card NVidia
instead of Intel
no other change from the guide, and it’s perfect !
Hello Demagog
Thanks for the great info!
I was trying to recompile gnome-applets according to the guide but I’m getting the following error:
checking for MIXER… no
configure: error: Mixer applet explicitly requested but a compatible gstreamer version was not found
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Any hints would be appreciated!
Hi,
Install the package “libgstreamer-plugins-base0.10-dev”.
Worked in my case!
Cheers
Acer Aspire One AOD250-1165
This model is fairly new. So it has the usual features, i.e. built in wi-fi, camera, 160 GB drive, etc, etc. This is the 3 hr battery model. I have no idea where Amazon gets their tech specs. We just bought this and the manual states that it comes with 1 GB of RAM, and is upgradeable to 2 GB. It recognized 4 wireless connections in my area the instant it was powered on. So far it’s great for what it was bought for, the internet, small low demand games, music, simple word processing…
Thank you guys, this works great both for jaunty and karmic!
Bye ^^
Thanks!
I followed these directions exactly with Ubuntu 9.10. The result was the loss of all audio functionality, both in and out, requiring a complete re-installation of Ubuntu to recover. Beware.
PA is a beast, indeed! Following the steps outlined here got my audio going again… Thanks a bunch!
Hallo…..
Mine is a bit different problem, yesterday i was trying to copy some data from an external hard disk (via USB) and it kept autoplaying and disconnecting randomly.
after that incident the audio in UBUNTU 9.04 Jaunty stopped completely. The media players seem to be playing everything but the output audio is off.
The audio is fine in the other dual boot of Windows though.
The codecs or sound package i use is ALSA mixer and kept pulse audio at bay as er your post above.
Kindly Help Urgently
Best Regards.
can someone please help me i lost all sound in firefox after i did this and i cant find a fix its very frustrating
In the latest version of Lucid, you can actually disable pulseaudio in the “startup applications” menu. Just uncheck the pulseaudio box and it doesn’t start on bootup.
Edit /etc/pulse/client.conf to change:
# autospawn = yes
to
autospawn = no
and you’ll never have a problem with accidental start-ups, either.
Thanks for the tip !
Thanks for the tip.
I’m about to re-enable pulseaudio before upgrading from 9.04 to 8.10 in preparation for upgrading to 10.04… wish me luck! I’ll report back after the upgrade.
Erk, that was supposed to be “9.04 to 9.10”
Has anyone tried any of this with UbuntuStudio 10.4?
Is the PA ALSA compatibility problem resolved in 10.4 by chance?
Any related UbuntuStudio 10.4 PA & ALSA tips or experiences out there to share?
Thanks!
Steve M
tekrytor
[…] where slax prolly uses alsa. you can't removed pulse audio, but you can force ubuntu to use alsa. https://idyllictux.wordpress.com/2009…eaudio-at-bay/ i will try this guide in 10.04 before i nuke it, i will let you know if this works. […]
Thanks!
Its been years since they implimented PulseAudio and it still doesn’t work correctly.
Have finally gone back to ALSA via your blog posting and everything (so far) appears to be fine :DDD.
All the absolute best!
I am running Lucid and sound is great without PA. I have not had any success however trying to capture sound (other than mike). Is there a method to use to capture sound coming thorugh the system via ALSA? Thanks again.
[…] Ubuntu 9.04 Jaunty – Keeping the beast Pulseaudio at bay April 2009165 comments 3 […]
[…] You hear sound Failure: You do not hear sound. Use this guide: https://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-keeping-the-beast-pulseaudio-at-bay/, then […]
Thanks in support of sharing such a pleasant opinion,
article is pleasant, thats why i have read it entirely
Unset Pulseaudio from system and set my card from ‘asoundconf list’ … sekomplett.wordpress.com
[…] If you really want to remove pulseaudio, you can try this (I haven't tested using 12.04): idyllictux.wordpress.com/2009/04/21/… […]
I do not even know the way I finished up here, but I believed this publish was once good.
I don’t know who you are but certainly you’re going to a well-known blogger in the event
you aren’t already. Cheers!