Bug 78784

Summary: bad post-install/pre-remove config for saving mixer settings
Product: [Retired] Red Hat Linux Reporter: Need Real Name <jmd>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED CURRENTRELEASE QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 8.0CC: mitr, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: FC3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-29 21:22:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2002-11-29 21:42:29 UTC
In what looks like an attempt to save mixer levels for the user, Red Hat puts
this in modules.conf:

alias sound-slot-0 sb
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1
|| :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :

While a valiant attempt, it should be apparent why it never works. The drivers
aren't ever removed, so pre-remove never executes. The mixer level saving should
either be added to initscripts to occur at boot, or this pre-remove line should
be removed entirely. As is, it causes unpredictable behavior. (Modified mixer
levels are never saved unless a user for some reason manually removes the
driver. As they never saw this behavior before, it would be unexpected, and,
maybe there wanted to RESTORE default mixer levels (and are going about it
wrong), this would cause DATALOSS and permanently lose them sensible mixer
levels that are loaded with the drivers)

Comment 1 Bill Nottingham 2005-09-29 21:22:34 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

This should be solved with the saving in /etc/init.d/halt, and loading on module
load, in current releases.