package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkms (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Maybe the issue is related to power saving. The system tried to download and update a package (new kernel image), AFAIK, without my intervention. Then one of the DKMS steps failed, and the install procedure failed. the dmesg command shows nothing particularly interesting.
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-
ProcVersionSign
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelMo
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/seq: pag 2330 F.... pipewire
CRDA: N/A
CasperMD5CheckR
Date: Tue Nov 21 19:12:16 2023
ErrorMessage: run-parts: /etc/kernel/
InstallationDate: Installed on 2022-09-13 (434 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/
PythonDetails: N/A
RelatedPackageV
SourcePackage: dkms
Title: package linux-image-
UpgradeStatus: Upgraded to lunar on 2023-06-05 (169 days ago)
dmi.bios.date: 12/29/2020
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P11RFH.
dmi.board.
dmi.board.name: NP550XCJ-XS2BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLA664A0C-
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: Notebook 5 Series
dmi.product.name: 550XCJ/550XCR
dmi.product.sku: SCAI-A5A5-
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
Right after submitting this bug (and before doing anything else) I ran a manual "apt update/apt upgrade", just in case.
To my surprise, the package installed cleanly (see attachment)
Really can't explain why it failed before. I didn't even rebooted the machine, so... no clue about why it worked now, after having failed previously.
Any ideas? maintainers of this package.
Anyway, hope this might be somehow useful for the developers/
Should it be closed right away?
Thanks!
Paulo