From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SRUlr-0002Nq-KO for garchives@archives.gentoo.org; Mon, 07 May 2012 20:43:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BA4DAE0996; Mon, 7 May 2012 20:42:44 +0000 (UTC) Received: from smtpout.karoo.kcom.com (smtpout.karoo.kcom.com [212.50.160.34]) by pigeon.gentoo.org (Postfix) with ESMTP id 01EC5E0991 for ; Mon, 7 May 2012 20:41:11 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.75,545,1330905600"; d="scan'208";a="619195322" Received: from 213-152-39-89.dsl.eclipse.net.uk (HELO compaq.stroller.uk.eu.org) ([213.152.39.89]) by smtpout.karoo.kcom.com with ESMTP; 07 May 2012 21:41:11 +0100 Received: from [192.168.1.100] (unknown [192.168.1.100]) by compaq.stroller.uk.eu.org (Postfix) with ESMTP id C8832AC6C7 for ; Mon, 7 May 2012 21:40:04 +0100 (BST) From: Stroller Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: [gentoo-user] asound.state bug? Can anyone else reproduce this, please? Date: Mon, 7 May 2012 21:40:41 +0100 Message-Id: <8481383F-6734-42CA-9745-0569404908B5@stellar.eclipse.co.uk> To: gentoo-user@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) X-Archives-Salt: 5c1762df-7373-454c-9ccf-133072678bcf X-Archives-Hash: 560a32cd98b83896da4e709b773ddb4e Can anyone reproduce this, please? The following steps conclude with a reboot: 1) `aplay -vv SomeFile.wav` - listen to some banging new tunes and = satisfy yourself that your speakers and ears are working. Skip this step = if you're already satisfied that your speakers are audible and that = sound issues from them ok.=20 2) Backup current alsa state - `/etc/init.d/alsasound save && cp = /var/lib/alsa/asound.state ~/asound.state.bu` 3) Stop /etc/init.d/alsasound and remove it from the default run-level - = `/etc/init.d/alsasound stop && rc-update del alsasound default` 4) Sound is still working, right? Now open `alsamixer` and mute it; = ideal is to mute all channels thoroughly (use the left and right arrow = keys to navigate channels, the M key to mute, the escape key to exit). 5) Run `/etc/init.d/alsasound save` 6) Reboot the system. Afte the reboot, is the sound muted, please?=20 Here it is, and I don't think it should be, because I think that should = be restored by the /etc/init.d/alsasound script, which has a = RESTORE_ON_START option in its conf.d file and which was removed from = the default runlevel in step (3). We can establish that it's not running = with `/etc/init.d/alsasound status` I'm also seeing that maybe alsa's default state is muted, so that the = muted state would be correct even if the sound state is not being = restored. That's fine - restore the previous backup of sound from when = audio was playing (`cp ~/asound.state.bu /var/lib/alsa/asound.state`) = and reboot the system. Now the unmuted state is restored and you can = listen to your music without starting /etc/init.d/alsasound. I'm happy to elaborate on the little more I know about this stuff, if = there's someone who can tell me that yes, they're seeing this, too, and = yes, this is *not* the expected behaviour. Right now I'm still wondering = if I'm doing something wrong. This system is ~amd64, baselayout 2.1. Stroller.