Ubuntu
initramfs-tools package

package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2

Bug #1780707 reported by Montecreasor on 2018-07-09

This bug report is a duplicate of: Bug #1568071: package initramfs-tools 0.122ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2: Cannot fork. Edit Remove

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	initramfs-tools (Ubuntu)	Triaged	Undecided	Unassigned

Bug Description

After installing a fresh install of ubuntu 18.04, the software updater asked me to update and after saying yes, it reported this error about initramfs-tools.

Also, another error just appeared which is much worse ... Here is what the dialog says:

An unhandlable error occured
There seems to be a programming error in aptdaemon, the software that allows you to install/remove software and to perform other package management related tasks.

Not that the install was a full erase of a partition and now an update or merge

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jul 8 22:33:38 2018
Df:

Dmesg:

ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 2
InstallationDate: Installed on 2018-07-09 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu2
apt 1.6.2
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Montecreasor (montecreasor) wrote on 2018-07-09:

AptOrdering.txt Edit (6.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.1 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (117.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (34.3 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (749 bytes, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2018-07-09

tags:

removed: need-duplicate-check

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-07-10:

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

Changed in initramfs-tools (Ubuntu):
status:	New → Confirmed

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2018-10-09:

Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
/usr/share/initramfs-tools/hooks/framebuffer: 146: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
/usr/share/initramfs-tools/hooks/framebuffer: 65: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
E: /usr/share/initramfs-tools/hooks/framebuffer failed with return 2.
/usr/sbin/mkinitramfs: 181: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/update-initramfs: 145: /usr/sbin/update-initramfs: Cannot fork
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 2

Changed in initramfs-tools (Ubuntu):
status:	Confirmed → Triaged

Revision history for this message

Benjamin Drung (bdrung) wrote on 2023-12-15:

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 1568071, 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.