** Changed in: bluez
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542
Title:
bose quietcomfort 35 unable to connect after suspend
Status in Bluez Utilities:
Fix Released
Status in bluez package in Ubuntu:
Fix Committed
Bug description:
Bose quietcomfort 35 is a common headset that can no longer connect to
a jammy system after just one suspend. This started at the end of
January but just now really debugging the issue.
Side note that my bluetooth mouse works fine without problem after any
amount of suspends.
The headset is only trying to connect to the jammy system (no other
bluetooth devices it's paired with has active bluetooth, to isolate
only the jammy <-> headset issue). This is jammy running on a T590, up
to date, not proposed.
heather@fenrir:~$ dpkg -l | grep bluetooth
ii gir1.2-gnomebluetooth-1.0:amd64 3.34.5-4
amd64 Introspection data for GnomeBluetooth
ii gnome-bluetooth 3.34.5-4
amd64 GNOME Bluetooth tools
ii libbluetooth-dev:amd64 5.63-0ubuntu1
amd64 Development files for using the BlueZ Linux Bluetooth
library
ii libbluetooth3:amd64 5.63-0ubuntu1
amd64 Library to use the BlueZ Linux Bluetooth stack
ii libgnome-bluetooth13:amd64 3.34.5-4
amd64 GNOME Bluetooth tools - support library
ii pulseaudio-module-bluetooth 1:15.99.1+dfsg1-1ubuntu1
amd64 Bluetooth module for PulseAudio sound server
On a fresh boot (not suspended yet), I can connect the headset
successfully. Here are the logs of that:
Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as
/devices/virtual/input/input30
Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
Mar 01 09:44:03 fenrir NetworkManager[1536]: <warn> [1646124243.8660]
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13
(Permission denied)
Mar 01 09:44:04 fenrir bluetoothd[1532]:
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3
processes of 1 users.
Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of
process 2708 owned by '1000' RT at priority 5.
Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3
processes of 1 users.
Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed:
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked
But then if I close the laptop lid and reopen, login, and try to
connect the headset the device is found invalid with the following
logs:
Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as
/devices/virtual/input/input152
Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
Mar 01 00:47:08 fenrir bluetoothd[40741]:
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error:
org.bluez.Error.InvalidArguments
Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
Mar 01 00:47:08 fenrir bluetoothd[40741]:
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error:
org.bluez.Error.InvalidArguments
Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
Mar 01 00:47:09 fenrir bluetoothd[40741]:
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error:
org.bluez.Error.InvalidArguments
Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
Mar 01 00:47:09 fenrir bluetoothd[40741]:
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error:
org.bluez.Error.InvalidArguments
Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply()
Hands-Free Voice gateway replied with an error:
org.bluez.Error.InvalidArguments, Unable to handle new connection
Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply()
Hands-Free Voice gateway replied with an error:
org.bluez.Error.InvalidArguments, Unable to handle new connection
Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply()
Hands-Free Voice gateway replied with an error:
org.bluez.Error.InvalidArguments, Unable to handle new connection
Mar 01 00:47:10 fenrir acpid[1503]: input device has been disconnected, fd 19
And then the headset will not connect until the next boot. This is 100%
reproducible for me too.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2020-06-29 (609 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20N4001LUS
Package: linux
PackageArchitecture: amd64
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic
root=UUID=80953ccb-1ccd-4c08-862c-22b80a0ea056 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Tags: jammy wayland-session
Uname: Linux 5.15.0-18-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/16/2019
dmi.bios.release: 1.39
dmi.bios.vendor: LENOVO
dmi.bios.version: N2IET61W (1.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20N4001LUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 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.9
dmi.modalias:
dmi:bvnLENOVO:bvrN2IET61W(1.39):bd05/16/2019:br1.39:efr1.9:svnLENOVO:pn20N4001LUS:pvrThinkPadT590:rvnLENOVO:rn20N4001LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N4_BU_Think_FM_ThinkPadT590:
dmi.product.family: ThinkPad T590
dmi.product.name: 20N4001LUS
dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590
dmi.product.version: ThinkPad T590
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 3C:F0:11:76:46:BA ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:59807 acl:2423 sco:0 events:3065 errors:0
TX bytes:693869 acl:203 sco:0 commands:2826 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1962542/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
