From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0000571]: Doesn't store mixer settings
Date: Wed, 13 Oct 2004 12:53:22 +0200 (CEST) [thread overview]
Message-ID: <20041013105322.C60401B00B@server.perex-int.cz> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000571
======================================================================
Reported By: pmatil
Assigned To:
======================================================================
Project: ALSA - utils
Bug ID: 571
Category: alsactl
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 10-07-2004 18:27 CEST
Last Modified: 10-13-2004 12:53 CEST
======================================================================
Summary: Doesn't store mixer settings
Description:
No errors are produced by the initscripts, however it seems that it doesn't
save mixer settings. After boot, asound.state is 'zeroed' eg. all sliders
are down, but unmuted. Running manually alsactl store, asound.state gets
all the right values, but after next boot / reboot, asound.state is
'zeroed' again. Asound.state lies in /var/lib/alsa/asound.state
======================================================================
----------------------------------------------------------------------
tiwai - 10-12-2004 14:44 CEST
----------------------------------------------------------------------
Is alsactl patched? It's usually in /etc/asound.state.
asound.state is saved when alsasound init service is stopped, too.
This means that the status of sound differs at this stage from
what you have now. Possibly, the window system (e.g. KDE) modifies
and restores the sound status by itself.
----------------------------------------------------------------------
pmatil - 10-13-2004 12:30 CEST
----------------------------------------------------------------------
It's possible. System is Debian so maybe it's patched. It doesn't matter
whether I start X (KDE) or not, sound levels aren't saved by the init
script. I don't know where alsa thinks it saved the volume levels, because
I don't know much of init scripting and it gives no error. So maybe this
is mainly a Debian problem...
----------------------------------------------------------------------
tiwai - 10-13-2004 12:53 CEST
----------------------------------------------------------------------
Check the init script you use. The alsasound script provided from the
original alsa-driver package uses /etc/asound.state, and call with -f
option.
Bug History
Date Modified Username Field Change
======================================================================
10-07-04 18:27 pmatil New Bug
10-12-04 14:44 tiwai Bugnote Added: 0002096
10-13-04 12:30 pmatil Bugnote Added: 0002120
10-13-04 12:53 tiwai Bugnote Added: 0002121
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next reply other threads:[~2004-10-13 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 10:53 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-18 17:10 [ALSA - utils 0000571]: Doesn't store mixer settings bugtrack
2004-10-18 15:42 bugtrack
2004-10-15 11:51 bugtrack
2004-10-14 14:26 bugtrack
2004-10-14 13:14 bugtrack
2004-10-14 11:25 bugtrack
2004-10-13 10:30 bugtrack
2004-10-12 12:44 bugtrack
2004-10-07 16:27 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041013105322.C60401B00B@server.perex-int.cz \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox