Ubuntu
blueman package

Bluetooth crashed after resuming from suspend

Bug #1851265 reported by Johannah Sprinz on 2019-11-04

This bug report is a duplicate of: Bug #1246981: Bluetooth devices fail to re-connect after sleep.. Edit Remove

This bug affects 2 people

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

Bug Description

Indicator disappeared, "Bluetooth Adapters" window completely empty and very small with only a button that says "close".

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: blueman 2.0.8-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Nov 4 18:36:55 2019
ExecutablePath: /usr/bin/blueman-adapters
InstallationDate: Installed on 2019-06-28 (128 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
InterpreterPath: /usr/bin/python3.7
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
SourcePackage: blueman
UpgradeStatus: Upgraded to eoan on 2019-10-28 (7 days ago)

Tags:

Revision history for this message

Johannah Sprinz (neothethird) wrote on 2019-11-04:

Dependencies.txt Edit (7.8 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (302 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (85.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-11-04:

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

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

Revision history for this message

Syfer Polski (syferpl) wrote on 2019-11-04:

I'm seeing something very similar. Judging by dmesg output, file descriptors from bluetooth connections aren't cleaned up after suspending, which blocks new connections back to the device. It usually fixes itself when the OS is shutdown(not rebooted), or operates without suspending for a few hours. Dmesg:
[159056.186990] usb 1-4: new full-speed USB device number 14 using xhci_hcd
[159056.187129] usb 1-4: Device not responding to setup address.
[159056.187189] debugfs: Directory '21' with parent 'devices' already present!
[159056.395246] usb 1-4: Device not responding to setup address.
[159056.395296] debugfs: Directory '22' with parent 'devices' already present!
[159056.603067] usb 1-4: device not accepting address 14, error -71
[159056.603164] usb usb1-port4: unable to enumerate USB device

Bluetooth was a lot less flaky in Kubuntu 19.04 then it is in Kubuntu 19.10

Revision history for this message

Syfer Polski (syferpl) wrote on 2019-11-04:

I don't have blueman installed, so I think NeoTheThird's guess for the guilty package is wrong. Regardless, I'd be happy to link my report as a possible duplicate - https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1851275