Mixer values are not getting stored across reboot cycles
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mythbuntu |
Fix Released
|
High
|
Unassigned | ||
alsa-utils (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: alsa-utils
I've been seeing reports of people who are testing recent Mythbuntu 9.10 daily images and setting IEC958, rebooting the machine and finding the setting not set anymore.
I experience this myself too, when I try to set mixer volumes and find that the settings are not persisting to the next boot. This provides a detrimental (and confusing) experience when you just finish setting your mixer settings to work with your home theatre perfectly and they aren't sticking.
ProblemType: Bug
Architecture: i386
Date: Sat Oct 17 17:04:25 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Alpha i386 (20091017)
Package: alsa-utils 1.0.20-2ubuntu5
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: alsa-utils
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(polkit-
(xfce4-
Changed in mythbuntu: | |
milestone: | none → karmic-rc |
status: | Confirmed → Fix Committed |
An alsa-utils package has been uploaded to the karmic queue which replaces the init script with an upstart job, citing this bug.
It also reverts the changes to the init script from the last two uploads - which should be sufficient to fix the problem with mixer state not being saved.
So I'm rejecting the upload out of the queue. Now is not the time to be converting additional services from sysvinit to upstart - particularly when that isn't needed in order to fix a bug, as is the case here.