package linux-image-extra-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: package linux-image-extra-4.4.0-138-generic is already installed and configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
the system shows that the package system is broken
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.4.0-138-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptdaemonVersion: 1.1.1+bzr982-
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CrashReports:
600:110:
640:0:
640:0:
644:0:
600:0:
Date: Mon Oct 29 23:43:21 2018
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
DuplicateSignature:
package:
Processing triggers for mime-support (3.59ubuntu1) ...
dpkg: error processing package linux-image-
package linux-image-
ErrorMessage: package linux-image-
HibernationDevice: RESUME=
InstallationDate: Installed on 2018-07-05 (116 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
MachineType: Dell Inc. Vostro 14-3468
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
SourcePackage: dpkg
Title: package linux-image-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.0.4
dmi.board.name: 0P1XYM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Vostro 14-3468
dmi.sys.vendor: Dell 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.