Red Hat Bugzilla – Bug 53896
mixer settings are reset arbitrarily without notice, nor mention
Last modified: 2007-04-18 12:37:16 EDT
Description of Problem:
Trying to record wav files from an external source, using grecord. mixer
settings are set by aumix. occasionally (read every so often) the mixer
settings are reverted back to some default setting without permission, nor
For example... I record a file now, and my settings are correct. I close
aumix, and go about my business... later I decide to record a new .wav
file and after recording, I learn that the rec level has been reset to 0.
Both root and my users .aumixrc shows the correct rec level (between 95 and
100), however, as stated, on occasion, the settigns are returned to some
Version-Release number of selected component (if applicable):
aumix 2.7-2 on a stock full 7.1 install with all current errata installed.
Not sure. this is another of those bugs that just happen. There are no
log messages generated, nothing to stdout or stderr.
Steps to Reproduce:
Normally, it happens this way.
1. set settings in aumix and set record to something high.
2. record something using grecord
3. close aumix after hitting s for save.
4. wait a while (maybe 30 minutes to an hour) and record something else.
5. opem aumix again and check levels...
when this happens, I find that the record and several other settings have
been mysteriously reset to some other setting that is apparently cached
somewhere, but I cant find it. THis occurs no matter which user is doing
the setting or recording, AND happens when I copy a .aumixrc file to both
root and local user directories, so that they are both using the same
aumixrc file to base mixer settings on.
settings do not change after settign and saving them,
Not sure how reproducible, however, Steve Taylor in support is experiencing
the same things on his box at home. his email is email@example.com if you
want to contact him.
What is grecord? I don't seem to have it. Where is it from?
It is possible that multiple applications are competing for the mixer
I don't observe this behaviour with my hardware. Unable to reproduce.
Probably best to contact the upstream maintainer/developer directly if
Whoops, wrong resolution.