Bug 102015 - media-sound/alsa-utils alsasound init script does not fail if needed modules are not found
|
Bug#:
102015
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: alsa-bugs@gentoo.org
|
Reported By: betelgeuse@gentoo.org
|
|
Component: Unspecified
|
|
|
URL:
|
|
Summary: media-sound/alsa-utils alsasound init script does not fail if needed modules are not found
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-08-10 10:58 0000
|
Background:
After updating a kernel I sometimes forget to rebuild modules so when I boot I
have the alsa modules missing.
Steps to reproduce:
1. /etc/init.d/alsasound stop (make sure that the modules are not loaded)
2. rm /lib/modules/<kernel>/alsa-driver/acore/snd.ko
3. /etc/init.d/alsasound start
4. /etc/init.d/alsasound status
Behaviour:
It gives a bunch of errors as expected but alsasounds status still reports
alsasound as started but it is most certain that sound is not working.
Expected:
When one of the modules is missing the init script should stop executing and
report failure with for example return 1.
Still present in alsa-utils-1.0.12
The problem is that one might be using built-in static support for ALSA, which
would break if we check modules presence.
I've fixed it in 1.0.14_rc2-r1 without revbump, as I just added it yesterday,
and this is a minor problem anyway.
