Bug 124437 - kudzu segmentation fault
Summary: kudzu segmentation fault
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kudzu
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-26 15:58 UTC by Brian Millett
Modified: 2014-03-17 02:45 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-05-26 19:59:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Brian Millett 2004-05-26 15:58:58 UTC
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):
kudzu-1.1.68-1

How reproducible:
Always

Steps to Reproduce:
1.boot system
2.OR 
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
                                                           [FAILED]
Updating /etc/fstab                                        [  OK  ]


Expected Results:  should just work

Additional info:

This was with the latest update from 
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/2/i386/

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.

Thanks.

Comment 1 Bill Nottingham 2004-05-26 19:28:58 UTC
Got a strace, or a gdb backtrace?

Comment 2 Brian Millett 2004-05-26 19:59:54 UTC
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.