Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I don't know how to reproduce this problem, because I don't regularly play music or sound. All I know is that, sometimes, I'll load a video (from youtube or from a local file) and there will be no sound.

Everything looks fine software wise:

  • Rebooting always fixes.
  • aplay, paplay and pals give no error message
  • I'm not in the audio group, as advised
  • The device exists and appears in use:

    $ lsof /dev/snd/by-path/pci-0000\:00\:1b.0
    pulseaudi 17313 badp   23u   CHR 116,10      0t0 7628 /dev/snd/by-path/../controlC0
    pulseaudi 17313 badp   30u   CHR 116,10      0t0 7628 /dev/snd/by-path/../controlC0
  • Restarting pulseaudio or alsa seems to do no good.

What is wrong here?

share|improve this question
If you are using gnome, you can get to sound preferences from the audio icon. This will show you what applications are trying to do things. Sometimes I've had browsers produce many entries - possibly many tabs with sound events. That caused temporary sound issues for me. – belacqua Jan 23 '11 at 17:33
@jgbelacqua No, that tab is usually empty. – badp Jan 23 '11 at 17:47
Can you tell us what version/architecture Ubuntu you're using ? (e.g., on straight Ubuntu 10.10, 64-bit, I fortunately haven't seen this issue....). Also, have you modified any packages that could have possibly touched sound drivers or changed default pulseaudio behavior? Finally, what kind of uptime and what kind of apps do you have running when this happens (or what apps have you had running prior to the failure you notice)? Thanks. – belacqua Jan 23 '11 at 21:16
@jgbelacqua: Ubuntu 10.10 32 bit with PPAs/software sources for/from Chromium, Google, GetDeb, Dropbox, Gnome Shell, Unity, Skype, Firefox, Ground Control, Transmission, GMail, Miro, Medibuntu, Gwibber, Nouveau, Opera, George's SE notification thingadongdong, Mumble, X, MeTv, Banshee, Aubergine, Ubuntu Tweak, Wine, ... a large list, but nothing sound related that I use. (I don't have software installed from them all). Uptime can be a few hours. Usually, it's just a browser and/or VLC and/or Flash. – badp Jan 23 '11 at 21:40

An interesting tool I hadn't seen from :

ubuntu-bug audio

It attempts to do some interactive checks. If you haven 't, try running that when the issue occurs. But the checks are worth running any time. I believe the bug information generated will provide the information that the next links ask for. (For example, giving the equivalent of the from fedora. EDIT: Actually, you can find here.)

That page has some other good info as well. I think most of the fixes are for constant problems, though, not intermittent ones like you are having.

Two Fedora-Linux wikis have some troubleshooting tips that could be extracted:

From the fedora pages:

The output of pulseaudio -vvvvv, run on the command line, is often helpful. To provide this correctly, first configure PulseAudio not to respawn itself automatically when it dies, by creating a file ~/.pulse/client.conf with this content:

autospawn = no

Then kill the existing server, with the command pulseaudio -k. Now launch pulseaudio -vvvvv from a console, and reproduce your problem. Provide the whole set of messages from the console where you ran pulseaudio.

The output of pacmd ls can also provide a snapshot of the audio system's state.

Application-wise, here's a post (from 2009) mentioning that Skype caused problems for him:

[...] I ran into some problems with skype (bug filed). PulseAudio asserts and goes away probably because of something Skype does wrong (although one could argue that PulseAudio shouldn’t break down completely because of one bad client).

Of course, there are lot of possible culprits, but knowing that one of your apps has in the past caused problems is at least encouraging (or discouraging, if you want).

Long shot -- check your CPU time for the pulseaudio process -- noticed this from the manpage:


Do not install CPU load limiter on platforms that support it. By default, PulseAudio will terminate itself when it notices that it takes up too much CPU time. This is useful as a protection against system lockups when real-time scheduling is used [....]

share|improve this answer
I tried ubuntu-bug audio, no luck. The rest will get some attention later. – badp Jan 24 '11 at 7:29

Rebooting helping and restarting alsa and pulseaudio may indicate your sound drivers.

Try to reload sound driver if it is not working.

(If you do not know what is your driver paste here output of lsmod, and name of your sound card)

share|improve this answer
How do you reload the sound driver? Thanks. – belacqua Jan 23 '11 at 21:17
give me name of your driver... but rmmod to unload, and insmod to load kernel module. – przemo_li Jan 24 '11 at 14:22
Except you can't unload a module in use... – badp Feb 19 '11 at 21:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.