We've been discussing rfkill on the duplicate bug (#1922338). The rfkill output from just after boot was: ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth blocked unblocked 2 wlan phy0 unblocked unblocked 4 bluetooth hci0 blocked unblocked
And we've come to the conclusion that the GUI does not run rfkill unblock, however I've checked today and after flicking the GUI switch it does indeed unblock the device: ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked 4 bluetooth hci0 unblocked unblocked It still doesn't work of course. I can also manually run rfkill unblock 1 (and 3), but that doesn't work either. Bluetooth starts working only after unblocking and then restarting bluetooth.service -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1912940 Title: Bluetooth (ideapad_bluetooth) disabled every time on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
