Red Hat Bugzilla – Bug 189602
Receiving segmentation fault when running kudzu
Last modified: 2014-03-16 22:59:26 EDT
Description of problem:
I am getting a segmentation fault when kudzu tries to start up. It fails to
start. This I think causes a problem when hardware detection takes place. The
system simply halts when trying to configure my onboard AC'97 sound card.
I performed an interactive logon and skipped these and then tried to detect the
sound card, but no go.
I have attached the stack trace and the output from the /home/root/scsound.log
Version-Release numbekudzu-188.8.131.52-1r of selected component (if applicable):
Every time I boot, or try and run kudzu.
Steps to Reproduce:
1.Boot machine or run kuzdu from shell.
[root@localhost ~]# kudzu
Created attachment 128090 [details]
Stacktrace of kuzdu
Created attachment 128398 [details]
output strace kudzu
Having similar problem, freezes my machine on boot, and interactively.(Notebook
Acer Aspire 5020, ATI Radeon mobility x700). Bugzilla lists other apparently
related/duplicated bugs of the same persuasion.
Ehi guys this bug ***IS*** high priority:
o) makes previously OK systems unbootable
o) getting out of it is a pain in the ass (boot rescue, disable kudzu, find out
if it can run in SAFE mode - it usually can)
o) it generally make upgrading miserable
This bug is about a crash - freezing the machine is another issue entirely.
Please open that separately.
Yes, that is what the subject says. However, out of 4 bugs logged against kudzu
for fc5 (and I wonder, how many people just gave up on the whole thing - "I knew
Linux sucked" - before even filing a bug report), 189602,183978 and 186538 all
say that kudzu "segfaults", but then say that the system hangs in the description.
I could file my problem against 186538 which is almost identical, except I see a
system freeze from the command line rather than a segfault.
I am under the impression that all of the above:
i) occur on laptops
ii) do not occur in SAFE mode
methinks they are very similar, but I'll refile or open a new bug if it helps.
Fixed in 1.2.41-1 by removing the offending code.