package udev 229-4ubuntu21.19 failed to install/upgrade: package udev is already installed and configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
ubuntu16.04.6
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu21.19
ProcVersionSign
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptdaemonVersion: 1.1.1+bzr982-
Architecture: amd64
Date: Mon Apr 8 08:14:29 2019
DuplicateSignature:
package:
Processing triggers for libc-bin (2.23-0ubuntu11) ...
dpkg: error processing package udev (--configure):
package udev is already installed and configured
ErrorMessage: package udev is already installed and configured
InstallationDate: Installed on 2019-04-08 (0 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0aa7 Intel Corp.
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 0408:5090 Quanta Computer, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1.5
apt 1.2.31
SourcePackage: dpkg
Title: package udev 229-4ubuntu21.19 failed to install/upgrade: package udev is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.46
dmi.board.
dmi.board.name: 8216
dmi.board.vendor: HP
dmi.board.version: 83.18
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.
dmi.sys.vendor: HP
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.