package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to install/upgrade: installed linux-image-5.13.0-40-generic package post-installation script subprocess returned error exit status 139

[Pablo Matorras]

.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Apr 25 08:15:43 2022
DuplicateSignature:
 package:linux-image-5.13.0-40-generic:5.13.0-40.45~20.04.1
 Setting up linux-image-5.13.0-40-generic (5.13.0-40.45~20.04.1) ...
 Segmentation fault (core dumped)
 dpkg: error processing package linux-image-5.13.0-40-generic (--configure):
  installed linux-image-5.13.0-40-generic package post-installation script subprocess returned error exit status 139
ErrorMessage: installed linux-image-5.13.0-40-generic package post-installation script subprocess returned error exit status 139
InstallationDate: Installed on 2020-10-30 (542 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.6
SourcePackage: linux-signed-hwe-5.13
Title: package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to install/upgrade: installed linux-image-5.13.0-40-generic package post-installation script subprocess returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in the application being used for the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]