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
