Luckily, I still had my terminal with the flash process open. I flashed it and it rebooted at 14:38:13. So 14:41:46 is indeed after rebooting, the first time, after the switch to rc-proposed. A later manual shutdown and start of the device resolved the issue. It might have been one of those things that happen only in very specific circumstances. I didn't update anything after switching to rc-proposed, I did check if there were any updates, but there were none. (which makes sense)
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1531515 Title: Bluetooth cannot be enabled on Ubuntu Touch rc-proposed Nexus 4 Status in bluez package in Ubuntu: Incomplete Bug description: After switching from OTA8.5 to rc-proposed (to test if my BT keyboard would work with that) BT cannot be turned on any more. I can flip the switch, but after 30s it is switched off again (probably never turned on). I am unable to discover any BT devices. Running bluetoothctl on the devices from the terminal and then entering "show" results in: "No default controller available" I switched to rc-proposed for the Nexus 4 like this: ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
