Ubuntu
bluez package

package bluez 5.65-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

Bug #2000714 reported by VinZR on 2022-12-29

This bug report is a duplicate of: Bug #1901115: package bluez failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.]. Edit Remove

This bug affects 1 person

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

Bug Description

Failed to start bluetooth generally
It also failed to upgrade because bluetooth timedout

Also, loading Settings menu taking around 1-2mn to load up

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: bluez 5.65-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Dec 29 11:20:21 2022
ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-11-07 (417 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude 7520
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=9b404c17-8df7-4455-9565-d88ae66441b9 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
dpkg 1.21.9ubuntu1
apt 2.5.3
SourcePackage: bluez
Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to kinetic on 2022-12-29 (0 days ago)
dmi.bios.date: 11/15/2022
dmi.bios.release: 1.22
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.22.0
dmi.board.name: 0CVCMK
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd11/15/2022:br1.22:svnDellInc.:pnLatitude7520:pvr:rvnDellInc.:rn0CVCMK:rvrA01:cvnDellInc.:ct10:cvr:sku0A38:
dmi.product.family: Latitude
dmi.product.name: Latitude 7520
dmi.product.sku: 0A38
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: Primary Bus: USB
  BD Address: 48:51:C5:06:6C:87 ACL MTU: 1021:4 SCO MTU: 96:6
  DOWN
  RX bytes:35379 acl:639 sco:0 events:3462 errors:0
  TX bytes:817060 acl:45 sco:0 commands:3339 errors:0

Tags:

Revision history for this message

VinZR (vinz-zeze) wrote on 2022-12-29:

AptOrdering.txt Edit (51.4 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (139.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Df.txt Edit (512 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (137.7 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (172.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (408.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (44.2 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (969 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Lsusb-v.txt Edit (91.3 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (14.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (10.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (13.0 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (393.1 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (2.3 MiB, text/plain; charset="utf-8")
getfacl.txt Edit (160 bytes, text/plain; charset="utf-8")
rfkill.txt Edit (113 bytes, text/plain; charset="utf-8")
syslog.txt Edit (12.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2023-01-04:

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 1901115, 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.