Waiting for sound system to respond

Bug #400973 reported by arky on 2009-07-18
This bug affects 42 people
Affects Status Importance Assigned to Milestone
gnome-media (Ubuntu)
Nominated for Karmic by Exozito
Nominated for Lucid by Exozito

Bug Description

Binary package hint: gnome-media

The gnome-volume-control doesn't work with LiveCD running with orca screen reader. It fails to start with 'Waiting for sound system to respond' error. Ubuntu blindness profiles doesn't use pulseaudio, that might be the source of the problem. On machines using pulseaudio it works gnome-volume-control works fine.

ProblemType: Bug
Architecture: i386
Date: Sat Jul 18 05:43:33 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-volume-control-applet
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090717)
Package: gnome-media 2.27.4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SourcePackage: gnome-media
Uname: Linux 2.6.31-3-generic i686

arky (arky) wrote :
arky (arky) wrote :
arky (arky) wrote :

Poking around found a lot of errors

Jul 18 11:14:13 ubuntu kernel: [ 62.181214] udev: starting version 145
Jul 18 11:14:13 ubuntu kernel: [ 62.265080] aufs au_xino_do_write:371:modprobe[3593]: I/O Error, write failed (4294967268)
Jul 18 11:14:13 ubuntu kernel: [ 62.268928] aufs au_xino_write:406:modprobe[3593]: I/O Error, write failed (-5)
Jul 18 11:14:13 ubuntu kernel: [ 62.270838] aufs au_set_h_iptr:94:modprobe[3593]: I/O Error, failed au_xino_write() -5
Jul 18 11:14:13 ubuntu kernel: [ 62.283883] aufs au_xino_do_write:371:modprobe[3593]: I/O Error, write failed (4294967268)
Jul 18 11:14:13 ubuntu kernel: [ 62.285971] aufs au_xino_write:406:modprobe[3593]: I/O Error, write failed (-5)

arky (arky) wrote :
arky (arky) wrote :
arky (arky) wrote :
Changed in gnome-media (Ubuntu):
status: New → Confirmed

I can confirm this bug for me, and I'm also not using PulseAudio. I'm not using any GNOME accessibility features either (I don't even have them installed). This is terrible; I can't even access my gstreamer or event sound properties just because I don't want/need PulseAudio on my system?

To 'arky': are you also having issues with high CPU usage, like in: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/400820 ?

arky (arky) wrote :

Yes dave, I have the same high CPU usage issue, I remove the applet from startup and panel so that I can continue using my karmic machine.

arky, a patch has been committed upstream for the CPU usage issue. It should find its way into Ubuntu soon. In the meantime, I have found that creating a ~/.pulse/client.conf file with this single line:
autospawn = false
will fix the CPU usage.

summary: - [karmic] Waiting for sound system to respond
+ Waiting for sound system to respond
Changed in gnome-media (Ubuntu):
importance: Undecided → Low
rotnacogeid (diego-cantor) wrote :

This bug also affects me. I think that pulse is conflicting with the previous alsa libraries that were before updating to karmic. For some reason this installation is not clean.

I found a good GUI workaround for controlling gstreamer and event sound preferences. One can still run the old gnome-sound-properties with a couple of files. The attached file has 32bit/x86 and 64bit/x86-64 versions of the gnome-sound-properties program. Move the appropriate version of this file to /usr/local/bin and move the sound-properties.glade (this file is not architecture-dependent) to /usr/local/share/gnome-control-center/glade/ (you'll probably need to create this directory).

If you need a different architecture, get the appropriate .deb at https://launchpad.net/ubuntu/+source/gnome-control-center/1:2.26.0-0ubuntu3 . DO NOT install the .deb, just right-click it and open it in the Archive Manager. The file you need is data.tar.gz/./usr/bin/gnome-sound-properties. Extract that file and follow the above instructions.

As for mixing, OSS4 users will probably want to use ossmix or ossxmix and ALSA users will probably install the alsamixergui package. I guess it would be possible to use the xfce4 mixer in GNOME too.

illume (illume) wrote :

I get this message too. Also not using pulseaudio before I upgraded, but karmic installed it for me on upgrade.

My sound buttons are now broken after I uninstalled pulse audio.

Was on an irc channel earlier talking with a bunch of people about what to do who had the same problem.

I had to restart ubuntu after I uninstalled pulseaudio, as the uninstall did not stop pulse audio.

A bunch of applications started using up all my cpu once pulse audio was stopped, and I had to restart my laptop. I guess the pulseaudio client library is buggy with regard to when pulse audio stops.

I had to uninstall pulse audio, since it used up a constant 3% cpu even when there was no sound coming out... making my battery flat, and keeping my fans running reducing the lifetime of my laptop.

illume (illume) wrote :

I found a web page describing the problem and a work around.


This is a bug with ubuntu karmic, and not gnome in general apparently.

illume, that "workaround" only works for OSS4 users. ALSA users should either use the attachment in Comment #11 or use "alsasink" and/or "alsasrc" if using gconf-editor directly.

Exozito (exozito1) wrote :

Even with the "workaround" for OSS4(Opensound), keyboard shortcuts for adjusting audio volume no longer work, and pulseaudio can't get along with OSS4.

OSS4 users can use the System -> Preferences -> keybindings app (or run "gnome-keybinding-properties" in terminal) to map volume keys to ossmix commands. First figure out what tracks are available by running 'ossmix' command with no arguments. Then experiment with the ossmix command in the terminal. Once you find what works, map it.
ossmix -- headph +2 #raise volume of headphone output
ossmix -- headph -2 #lower "
ossmix -- mute toggle #uhh, mute :)

There are also more complicated scripts: http://www.opensound.com/wiki/index.php/Tips_And_Tricks#ossvol

I've reconfigured the appropriate gnome packages to use gstreamer instead of pulseaudio: https://launchpad.net/~dtl131/+archive/ppa/

OSS/4 users will want the libcanberra packages in that PPA as well (if they want event sounds). ALSA users don't need to bother with the libcanberra in that PPA.

kronictokr (pstone78) wrote :
Download full text (5.0 KiB)

pulse AND alsa both come installed and thats the problem. they conflict, and cause a LOT of problems. try this , my personal mix. should work like a charm. you can reverse this method to keep pulse if you like . but i think this method is pretty good

almost willing to bet fix all sound issues in karmic, unless hardware completely doesnt support it, like SIS graphics

could reverse the process to keep pulse if you wanted

software conflict, this should fix it

since this is a microsoft, i mean software conflict problem, you should be able to use this method on all karmic install no matter what your hardware is. if not, i would suggest backing up your info and starting from the top. again tho, you shouldnt have to. any pakages you already have shouldnt affect the script either, or your install. restores all sound including system sounds. also stops freezing issues that happened when adjusting audio settings.


sudo apt-get remove libsdl1.2debian-alsa

includes audacious music player, vlc , and ubuntu restricted extras(minus pulse updates :D ).

sudo aptitude install libdns53 libdns53 linux-headers-2.6.31-16 linux-headers-2.6.31-16-generic linux-image-2.6.31-16-generic ureadahead alsa-oss alsa-base alsa-tools alsa-tools-gui alsa-utils alsa-oss linux-sound-base asoundconf-gtk audacious audacious-plugins audacious-plugins-extra cabextract flashplugin-installer freepats gnome-alsamixer gsfonts-x11 gstreamer0.10-ffmpeg libesd-alsa0 gnome-alsamixer gstreamer0.10-plugins-bad gstreamer0.10-plugins-bad-multiverse gstreamer0.10-plugins-ugly gstreamer0.10-plugins-ugly-multiverse ia32-libs java-common lib32asound2 lib32bz2-1.0 lib32ncurses5 lib32stdc++6 lib32v4l-0 lib32z1 liba52-0.7.4 libao2 libass3 libaudclient2 libaudcore1 libaudid3tag2 libaudio2 libaudutil1 libavcodec52 libavformat52 libavutil49 libbinio1ldbl libbio2jack0 libbio2jack0-dev libcdaudio1 libcddb2 libcelt0 libdc1394-22 libdca0 libdirac0c2a libdvbpsi5 libdvdnav4 libdvdread4 libebml0 libenca0 libfaac0 libfaad0 libffado1 libfftw3-3 libfluidsynth1 libfreebob0 libftgl2 libgconfmm-2.6-1c2 libglademm-2.4-1c2a libglew1.5 libgsm1 libid3tag0 libiptcdata0 libiso9660-5 libjack-dev libjack0 libjack0 liblash2 liblua5.1-0 libmad0 libmatroska0 libmcs1 libmimic0 libmjpegtools-1.9 libmms0 libmodplug0c2 libmowgli1 libmp3lame0 libmp4v2-0 libmpcdec3 libmpeg2-4 libofa0 libpostproc51 libprojectm-data libprojectm2 libquicktime1 libreadline5 libresid-builder0c2a libsad2 libschroedinger-1.0-0 libsdl1.2debian-all libsidplay1 libsidplay2 libsoundtouch1c2 libswscale0 libtwolame0 libvcdinfo0 libvlc2 libvlccore2 libwildmidi0 libx264-67 libxml++2.6-2 libxvidcore4 nspluginwrapper odbcinst1debian1 sun-java6-bin sun-java6-jre sun-java6-plugin ttf-dejavu ttf-dejavu-extra ttf-liberation ttf-mscorefonts-installer ubuntu-restricted-extras unixodbc unrar vlc-data vlc-nox vlc-plugin-pulse linux-backports-modules-2.6.31-16-generic linux-backports-modules-alsa-2.6.31-16-generic linux-backports-modules-alsa-karmic-generic linux-backports-modules-headers-karmic-...


C de-Avillez (hggdh2) wrote :

@all: please be carefull if you are considering following the instructions in the previous comment. These actions are not supported, and *may* result in a broken system.

@ comment #18
That looks dangerous (and unnecessary), especially deleting system files without using the package manager. I know you can remove pulseaudio without taking out too many packages, as long as you don't try and remove libpulse packages.

Ernst (ernst-blaauw) wrote :

On my laptop, the icon in the notification area shows a cross sign, looking like the sound is muted, but that's not the case: I hear sound. If I click on it and press "Sound Preferences", I get a dialog box saying "Waiting for sound system to respond".

I'm running Lucid 32-bit.

$ apt-cache policy gnome-media
  Installed: 2.28.5-0ubuntu3
  Candidate: 2.28.5-0ubuntu3
  Version table:
 *** 2.28.5-0ubuntu3 0
        500 http://nl.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

Lubosz Sarnecki (lubosz) wrote :

I also have this problem on Lucid 64bit. Sound works, but the panel does not. alsamixer seems to work too.
There also is no icon for the volume control in Indicator Applet.

$ uname -a
Linux HackProHackstation 2.6.32-16-generic #24-Ubuntu SMP Sat Mar 6 12:32:35 UTC 2010 x86_64 GNU/Linux

$ apt-cache policy gnome-media
  Installed: 2.29.91-0ubuntu1
  Candidate: 2.29.91-0ubuntu1
  Version table:
 *** 2.29.91-0ubuntu1 0
        500 http://archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

Lubosz Sarnecki (lubosz) wrote :

Maybe i should mention that i did not have this problem in Karmic from which i upgraded.

Lubosz Sarnecki (lubosz) wrote :

I get following when i run gnome-volume-control

$ gnome-volume-control
socket(): Address family not supported by protocol

Sorry for the 3 posts, but bugtrackers should support edit :/

Lubosz Sarnecki (lubosz) wrote :

This crash happened because of the old version of o3d i had in my plugins directory. libnpo3dautoplugin.so

The bug report is invalid.

Lubosz Sarnecki (lubosz) wrote :

Wrong bug report, sorry. This has nothing to do with libnpo3dautoplugin.so.

mercedes (preciousa1237) on 2010-03-13
Changed in gnome-media (Ubuntu):
status: Confirmed → In Progress
Richard (richpaulfahey) wrote :

I just deleted the .pulse directory in my home folder and that seemed to do the trick! Could then open the sound panel to reconfigure. (Also deleted Pulse directories in /tmp but not sure if that was necessary)

Alex Shulgin (alex-shulgin) wrote :

#27: did the trick for me too, thanks!

For the record: I've upgraded from karmic to lucid and switched from XFCE to GNOME at the same time and got this problem.

Boris Burtin (boris-burtin) wrote :

I just hit a related issue when moving my home directory from one system to another. After moving the data from my home directory (including ~/.pulse), the sound applet stopped responding. On startup, it would say "Waiting for sound system to respond". After deleting ~/.pulse and rebooting, the problem went away. PulseAudio should be more forgiving in this case, since it's common to copy user preferences from one account to another.

If this is a separate bug, let me know and I'll file it.

I had something very similar to the problem described by Ernst (#21) and after deleting ./pulse directory in my local folder everything is OK.

Thanks a lot, Richard!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers