package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1607874 reported by Didi Dwi Novianto on 2016-07-29
76
This bug affects 15 people
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
High
Unassigned

Bug Description

ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sysv-rc.0.crash'

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sysv-rc 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Jul 29 23:52:04 2016
DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (833 days ago)
InstallationMedia:

PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.0.1ubuntu2.14
SourcePackage: sysvinit
Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

tags: removed: need-duplicate-check
Launchpad Janitor (janitor) wrote :

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

Changed in sysvinit (Ubuntu):
status: New → Confirmed
Changed in sysvinit (Ubuntu):
importance: Undecided → High
Rudi Hansen (rsh-pobox) wrote :

I get this error when trying to do a release upgrade from 14.04.5 LTS to 16.04.3 LTS

Witch surprises me when i see this bug was reported almost one year ago.
Any chance this will be fixed?

selinuxium (selinuxium) wrote :

Just suffered this issue myself.

Winding back to previous state.

John Wilson (jowilhnson) wrote :

Same. Attempted upgrade from 14.04.5 LTS to 16.04.3 LTS

Greg Rundlett (greg.rundlett) wrote :

#metoo

somekool (somekool) wrote :

#metoo !

14.04 is about to go out of support, I think a lot of people will attempt to upgrade their base AMI from 14.04 to 16.04

at least, that's my case.

if this 3 years old bug still unassigned. does this mean this upgrade path from LTS to LTS is not possible ?!?

"not possible" - In my experience with a handful of machines, upgrade to 16.04 was possible on all but one, but not smooth on any (as far as I remember). On the machine which encountered this specific error, it took some searching on the error message, then running the plausible relevant commands (I think apt-get and/or dpkg, but I do not remember offhand).

tuxayo (tuxayo) wrote :

Hi, I upgraded a Ubuntu 14.04 to 16.04 and got many failed packages configurations during the upgrade. It's likely due to this.

After the upgrade, *before rebooting*, I did

dpkg --configure --pending

remaining errors were on linux-* packages and initramsfs-tools, still not rebooted.

I removed old packages from kernel 3.13 that where still here and caused failures on microcode

dpkg --configure -a
issue with casper-memdisk

Removed it: https://askubuntu.com/questions/624519/upgrade-from-14-04-to-15-04-fails/635679#635679
sudo dpkg -P casper-memdisk

dpkg --configure -a
success

reboot, doesn't boot

grub => failsafe
in menu select => continue normal boot (actually that's not a normal boot, I guess things like nomodeset have been added)
boot success

To be continued: to be able to normally boot. But I hope that these details can help someone else. (disclaimer: I might have done something stupid ^^")

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers