http://qa.mandrakesoft.com/show_bug.cgi?id=3005
Product: drakconf
Component: drakconf
Summary: mcc lies about services in mdk-9.1rc2
Version: 9.1-6mdk
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
This bug was reported earlier in bug 2283. However, it was resolved as "fixed" even
though the
bug remains exactly as it was.
Firstly, the only ALSA rpms installed on my system are:
libalsa-data-0.9.0-0.14rc7mdk
libalsa2-0.9.0-0.14rc7mdk
Here's how to reproduce the bug:
1. As before, start mcc for the 1st time after a reboot. Mcc shows the status of the
alsa
service as "stopped" even though the ALSA sound drivers are all loaded (lsmod shows
them
loaded) and sound is already working.
2. Click on the start button for alsa service. Mcc shuts down and then starts the
service and
shows it as "running". All it does is execute /etc/rc.d/init.d/alsa to unload and then
reload the
ALSA kernel modules.
The question is: if it is "running" now, why does mcc show it as "stopped" at the
beginning ?
Also, what does it mean to say "alsa service running" when the script
/etc/rc.d/init.d/alsa is
clearly not running in the manner in which /sbin/devfsd, /usr/sbin/atd run as a
daemons ?
Note that I do _not_ have alsa-utils installed so there is no way /usr/bin/aconnect
and
/usr/sbin/alsactl can be run by the script in /etc/rc.d/init.d/alsa .
More stupid behavior:
3. Quit mcc.
4. Manually, using modprobe/rmmod, unload all sound modules.
5. Start mcc again and it still shows the alsa service as "running". At the same time
lsmod
shows no sound modules. So why this misinformation ?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
