Ubuntu
bluez package

connecting bluetooth devices fails

Bug #1971534 reported by Thomas Schweikle on 2022-05-04

This bug report is a duplicate of: Bug #1968875: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect. Edit Remove

This bug affects 1 person

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

Bug Description

Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect.

It is the same using graphical tools or cli.

It is the same for
- ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta)
- debian 11.3
- fedora 35

Working distros are:
- kali (latest rolling)
- openSUSE Leap 15.4
- openSUSE tumbleweed

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Wed May 4 08:57:30 2022
InstallationDate: Installed on 2021-08-18 (258 days ago)
InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20BWS33U00
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2015
dmi.bios.release: 1.17
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET52WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BWS33U00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.1
dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BWS33U00
dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
  BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6
  UP RUNNING PSCAN
  RX bytes:4581 acl:7 sco:0 events:435 errors:0
  TX bytes:46460 acl:7 sco:0 commands:399 errors:0

Tags:

Revision history for this message

Thomas Schweikle (tps) wrote on 2022-05-04:

CurrentDmesg.txt Edit (83.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.4 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Lsusb-t.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Lsusb-v.txt Edit (141.1 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (5.4 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (325 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (9.9 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (269.0 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (438.0 KiB, text/plain; charset="utf-8")
getfacl.txt Edit (133 bytes, text/plain; charset="utf-8")
rfkill.txt Edit (250 bytes, text/plain; charset="utf-8")
syslog.txt Edit (8.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2022-05-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 1968875, 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.