Ubuntu
systemd package

Some packages, e.g. systemd, fail to upgrade in Ubuntu app on Windows WSL (package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1)

Bug #1757538 reported by Rummskartoffel on 2018-03-21

This bug report is a duplicate of: Bug #1748659: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1. Edit Remove

This bug affects 8 people

Affects		Status	Importance	Assigned to	Milestone
	systemd (Ubuntu)	Confirmed	High	Unassigned

Bug Description

This occurred after running do-release-upgrade on Ubuntu 16.04 on the Linux Subsystem Windows. After the upgrade has failed, there are now dependency problems with udev and libudev1, but I do not know whether these are connected.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 234-2ubuntu12.3
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented
Date: Wed Mar 21 21:51:43 2018
Dmesg:

ErrorMessage: subprocess installed post-installation script returned error exit status 1
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcInterrupts:

ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory
RelatedPackageVersions:
dpkg 1.18.24ubuntu1
apt 1.2.26
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf

2 overridden configuration files found.
Title: package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-03-21 (0 days ago)

Tags:

Revision history for this message

Rummskartoffel (rummskartoffel) wrote on 2018-03-21:

AptOrdering.txt Edit (17.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (394 bytes, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (20.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (791 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (262 bytes, text/plain; charset="utf-8")

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2018-03-21:

Yes, we are aware that packages, and specifically systemd, fail to upgrade inside WSL container.

I will look into pushing out an update to the Ubuntu app in the store, with the new systemd already installed in-place.

summary:	- package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess - installed post-installation script returned error exit status 1 + Some packages, e.g. systemd, fail to upgrade in Ubuntu app on Windows + WSL (package systemd 234-2ubuntu12.3 failed to install/upgrade: + subprocess installed post-installation script returned error exit status + 1)
Changed in systemd (Ubuntu):
status:	New → Confirmed
importance:	Undecided → High