Bug#556086: alsa-utils: aumix and alsactl state incompatible?
In order to definitely rule out aumix, please uninstall (and purge) it and see whether the problem persists. well, without aumix, it's the very same -- only i can't fix it, since alsamixer misses the relevant control ... thus, it _is_ pretty much an alsa issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556086: alsa-utils: aumix and alsactl state incompatible?
reassign 556086 alsa-utils thanks On Wed, Nov 18, 2009 at 22:09, arne anka deb...@ginguppin.de wrote: In order to definitely rule out aumix, please uninstall (and purge) it and see whether the problem persists. well, without aumix, it's the very same -- only i can't fix it, since alsamixer misses the relevant control ... thus, it _is_ pretty much an alsa issue. okay, reassigning back to alsa-utils - sorry for the inconvenience. -- Stefan Ott http://www.ott.net/ You are not Grey Squirrel? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556086: alsa-utils: aumix and alsactl state incompatible?
Package: alsa-utils Version: 1.0.21-1 Severity: normal after every boot, my audio is muted. looking into aumix it shows the controls Volume and Pcm 2 set to zero -- although the were set to sensible values upon shutdown. Pcm 2 only knows 0 or 100 and has to be 100 to make Volume work at all. at boot the message Saved ALSA mixer settings detected; aumix will not touch mixer. is displayed, the saved alsa state (/var/lib/alsa/asound.state) shows the timestamp of the last shutdown. alsamixer's controls do not correspondend (in an easy to grasp way) to the controls of aumix, but apparently there's nothing representig aumix' Pcm2. due to the user-hostile style of alsa's state files i am unable to understand, waht exactly the state file stores -- but apparently it does in no way help to restore sane values upon boot. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31.5 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages alsa-utils depends on: ii dialog1.1-20080819-1 Displays user-friendly dialog boxe ii libasound21.0.21a-1 shared library for ALSA applicatio ii libc6 2.10.1-7 GNU C Library: Shared libraries ii libncursesw5 5.7+20090803-2 shared libraries for terminal hand ii linux-sound-base 1.0.21+dfsg-2 base package for ALSA and OSS soun ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii module-init-tools 3.11-1 tools for managing Linux kernel mo ii udev 147-4 /dev/ and hotplug management daemo ii whiptail 0.52.10-4.1Displays user-friendly dialog boxe Versions of packages alsa-utils recommends: ii alsa-base 1.0.21+dfsg-2 ALSA driver configuration files ii pciutils 1:3.1.4-3 Linux PCI Utilities alsa-utils suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556086: [Pkg-alsa-devel] Bug#556086: alsa-utils: aumix and alsactl state incompatible?
* arne anka [091113 13:56 +0100] Package: alsa-utils Version: 1.0.21-1 Severity: normal after every boot, my audio is muted. looking into aumix it shows the controls Volume and Pcm 2 set to zero -- although the were set to sensible values upon shutdown. Pcm 2 only knows 0 or 100 and has to be 100 to make Volume work at all. at boot the message Saved ALSA mixer settings detected; aumix will not touch mixer. is displayed, the saved alsa state (/var/lib/alsa/asound.state) shows the timestamp of the last shutdown. This sounds like many similar alsa bugs. Try just to purge aumix 'dpkg --purge aumix'. Maybe we should conflict aumix against alsa-utils. Elimar -- It's a good thing we don't get all the government we pay for. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556086: [Pkg-alsa-devel] Bug#556086: alsa-utils: aumix and alsactl state incompatible?
This sounds like many similar alsa bugs. Try just to purge aumix 'dpkg --purge aumix'. Maybe we should conflict aumix against alsa-utils. not really a solution -- i definitely prefer aumix over alsamixer. what exactly causes the problem? i did not find a matching entry for alsa-utils. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556086: [Pkg-alsa-devel] Bug#556086: alsa-utils: aumix and alsactl state incompatible?
reassign 556086 aumix thanks * arne anka [091113 19:42 +0100] This sounds like many similar alsa bugs. Try just to purge aumix 'dpkg --purge aumix'. Maybe we should conflict aumix against alsa-utils. not really a solution -- i definitely prefer aumix over alsamixer. what exactly causes the problem? i did not find a matching entry for alsa-utils. Hmm, the aumix maitainer should help. Reassigned. Elimar -- Do you smell something burning or ist it me? signature.asc Description: Digital signature
Bug#556086: alsa-utils: aumix and alsactl state incompatible?
Hi This doesn't look like an aumix issue to me (if you check the aumix init script you will see that, when it says will not touch mixer it does indeed *not* touch the mixer). In order to definitely rule out aumix, please uninstall (and purge) it and see whether the problem persists. cheers -- Stefan Ott http://www.ott.net/ You are not Grey Squirrel? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
