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/
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).
** Chang
^^^
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 (
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 Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bug
4 matches
Mail list logo
