up2date --register proceeds to the point after selecting: Red Hat Enterprise Linux AS (v. 3 for AMD64/Intel EM64T) At this point the up2date channels window closes and what appears in the xterm window is: Reading DMI info failed Segmentation fault If I repeat the up2date without the "--register" argument I get the same "Segmentation fault" without the previous line "Reading DMI info failed" up2date-4.2.5-1 How reproducible: Always Steps to Reproduce: 1.up2date2.select package to install in new window - one item here: Red Hat Enterprise Linux AS (v. 3 for AMD64/Intel EM64T) Actual Results: after some progress bar info the window closes The original XTERM window shows "Segmentation fault" Expected Results: The up2date window should complete without segmentation fault
the dmi is segfaulting on the dmi info from that box. --nohardware is a workaround. I'm going to attach a python script to grab the dmi info in a format I can use to debug the dmi module. If you could run it on the box showing the segfault, and attach the result, it will help debug this.
Created attachment 101978 [details] python script to grab raw dmi info Run this script like: python getdmi.py run it as root. It should write out a file called "dmiinfo.out" please attach "dmiinfo.out" to this bug.
Created attachment 102080 [details] the output file requested from "python get_dmi.py" script
I updated to up2date version 4.2.33-1 and this problem was resolved
Closing as per comment #5.