[Bug 285962] [patch] mixer(8) should honour SOUND_MIXER_READ_DEVMASK result for output
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 285962] [patch] mixer(8) should honour SOUND_MIXER_READ_DEVMASK result for output"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 285962] [patch] mixer(8) should honour SOUND_MIXER_READ_DEVMASK result for output"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 08 Apr 2025 16:50:56 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285962
Bug ID: 285962
Summary: [patch] mixer(8) should honour
SOUND_MIXER_READ_DEVMASK result for output
Product: Base System
Version: 14.3-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: bugs@FreeBSD.org
Reporter: mail@fbsd2.e4m.org
Created attachment 259393
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=259393&action=edit
patch for diff
I have several machines spitting out something like
mixer: speaker.volume=0.00:0.00: Device not configured
on the console during boot. The reason is:
On shutdown, /etc/rc.d/mixer writes the state of all mixers to /var/db using
"mixer -f ${dev} -o". On reboot, /etc/rc.d/mixer tries to restore the last
state using "mixer -f ${dev} `cat ${file}`".
"mixer -f ${dev}" (with or w/o -o) walks through all devices, not taking
into account if the corresponding device actually exists. The result is that
non-existing devices (and their values) are being saved (in this case
"speaker.volume") and these can't be restored.
This patch fixes this by skipping devices which do not exist.
--
You are receiving this mail because:
You are the assignee for the bug.