package linux-image-3.16.0-44-generic 3.16.0-44.59~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Bug #1477369 reported by Leong Weijian
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-lts-utopic (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

It started randomly

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-44-generic 3.16.0-44.59~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13
Uname: Linux 3.16.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Jul 23 10:24:18 2015
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationDate: Installed on 2015-05-11 (72 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: linux-lts-utopic
Title: package linux-image-3.16.0-44-generic 3.16.0-44.59~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Leong Weijian (weijian19391) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-lts-utopic (Ubuntu):
status: New → Confirmed
Revision history for this message
Bill Canaday (bill13510) wrote :

Installation continued after error was thrown. Appeared to complete, except that it exited with a generalized error message that some programs could not be installed. Moreover, instead of saying it could not write to the error log as it usually does, this time it said that no error log was found.

Not, apparently a killer.

I preceded this update with:
bill@bill-110-210:~$ sudo rm /boot/*[33,41]-generic (always trying to maintain 2 known-good installs prior to upgrading.

ls /boot appears to show a completed install.

bill@bill-110-210:~$ ls /boot
abi-3.16.0-38-generic initrd.img-3.16.0-49-generic
abi-3.16.0-45-generic lost+found
abi-3.16.0-46-generic memtest86+.bin
abi-3.16.0-49-generic memtest86+.elf
config-3.16.0-38-generic memtest86+_multiboot.bin
config-3.16.0-45-generic System.map-3.16.0-38-generic
config-3.16.0-46-generic System.map-3.16.0-45-generic
config-3.16.0-49-generic System.map-3.16.0-46-generic
extlinux System.map-3.16.0-49-generic
grub vmlinuz-3.16.0-38-generic
initrd.img-3.16.0-38-generic vmlinuz-3.16.0-45-generic
initrd.img-3.16.0-45-generic vmlinuz-3.16.0-46-generic
initrd.img-3.16.0-46-generic vmlinuz-3.16.0-49-generic

Revision history for this message
Bill Canaday (bill13510) wrote :

Um ... it happened again.

Revision history for this message
Bill Canaday (bill13510) wrote :

Since so few others have reported this issue, I'm guessing that I must be doing something wrong. Would anyone care to volunteer a guess as to what that might be? I'm not afraid of the CLI but my Linux Guru cap got lost at the dry cleaners.

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.