From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description of problem: I have been seeing bug #112718 on my MSI K7T. After updating to kudzu- 1.1.36.1-1 the segmentation fault is still there. Version-Release number of selected component (if applicable): kudzu-1.1.36.1-1 How reproducible: Always Steps to Reproduce: 1. boot Fedora Core 1 on MSI K7T 2. 3. Actual Results: The graphical boot gets interrupted and reports segmentation fault in Kudzu Expected Results: The graphical boot to continue without segfault Additional info:
Can you get a backtrace?
Yes, but I will need some instructions on how to run the backtrace.
Install the kudzu debuginfo file from the debug directory of the updates. Then, run: gdb /usr/sbin/kudzu Enter 'r' to run the program And, when it segfaults, enter 'bt' for a backtrace.
Created attachment 98580 [details] gdb trace of kudzu segfault
See attached trace. Had to run from console, KDE went haywire when running Kudzu from there
rpm -V kudzu shows no changes, correct? Can you attach the output of kudzu -p?
Created attachment 98601 [details] Output of kudzu -p
rpm -V shows up empty. See attached file for output of kudzu -p.
hwconf.c:696 says: if (dev->device && isAliased(cf,dev->device,dev->driver)!=-1 So, it shouldn't get there with dev->device == NULL. Hm, will have to test some more.
Any progress? Anything I can do to help?
Nope, no progress... it really looks like a 'that can't happen' things. Unless the backtrace is screwed up. :/
Any way I can check if the backtrace is screwed up? Anything else I can do?
Closing bugs on older, no longer supported releases. Apologies for any lack of response. Please open a new bug if this persists on a current release, such as Fedora Core 3.