desktop-packages team mailing list archive

[Launchpad Bug Tracker <461061@xxxxxxxxxxxxxxxxxx>]

[Expired for gnome-bluetooth (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-bluetooth (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/461061

Title:
  [KARMIC]bluetooth can't be re-enabled after it has been manually
  disabled

Status in “gnome-bluetooth” package in Ubuntu:
  Expired

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/461061/+subscriptions