package shared-mime-info 0.71-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[SanjayGoswami]

Binary package hint: shared-mime-info

This problem occurred during installation of k3b!

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: shared-mime-info 0.71-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Fri Dec 17 19:44:50 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 139
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: shared-mime-info
Title: package shared-mime-info 0.71-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[LexLythius (lexlythius)]

Same problem here.

OS Version: Ubuntu 10.04.2 LTS
Signature: Ubuntu 2.6.32-28.55-server 2.6.32.27+drm33.12
Uname: Linux server1 2.6.32-28-server #55-Ubuntu SMP Mon Jan 10 23:57:16 UTC 2011 x86_64 GNU/Linux

Find attached apt-get output, dmesg last lines and strace output.

If I get it right, looks like it's trying to read past apport.xml EOF (at offset 414) to complete a 8192 byte chunk.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in application being used by the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out!