Red Hat Bugzilla – Bug 511210
bluetooth not enabled until I turn RF kill switch off and then on again
Last modified: 2009-09-16 10:03:32 EDT
Description of problem:
After a reboot I have to turn the RF kill switch off and then on again before my bluetooth gets enabled.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Notification bar icon has a red cross.
I have a menu entry to turn off (yes, turn off, not on)
If I select Properties, it offers me a button to start the service. If I press the button it goes grey and nothing happens.
This is just like the previous bug I reported on bluez, except now I can fix it by turning the RF kill switch off and on again. After that it works nicely, at least for blueproximity and amora. I have not tried file transfers yet.
As above, but without having to turn off and on whenever I reboot.
HP EliteBook 2530p
Was fixed in 4.47-2:
* Wed Aug 05 2009 Bastien Nocera <firstname.lastname@example.org> 4.47-2
- Remove hid2hci calls, they're in udev now
- Work-around udev bug, bluetoothd wasn't getting enabled