package bluez-obexd 5.37-0ubuntu5.1 failed to install/upgrade: package bluez-obexd is already installed and configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I'm not sure.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bluez-obexd 5.37-0ubuntu5.1
ProcVersionSign
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptdaemonVersion: 1.1.1+bzr982-
Architecture: amd64
Date: Wed Sep 13 12:05:54 2017
DuplicateSignature:
package:
Processing triggers for fontconfig (2.11.94-
dpkg: error processing package bluez-obexd (--configure):
package bluez-obexd is already installed and configured
ErrorMessage: package bluez-obexd is already installed and configured
InstallationDate: Installed on 2017-09-01 (11 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Inspiron 3847
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1.2
apt 1.2.24
SourcePackage: dpkg
Title: package bluez-obexd 5.37-0ubuntu5.1 failed to install/upgrade: package bluez-obexd is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 088DT1
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 3847
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: AC:D1:B8:02:E3:88 ACL MTU: 1022:8 SCO MTU: 183:5
UP RUNNING
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3407 acl:0 sco:0 commands:49 errors:0
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1716972, so 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.