package linux-modules-extra-5.4.0-31-generic 5.4.0-31.35 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
ok
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-modules-
ProcVersionSign
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
AptOrdering:
linux-
linux-
linux-
NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CasperMD5CheckR
Date: Sun May 24 08:52:16 2020
DpkgTerminalLog:
dpkg: error processing package linux-modules-
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
dpkg: too many errors, stopping
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
InstallationDate: Installed on 2020-04-26 (27 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: FUJITSU LIFEBOOK AH531
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/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageV
SourcePackage: linux
Title: package linux-modules-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: 1.27
dmi.board.name: FJNBB0F
dmi.board.vendor: FUJITSU
dmi.chassis.type: 9
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU/
dmi.product.name: LIFEBOOK AH531
dmi.sys.vendor: FUJITSU
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.