Ubuntu
indicator-sound package

114 instances of indicator-sound-service running

Bug #1394193 reported by tp
108
This bug affects 23 people
Affects Status Importance Assigned to Milestone
indicator-sound (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have at the moment 114 instances of indicator-sound-service running.
I can get rid of them by running "sudo killall indicator-sound-service".
After which, in about two seconds, 114 new indicator-sound-service processes are started.

$ ps aux | grep indicator-sound-service | grep lightdm | wc -l
114

$ ps aux | grep indicator-sound-service | grep lightdm | wc -l
lightdm 32320 0.0 0.0 54320 612 ? Ds 15:17 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32321 0.0 0.0 54320 612 ? Ds 15:17 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32322 0.0 0.0 54320 616 ? Ds 15:17 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32323 0.0 0.0 54320 616 ? Ds 15:17 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32324 0.0 0.0 54320 612 ? Ds 15:17 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32325 0.0 0.0 54320 612 ? Ds 15:17 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32326 0.0 0.0 54320 616 ? Ds 15:17 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
etc...

I'm not an expert, but I don't think I need 114 instances of indicator-sound-service.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ActionStates: ({'mute': (true, signature '', [<false>]), 'phone-settings': (true, '', []), 'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume': (true, '', [<0.14678955078125>]), 'scroll': (true, 'i', []), 'play-playlist.gmusicbrowser.desktop': (true, 's', []), 'gmusicbrowser.desktop': (true, '', [<{'running': <false>, 'state': <'Paused'>}>]), 'desktop-settings': (true, '', []), 'volume': (true, 'i', [<0.8486785888671875>]), 'root': (true, '', [<{'title': <'Sound'>, 'accessible-desc': <'Volume (84%)'>, 'icon': <('themed', <['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': <true>}>]), 'previous.gmusicbrowser.desktop': (true, '', []), 'play.gmusicbrowser.desktop': (true, '', [<'Paused'>])},)
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 19 15:20:57 2014
InstallationDate: Installed on 2013-05-20 (548 days ago)
InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to trusty on 2014-04-29 (204 days ago)
upstart.indicator-sound.log:
 (process:2208): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

 ** (process:32533): CRITICAL **: volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' failed

 ** (process:32533): CRITICAL **: file /build/buildd/indicator-sound-12.10.2+14.04.20140401/obj-x86_64-linux-gnu/src/volume-control.c: line 1775: uncaught error: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface (g-dbus-error-quark, 16)

See original description
Revision history for this message
tp (torben-putkonen) wrote :
description: updated
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-sound (Ubuntu):
status: New → Confirmed
Revision history for this message
Dun Peal (dunpealer) wrote :

I have 125 instances, together eating about 12% CPU.

Revision history for this message
Christian Uceda (christianuceda) wrote :

I have the same proble, I have found 29 instances of indicator-sound-service running on my box.

I run Xubuntu 14.04.1.

Revision history for this message
Janne Snabb (snabb) wrote :
Download full text (28.6 KiB)

Same issue herre on Xubuntu 14.04.1 x86_64.

I have 103 instances of the process. The processes are owned by "lightdm" user except for one which is owned by my userid "snabb" (see the process list at the end).

There are also 103 instances of process "init --user --startup-event indicator-services-start" owned by "lightdm" as well, except one is owned by myself again (see the second process list at the end).

When executing "sudo killall indicator-sound-service" all of the instances were restated.

At the time there was lots of syslog output by pulseaudio. See the end of message for tail output.

$ sudo ps axuwww | fgrep indicator-sound-service | fgrep -v fgrep
lightdm 3440 0.0 0.0 399020 5024 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3441 0.0 0.0 472752 5048 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3442 0.0 0.0 399040 5036 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3453 0.0 0.0 399020 5024 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3462 0.0 0.0 399012 5156 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3463 0.0 0.0 399020 5020 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3467 0.0 0.0 399012 5152 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3474 0.0 0.0 399012 5156 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3483 0.0 0.0 399012 5156 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3498 0.0 0.0 399020 5164 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3506 0.0 0.0 407208 5132 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3507 0.0 0.0 399020 5168 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3512 0.0 0.0 399012 5160 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3513 0.0 0.0 407208 5168 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3514 0.0 0.0 399020 4976 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3555 0.0 0.0 399012 5160 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3560 0.0 0.0 399012 5152 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3561 0.0 0.0 399020 4972 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3605 0.0 0.0 399020 4976 ? Ssl 17:57 0:00 /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 3638 0.0 0.0 399020 5164...

Revision history for this message
Janne Snabb (snabb) wrote :

One more thing:

I was able to get rid of the processes by executing the following command:

$ sudo kill `ps axuwww | fgrep indicator-services-start | awk '{ print $2 }'`

However, as a result I lost the sound control thingy from the panel. I should have probably excluded the indicator process which was owned by myself.

The following command might be better (not tested, for future reference):

$ sudo pkill -u lightdm -f indicator-services-start

Revision history for this message
Eugene Shkel (eshkel) wrote :

Also I see same amount of process 'init --user --startup-event indicator-services-start'

~$ ps -aux | grep "init --user --startup-event indicator-services-star[t]" | wc -l
81
~$ ps -aux | grep "indicator-sound/indicator-sound-servic[e]" | wc -l
81

Revision history for this message
Sergej Kozin (sergejkozin) wrote :

I am using Ubuntu 14.04.3, XFCE 4.12, LightDM.

New instances of "indicator-sound-service", "indicator-bluetooth-service", "indicator-services-start" appears after Lock / Unlock screen.

Revision history for this message
Christian Uceda (christianuceda) wrote :

On bug

https://bugs.launchpad.net/lightdm/+bug/1322275/comments/10

I posted a workaround that can be useful (comment 10)

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.