[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
** Changed in: bluez Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
OK the crash is a separate issue. This is https://github.com/bluez/bluez/issues/284 which is also fixed in BlueZ 5.64. ** Bug watch added: github.com/bluez/bluez/issues #284 https://github.com/bluez/bluez/issues/284 ** Bug watch added: github.com/bluez/bluez/issues #284 https://github.com/bluez/bluez/issues/284 ** Changed in: bluez Remote watch: github.com/bluez/bluez/issues #272 => github.com/bluez/bluez/issues #284 ** Changed in: bluez (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** No longer affects: linux (Ubuntu) ** No longer affects: linux-firmware (Ubuntu) ** Tags added: fixed-in-5.64 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
See also bug 1962563. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
If you can find evidence of 'bluetoothd' crashing then it is https://github.com/bluez/bluez/issues/272 (fixed in BlueZ 5.64). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
Actually it sounds like https://github.com/bluez/bluez/issues/272 but yours isn't crashing(?) There's mention of QC35 in https://github.com/bluez/bluez/issues/220 too, and that it works after downgrading to BlueZ 5.61. Both seem to be fixed in upstream master (which will be BlueZ 5.64). ** Changed in: bluez (Ubuntu) Status: Invalid => New ** Bug watch added: github.com/bluez/bluez/issues #272 https://github.com/bluez/bluez/issues/272 ** Bug watch added: github.com/bluez/bluez/issues #220 https://github.com/bluez/bluez/issues/220 ** Also affects: bluez via https://github.com/bluez/bluez/issues/272 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
Reassigned to the kernel/firmware packages. We next need to review what the kernel has logged during suspend/resume. Comment #18 doesn't look like enough info so can you attach the full log? (journalctl -b0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
^^^ That's missing two of your radio devices (the Intel Wifi and Bluetooth), if you compare to comment #17. So it looks like the kernel devices have vanished after resuming from suspend the first time. ** Changed in: bluez (Ubuntu) Status: New => Invalid ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
There is no difference in 'rfkill' before/after suspend. In both cases, the bluetooth line looks like this: heather@fenrir:~$ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth tpacpi_bluetooth_sw unblocked unblocked And the PID of bluetoothd is the same before/after suspend, and not missing. I've also added some apport info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
apport information ** Description changed: 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:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth 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: + 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]: [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 pulseau
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
Also does the 'rfkill' command show any difference in the radio status after resume? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: bose quietcomfort 35 unable to connect after suspend
Firstly good news that it partially works now. It didn't before according to bug 1620636. What is the Bluetooth chip in the laptop (lspci / lsusb)? We probably need to check to see if it is chip-specific (a kernel bug) or a BlueZ bug. Please also check the PID of bluetoothd to see if it's the same or different/missing after resume-from-suspend. ** Tags added: a2dp jammy resume suspend-resume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: bose quietcomfort 35 unable to connect after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
