[Bug 461061] [NEW] [KARMIC]bluetooth can't be re-enabled after it has been manually disabled
Launchpad Bug Tracker
461061 at bugs.launchpad.net
Mon Oct 26 17:37:30 GMT 2009
You have been subscribed to a public bug:
Using latest karmic beta, on a macbookpro 5.5
Bluetooth works fine for a bluetooth mouse that was setup while in jaunty (using an older bluez package from intrepid following guideline from launchpad q&a and bug reports, etc.).
Then I upgraded to karmic beta. I've just noticed today that if I manually disable bluetooth (to reduce energy consumptoin while running on battery, etc.), I can't re-enable it again withtout reboot (I didn't try loging out and in again, sorry). When I attempt to re-enable bluetooth from the dropdown menu associated with the bluetooth icon in the top bar (using gnome), I see that the text changes as if bluetoth was enabled indeed, but no connection is done, the bluetoth icon is still light grey, and no option to select the bluetooth device from the list, as I could when I first booted the computer and opened the list of bluetoth devices.
Unlock that old bluetoth package and using al packages from karmic
doesn't make any change.
** Affects: gnome-bluetooth (Ubuntu)
[KARMIC]bluetooth can't be re-enabled after it has been manually disabled
You received this bug notification because you are a member of Bluetooth, which is subscribed to gnome-bluetooth in ubuntu.
More information about the Ubuntu-bluetooth