[Bug 15585] Muted sound after dist-upgrade from Hoary to Breezy

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Thu Sep 29 12:18:55 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=15585
Ubuntu | alsa-utils


jdthood at yahoo.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jdthood at yahoo.co.uk




------- Additional Comments From jdthood at yahoo.co.uk  2005-09-29 13:18 UTC -------
The problem is that the alsa-utils package inadequately handles changes in
the mixer interface from one kernel version to another.  On shutting down
the mixer state is stored in /var/lib/alsa/asound.state.  After booting
with the new kernel, "alsactl restore" tries to feed this asound.state to
the (new 'n' improved) driver and the driver gags because the mixer
descriptions have changed.

/etc/init.d/alsa-utils already runs alsactl with the "-F" option in an
attempt to deal with this, but apparently that is not good enough.

It would be nice if alsactl and the driver dealt with this problem in a
better way.

alsa-utils should be changed so that instead of doing a mere
"alsactl restore" it takes the following steps in the "start"
method (on boot):

     Move old asound.state to asound.state_PREV
     Run "alsactl store" to create new asound.state
     Run asound.state through a processor which sets "sane"
       default values without changing the structure of the file
     Use the values in asound.state_PREV to update the values in
       the new asound.state without changing the structure of
       the file
     Run "alsactl restore"

Mandriva already does something like this.

Any volunteers to implement this?  ;)

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kernel-bugs mailing list