After update from xubuntu i686 version 16.04 to i686 18.04 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I had 32-bits OS of Xubuntu from 16.04, and answered yes to be upgraded into 18.04 on my HP EliteBook 6930p laptop.
Severals error came up after the reboot.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSign
Uname: Linux 4.15.0-33-generic i686
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
Date: Thu Aug 23 22:30:08 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2
InstallationDate: Installed on 2014-01-22 (1674 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageV
dpkg 1.19.0.5ubuntu2
apt 1.6.3ubuntu0.1
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago)
summary: |
- After update from xubuntu i686 version 04.16 to i686 04.18 package + After update from xubuntu i686 version 16.04 to i686 18.04 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1773859, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.