package linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139

Bug #2054116 reported by Andrew Brown
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-hwe-6.5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

No more details.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Feb 16 15:00:47 2024
DuplicateSignature:
 package:linux-image-6.5.0-18-generic:6.5.0-18.18~22.04.1
 Setting up linux-image-6.5.0-18-generic (6.5.0-18.18~22.04.1) ...
 Segmentation fault (core dumped)
 dpkg: error processing package linux-image-6.5.0-18-generic (--configure):
  installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139
ErrorMessage: installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139
InstallationDate: Installed on 2024-02-11 (4 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt 2.4.11
SourcePackage: linux-signed-hwe-6.5
Title: package linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Andrew Brown (trailrider183) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Hello Andrew, this is confusing, based on the segfault from the maintainer scripts, I was expecting to see more evidence of memory failure or disk failure in your logs, but they look reasonable enough.

It might still be worth running memtest86 overnight or over the weekend, just to be sure.

Thanks

information type: Private Security → Public
tags: removed: need-duplicate-check
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.