When i disable BT (either with bluedevil or from terminal) and then reboot or restart the bluetooth daemon, bluedevil cant control my BT anymore. Neither can it enable / disable it, nor can it scan, pair, etc.

Note:
* I can enable and reenable it, thats no problem. But when its disabled and then this bug comes up
* Removing /var/lib/bluetooth/*****/conf and restart the daemon fixes this bug, but only until I disable BT and restart again.
* When when i restart the daemon and BT was turned off, the icon is displayed, like BT is enabled.
* When i remove the config files and restart the daemon BT works like it is expected.
* I can ALWAYS use sudo hciconfig hci0 up sudo hciconfig hci0 down to enable / disable bluetooth
* "sudo hciconfig hci0 up" is another way to get bluedevil to work again

Conclusion:
bluedevil seems not to notice that bluetooth is turned off, when it gets started. It should check the information in /var/lib/bluetooth/aa:bb:cc:dd:ee/config so that it knows weather BT is disabled or enabled! Don't know wheather this has something to do with Arch moving /lib to /var/lib....

Workaround:
As a workaround i tried to make an autostart script, with sudo hciconfig hci0 up && sudo hciconfig hci0 down, to save power and also to make BT work again for me!

Once this issue has been triggered, is it possible to "disable" and then "enable" it again through Bluedevil?

Can you please add your feedback in: https://bugs.kde.org/show_bug.cgi?id=304292 ?

I will try to figure out this bug the next weekend, and would be useful to have all the info in the same place.

thanks !

bcooksley wrote:Once this issue has been triggered, is it possible to "disable" and then "enable" it again through Bluedevil?

No, this is not possible, since bluedevil thinks (i guess) BT is enabled. Because clicking on the icon shows all
the actions, BT can do normally. But no matter what i click nothing works. Even after clicking "disable" its still the same.

Right now i kind of fixed my problem by adding
sudo hciconfig hci0 up
sudo hciconfig hci0 down
to my /etc/rc.local

So sorry for not answering for some time. But still it would be nice to behave like before

Okay, looks like this will need a bug fix in Bluedevil, please follow the bug for further information as to this issue.

I just experienced this bug as well. From the tray notification icon I selected "turn off bluetooth" which, insteading of greying the icon, removed it completely. Upon a reboot, the bluetooth icon shows (NOT greyed) with all the settings present, but I cannot connect to any devices. I tried the hciconfig commands to no avail. I've just deleted the config file in /var/lib/bluetooth/**** and I'll try rebooting to see if that works. I'm running Kubuntu 13.10, KDE 4.11.1.

Is there anything in dmesg to indicate that your Bluetooth adapter is being initialized successfully?

Deleting the config file didn't help. I had to remove the entire /var/lib/bluetooth/**** folder and reboot. Bluetooth works again but all previous settings are erased. I don't see much interesting in dmesg, but that's like my problem. One thing says "Bluetooth: re-auth of legacy device is not possible." That's likely AFTER I got bluetooth working again though.

Okay. If I recall correctly, some devices handle being disabled very badly - and disappear entirely when they do so.
Unfortunately, bluetoothd saves their state and reapplies it on boot, hence why you need to erase data from /var/lib/bluetooth/ to fix things.