Comment 0 for bug 1962542

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.

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