Red Hat Bugzilla – Bug 527075
[abrt] crash detected in lash-0.5.4-8.fc12
Last modified: 2010-03-10 00:28:56 EST
abrt detected a crash.
How to reproduce
Process was terminated by signal 6
Created attachment 363584 [details]
Could you tell us how to reproduce the bug? Thanks.
This might be a consequence of the long standing bug 505421. I hope they
fix that soon which is not very hard to do. (if you read that bug you will see
the unresponsiveness of the maintainer which renders F-11 useless for audio
Well, the workaround is to unblacklist snd-seq* modules. Or to issue a
which can be put in your /etc/rc.local file. I believe that lash_* applications
will start fine afterwards.
Please verify the workaround.
Ok, please, check this out:
[root@introdesk modprobe.d]# grep snd-seq ./*
./dist.conf:alias sound-service-*-1 snd-seq-oss
./dist.conf:alias sound-service-*-8 snd-seq-oss
./dist-oss.conf:# install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-pcm-oss && /sbin/modprobe snd-seq-device && /sbin/modprobe snd-seq-oss
I don't have it blacklisted...
So, are snd-seq and snd-seq-oss loaded (can be checked via lsmod) but lash fails?
[renich@introdesk ~]$ lsmod | grep snd
snd_hda_codec_analog 78544 1
snd_hda_intel 32136 4
snd_hda_codec 80480 2 snd_hda_codec_analog,snd_hda_intel
snd_usb_audio 101784 0
snd_pcm 90568 4 snd_hda_intel,snd_hda_codec,snd_usb_audio
snd_timer 24544 1 snd_pcm
snd_usb_lib 19912 1 snd_usb_audio
snd_rawmidi 25888 1 snd_usb_lib
snd_seq_device 8700 1 snd_rawmidi
snd_hwdep 9864 2 snd_hda_codec,snd_usb_audio
snd 74936 17 snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_pcm,snd_timer,snd_usb_lib,snd_rawmidi,snd_seq_device,snd_hwdep
soundcore 7952 1 snd
snd_page_alloc 10464 2 snd_hda_intel,snd_pcm
So they are not loaded. Load them via
Then start your lash application.
sorry, it doesn't work.
After the modprobe, I try to run lash and it gives an error about the device already being in use.
Hmm... What device? Is there more to the error message?
huh? what device?
Well, it just gives me that message.
I have an M32N32-WS motherboard. I suppose everything is nvidia. The audio works fine... but I just can't make that modprobe you asked and start lash...
Sorry for the poor info on this
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
I think this issue is resolved by the module-init-tools folks. Could you verify if things work for you?
Confirmed, they work fine now ;)
Since this is resolved by fixing of module-init-tools, I mark this as a duplicate of the corresponding bug.
*** This bug has been marked as a duplicate of bug 505421 ***