Alsa Mixer does not store its state correctly

Bug #272865 reported by Sergei (Nolar) Vasilyev
4
Affects Status Importance Assigned to Milestone
alsa-utils (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: alsa-utils

Alsamixer behaves strangely, together with gnome-sound-properties, at least with recording from 'digital' input source. While system is running, it is enough to set them up (roll to the highest value and unmute) - and the gnome-sound-recorder records the sound normally.

But if I store achieved state with "sudo alsactl store 0", and then reboot, it looses all its states. Actually, it sets somehow unpredictable values (both recording levels and mute-flags). Looks just like if it writes and reads different ways.

Ubuntu 8.10.a5 (Intrepid Ibex), up-to-date.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: nvidia
Package: alsa-utils 1.0.17-0ubuntu1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-utils
Uname: Linux 2.6.27-3-generic i686

Tags: apport-bug
Revision history for this message
Sergei (Nolar) Vasilyev (nolar) wrote :
Revision history for this message
Daniel T Chen (crimsun) wrote :

fixed in jaunty

Changed in alsa-utils:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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