Ubuntu
bluez package

package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

Bug #1718974 reported by Leonid on 2017-09-22

This bug report is a duplicate of: Bug #1700256: package bluez 5.37-0ubuntu5 failed to install/upgrade [bluez depends on udev (> = 170-1); but: Package udev is not configured yet.]. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	bluez (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

When updating

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Sep 22 22:25:17 2017
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2017-07-29 (55 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
InterestingModules: bluetooth
MachineType: Gigabyte Technology Co., Ltd. P35-S3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=68eb309e-4d7d-4735-b7ec-c972ec4839d6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.24
SourcePackage: bluez
Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: P35-S3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-S3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-S3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-S3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
hciconfig:

rfkill:

syslog:
Сен 22 22:23:03 leonid-P35-S3 NetworkManager[776]: <info> [1506108183.9686] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Сен 22 22:23:57 leonid-P35-S3 ureadahead[249]: ureadahead:unity-control-center_bluetooth.png: Относительный путь пропущен

Tags:

Revision history for this message

Leonid (leonid-reynish) wrote on 2017-09-22:

AptOrdering.txt Edit (587 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (58.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (624 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (57.2 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (11.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (695.0 KiB, text/plain; charset="utf-8")
HookError_ubuntu.txt Edit (826 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (7.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (33.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (552 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (787 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (141.6 KiB, text/plain; charset="utf-8")
getfacl.txt Edit (161 bytes, text/plain; charset="utf-8")

Leonidas S. Barbosa (leosilvab) on 2017-09-22

information type:

Private Security → Public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-11-07:

Status changed to 'Confirmed' because the bug affects multiple users.

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

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2018-02-27:

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 1700256, 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. Feel free to continue to report any other bugs you may find.