Ubuntu
linux package

package linux-headers-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: installed linux-headers-5.4.0-39-generic package post-installation script subprocess returned error exit status 1

Bug #1885274 reported by MJ Gober on 2020-06-26

This bug report is a duplicate of: Bug #2068107: package linux-headers-<version> <version> failed to install/upgrade: installed linux-headers-<version> package post-installation script subprocess returned error exit status. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Automated reporting popped up stating there is a problem and to report it.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-headers-5.4.0-39-generic 5.4.0-39.43
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: mjgober 1203 F.... pulseaudio
CasperMD5CheckResult: skip
Date: Fri Jun 26 06:42:54 2020
ErrorMessage: installed linux-headers-5.4.0-39-generic package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-05-30 (26 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IwConfig:
enp3s0 no wireless extensions.

lo no wireless extensions.

enp6s0 no wireless extensions.
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: Gigabyte Technology Co., Ltd. B365M DS3H
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0907d40a-1960-4538-a2a4-8091d6d91526 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu26
RfKill:

SourcePackage: linux
Title: package linux-headers-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: installed linux-headers-5.4.0-39-generic package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: B365M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B365M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Tags:

Revision history for this message

MJ Gober (mjgober) wrote on 2020-06-26:

AlsaInfo.txt Edit (53.1 KiB, text/plain; charset="utf-8")
AptOrdering.txt Edit (379 bytes, text/plain; charset="utf-8")
CRDA.txt Edit (468 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (81.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Df.txt Edit (1001 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (81.5 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (12.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.9 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (598 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (65.9 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lsusb-v.txt Edit (8.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (5.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.2 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (247.4 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (562.6 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2020-06-26

tags:

removed: need-duplicate-check

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2020-06-26: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

You-Sheng Yang (vicamo) wrote on 2020-06-26:

Setting up linux-headers-5.4.0-39-generic (5.4.0-39.43) ...
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-39-generic
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/tn40xx/001/source/dkms.conf does not exist.
...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
dpkg: error processing package linux-headers-5.4.0-39-generic (--configure):
installed linux-headers-5.4.0-39-generic package post-installation script subprocess returned error exit status 1

You have unknown broken dkms package tn40xx installed.

Changed in linux (Ubuntu):
status:	Confirmed → Invalid

Revision history for this message

Juerg Haefliger (juergh) wrote on 2024-06-06:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2068107, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.