After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 537515 - mixer_applet2 process uses 100% cpu if an USB external sound device is unplugged.
mixer_applet2 process uses 100% cpu if an USB external sound device is unplug...
Status: RESOLVED DUPLICATE of bug 519388
Product: gnome-applets
Classification: Other
Component: mixer
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-10 04:52 UTC by Toño
Modified: 2008-10-27 16:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Toño 2008-06-10 04:52:07 UTC
+++ This bug was initially created as a clone of Bug #519388 +++

When removing an external USB audio device (Creative SB 24 external in my case but usb headsets might suffer same behavior), the mixer applet starts eating one core cpu time (as I think it is single threaded). It does not necessarily have to be a secondary card, in my system the built in card is bios-disabled so only usb sound is available.

Steps to reproduce:
1. Connect a sound device via USB, might be a secondary.
2. Load a mixer applet and configure it to manage the usb device via ALSA.
5. (not sure if this is needed) Make the external card the default card in ALSA.
6. Unplug the usb sound device.
7. Almost immediately the process 'mixer_applet2' starts eating the CPU time.


Actual results:
You can see the process 'mixer_applet2' using 100% of one core cpu time on top, atop etc.
After replugging the card, open the preferences window and select OSS then ALSA again to revert the applet to its normal non cpu hungry state.

Expected results:
Awareness of hotplug sound devices (might be achieved via d-bus).
When unplugging a device turn the speaker icon to the n/a icon.

Does this happen every time?
Yes
Comment 1 Toño 2008-06-10 04:59:24 UTC
IMPORTANT!!!!!!!

The bug from which this one was cloned, was reported when using the USB device as a secondary sound device, however the bug happens even when it is working as the primary sound device or when it is the only one.
Comment 2 Toño 2008-06-10 05:21:34 UTC
The comment #8 of bug 167606 seems to go along the same lines of this bug.

----> http://bugzilla.gnome.org/show_bug.cgi?id=167606#c8
Comment 3 Gido Bruno 2008-06-10 12:48:00 UTC
This also happens to me with a Plantronics usb headset.
Comment 4 Teppo Turtiainen 2008-10-27 16:39:19 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 519388 ***