← Back to team overview

kernel-packages team mailing list archive

[Bug 95940] Re: No way to reset ALSA state from GUI


** Tags added: hardy

** Tags added: jaunty

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  No way to reset ALSA state from GUI

Status in gnome-applets:
  Won't Fix
Status in KDE Multimedia:
Status in gnome-applets package in Ubuntu:
Status in linux package in Ubuntu:
Status in linux-source-2.6.20 package in Ubuntu:
  Won't Fix
Status in gnome-applets source package in Hardy:
  Won't Fix
Status in linux source package in Hardy:
Status in linux-source-2.6.20 source package in Hardy:
  Won't Fix

Bug description:
  There is no way to reset the ALSA state from the mixer applet.

  Several users have found that they lose sound, and that the problem
  turns out to be an asound.state file which does not work for their
  hardware. It has not been established how the file came to be corrupt
  or whether the problem was caused by upgrades to newer versions which
  did not handle the file as written by the previous version. It has not
  been established what aspect of the asound.state files caused the
  problem. But several approaches can fix the problem:

    1. Removing the ALSA modules, deleting the asound.state file, and
  reloading the modules. This is difficult to do for non-expert users,
  because applications such as the Gnome mixer and volume control can be
  using the modules, preventing their unloading.

    2. Removing the ALSA modules, and editing the asound.state to an
  ultra-minimal state that reflects only the primary card, and reloading
  the modules.

   3. Invoking the alsa-utils "reset" option. On Ubuntu, typing this
  fixes the problem for Intel sound cards:

       /etc/init.d/alsa-utils reset Intel

  The latter option is thought to be best, because it doesn't require
  unloading and reloading modules.

  It would be very useful to be able to invoke that "reset" command from
  the GUI Gnome mixer applet, which is why this bug has been filed on

To manage notifications about this bug go to: