indicator-sound takes over one CPU core if it can't access pulseaudio

[Michael]

Binary package hint: indicator-sound

Originally reported on bug 365187 and reported here as a separate issue on Ka-Hing Cheung's request.

When Indicator Applet fails to access pulseaudio it pushes system CPU usage to use up all spare capacity of one core (most of this is accounted for by top as "system" time). Seen on Lucid and Maverick. To reproduce, change $HOME/.pulse* to be owned by root and kill pulseaudio. To make the problem go away again, rm -r $HOME/.pulse*.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: indicator-sound 0.4.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Wed Sep 22 10:07:04 2010
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.utf8
SourcePackage: indicator-sound
XsessionErrors:
 (bluetooth-applet:1668): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (polkit-gnome-authentication-agent-1:1676): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1672): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed