package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-firmware (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
System is a new build. Right off the lastest ISO. Updates were applied. There were issues applying updates. This system does have a mobile i7 and a Geforce 960m 4GB edition.
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: linux-firmware 1.175.3
ProcVersionSign
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Apr 11 20:06:27 2019
Dependencies:
Df:
Dmesg:
ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 2
InstallationDate: Installed on 2019-04-11 (4 days ago)
InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
PackageArchitec
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageV
dpkg 1.19.0.5ubuntu5
apt 1.7.4
SourcePackage: linux-firmware
Title: package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
From the logs:
Setting up linux-firmware (1.175.1) ... img-4.18. 0-17-generic mkinitramfs: 165: /usr/sbin/ mkinitramfs: Cannot fork mkinitramfs: 225: /usr/sbin/ mkinitramfs: Cannot fork mkinitramfs: 183: /usr/sbin/ mkinitramfs: Cannot fork update- initramfs: 145: /usr/sbin/ update- initramfs: Cannot fork
update-initramfs: Generating /boot/initrd.
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
This could be a systems resource issue, for example if you set a limit on the number of processes allowed and reached that limit. It's hard to pinpoint a cause with the limited information attached to this bug. If you continue to have this issue, please collect dmesg output and attach it here as that might provide some clues.