Upgrade from Jaunty 9.04 to Karmic 9.10 installArchives() failed : python-wadllib: subprocess installed post-installation script returned error exit status 139

Here is the error:

Setting up python-wadllib (1.1.2-0ubuntu1) ...
Segmentation fault
dpkg: error processing python-wadllib (--configure):
 subprocess installed post-installation script returned error exit status 139

2009-10-30 19:36:33,460 ERROR got an error from dpkg for pkg: 'python-wadllib': 'subprocess installed post-installation script returned error exit status 139

(and then a cascade of similar ones)

Could you please do a "$ ls -l /var/crash" and attach the output here?

As requested here is the contents of /var/crash

The contents of the Python-wadllib.0.crash were small so I've posted them as well.

===== python-wadllib.0.crash ========
ProblemType: Package
Date: Fri Oct 30 19:36:34 2009
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 139

Package: python-wadllib
SourcePackage: python-wadllib
VarLogDistupgradeAptlog: base64
 H4sICAAAAAAC/1ZhckxvZ0Rpc3R1cGdyYWRlQXB0bG9nAA==
================================

here is the output of ls -la in /var/crash as well

kat@zuperpaqi:/var/crash$ ls -la
total 2004 # this is strange, why does it show 2004 files when there are only 4 (6 if you count . and ..)
drwxrwxrwt 2 root root 64 2009-11-02 13:42 .
drwxr-xr-x 16 root root 4096 2009-11-02 13:37 ..
-rwxr-xr-x 1 root root 0 2009-11-02 08:55 .lock
-rw------- 1 root root 194670 2009-10-30 19:36 python-wadllib.0.crash
-rw------- 1 root root 13729 2009-10-31 18:20 _usr_bin_landscape-sysinfo.0.crash
-rw------- 1 kevin kevin 1826664 2009-11-02 08:55 _usr_lib_nspluginwrapper_i386_linux_npviewer.bin.1000.crash
kat@zuperpaqi:/var/crash$

Thanks for this additional data. That is odd, a exit status of 139 means a segfault but apport did not catch what segfaulted. If it was python, then apport was proably crashing itself :/

This looks like a hardware issue. If it's still an issue, could you run memtest on your system? (boot a live CD / USB key and select test memory)
Thanks in advance.

results of the requested memory test are clean... see attachment

Thanks.
Since there is not clear indication as what caused this bug and how to recreate it, I'm setting its status back to New and affecting it to python-support. Thanks for taking the time to make Ubuntu better!

Can you reproduce this crash with:
sudo update-python-modules --post-install
?

Sorry guys, Ubuntu now does not start at all on the machine. Get a blinking cursor before GRUB loads. Switching the machine to a permenant LTSP machine. Recovering the ubuntu installation would corrupt the bug. So I think this bug can be closed as no longer reproducable. Unless of course the other person who is affected can do this command for Loïc.

Thanks for following up. I'm closing this report due to your last comment.
If someone can reproduce this issue and provide the output of the command in comment 10 then don't hesitate to reopen this report.

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!