package sessioninstaller 0.20+bzr141-0ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 139

Bug #1467656 reported by Parvu Florin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sessioninstaller (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The same

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: sessioninstaller 0.20+bzr141-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Mon Jun 22 21:18:21 2015
DpkgTerminalLog:
 Removing sessioninstaller (0.20+bzr141-0ubuntu4) ...
 Segmentation fault (core dumped)
 dpkg: error processing package sessioninstaller (--remove):
  subprocess installed pre-removal script returned error exit status 139
DuplicateSignature: package:sessioninstaller:0.20+bzr141-0ubuntu4:subprocess installed pre-removal script returned error exit status 139
ErrorMessage: subprocess installed pre-removal script returned error exit status 139
InstallationDate: Installed on 2015-06-22 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt 1.0.9.7ubuntu4
SourcePackage: sessioninstaller
Title: package sessioninstaller 0.20+bzr141-0ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Parvu Florin (florinparvu-contact) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) 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 the application being used for 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!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: package-install-segfault
Changed in sessioninstaller (Ubuntu):
status: New → Invalid
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.