From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Description of problem:
When I boot Fedore Core 1.0 with my Zaurus plugged in and turned on,
Kudzu crashes. I see a FAILED message for it, and above it is shown a
In order for the Zaurus to be recognized and work, you have to put
this into /etc/hotplug/blacklist:
A friend of mine has also reported that redhat-config-network crashes
on startup when the Zaurus is plugged in and on.
Could be related if they depend on same libraries.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. With computer off, plug in and turn on Zaurus
2. Boot computer
3. The graphical boot screen switches to the detailed mode, and you
can see that kudzu has crashed with a segfault.
Does it crash post-boot as well?
Can you install the debuginfo and get a traceback?
Created attachment 96123 [details]
Strace output when I run kudzu that shows the segfault.
I haven't had a chance to find and install debuginfo yet, but here is the
strace output when kudzu crashes. Also, yes, it does crash post-boot when I
run from the commandline--thus the strace.
Created attachment 96329 [details]
GDB Output of Segfault
I was not able to find debuginfo, so I ran kudzu with gdb. This attached file
contains that. I also found that running hwbrowser crashes as well. I ran
python with DeviceList.py in GDB, and the second listing in this file is from
*** This bug has been marked as a duplicate of 106332 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.