I don't think the GUI is meant to start bluetoothd at all. It only toggles the power state of the Bluetooth hardware. It assumes bluetoothd is always running. So failure to restart after a crash is a problem with bluez's systemd scripting.
** Package changed: gnome-control-center (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1948990 Title: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1948990/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
