package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-signed (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't kno why my computer is blocked just 15 s afeter start up
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-
ProcVersionSign
Uname: Linux 6.2.0-32-generic x86_64
NonfreeKernelMo
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
CRDA: N/A
CasperMD5CheckR
Date: Fri Dec 8 12:03:31 2023
DpkgHistoryLog:
Start-Date: 2023-12-08 12:03:21
Commandline: /usr/bin/
Install: linux-signature
Upgrade: linux-modules-
ErrorMessage: installed linux-image-
InstallationDate: Installed on 2022-10-31 (403 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A17 FA706ICB_TUF706ICB
ProcFB: 0 amdgpudrmfb
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: linux-signed
Title: package linux-image-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2022
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FA706ICB.304
dmi.board.
dmi.board.name: FA706ICB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.ec.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: ASUS TUF Gaming A17
dmi.product.name: ASUS TUF Gaming A17 FA706ICB_TUF706ICB
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
tags: | removed: need-duplicate-check |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.