package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11: seems to be a problem with dkms update for nvidia drivers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkms (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Kernel updates seem not to work any more with nvidia drivers (dkms). This problem already occurred with every new kernel image since i reinstalled Ubuntu 23.04 on a new disk. Since this also affects kernel security updates, i guess this also implies a security vulnerability (thats why i selected this also).
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-
ProcVersionSign
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelMo
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/seq: helmut 1943 F.... pipewire
CRDA: N/A
CasperMD5CheckR
Date: Thu Oct 5 09:33:30 2023
ErrorMessage: run-parts: /etc/kernel/
InstallationDate: Installed on 2023-06-24 (102 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: ASUSTeK COMPUTER INC. G751JT
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=
Python3Details: /usr/bin/
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageV
SourcePackage: dkms
Title: package linux-image-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G751JT.206
dmi.board.
dmi.board.name: G751JT
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.modalias: dmi:bvnAmerican
dmi.product.family: G
dmi.product.name: G751JT
dmi.product.sku: ASUS-NotebookSKU
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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.