Bug 124437 - kudzu segmentation fault
kudzu segmentation fault
Product: Fedora
Classification: Fedora
Component: kudzu (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-05-26 11:58 EDT by Brian Millett
Modified: 2014-03-16 22:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-26 15:59:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Millett 2004-05-26 11:58:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040525 Firefox/0.8.0+

Description of problem:
starting kudzu at boot time fails with a segmentation fault

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.boot system
3.service kudzu start

Actual Results:  Checking for new hardware/etc/init.d/kudzu: line 97:
 4762 Segmentation fault    /usr/sbin/kudzu $KUDZU_ARGS -t 30
Updating /etc/fstab                                        [  OK  ]

Expected Results:  should just work

Additional info:

This was with the latest update from 

I just noticed that the rev in rawhide is kudzu-1.1.67-1.  What gives?
 Am I getting messed up by getting update from update/testing & rawhide?
I thought rawhide was ahead of updates.

Comment 1 Bill Nottingham 2004-05-26 15:28:58 EDT
Got a strace, or a gdb backtrace?
Comment 2 Brian Millett 2004-05-26 15:59:54 EDT
Ok, I'm really confused now.  I had downgraded to kudzu in rawhide
(1.1.67-1).  Got your email, so I rpm -Uvh the 1.1.68-1 rpms.  Ran the
command again and this time it works.

I can not reproduce it.  Could there be something with yum update ?

Thank you, and I'll mark this as closed.

Note You need to log in before you can comment on or make changes to this bug.