package liblapack3gf 3.3.0-3 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Segmentation fault)

Bug #818320 reported by Souldjer Stylee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lapack (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

About 2mins after logging into the user account, even from a cold boot, unplugged, the pc gets a system problem error

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: liblapack3gf 3.3.0-3
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Jul 29 19:15:48 2011
ErrorMessage: subprocess installed post-installation script was killed by signal (Segmentation fault)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: lapack
Title: package liblapack3gf 3.3.0-3 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Segmentation fault)
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Souldjer Stylee (ghetyoungain) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

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!

Changed in lapack (Ubuntu):
status: New → Invalid
tags: added: package-install-segfault
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.