I can confirm this bug is now fixed.
bluez-gnome is still at 0.25-0ubuntu1 though, so i have no idea what fixed it (kernel modules?).
I can confirm this bug is now fixed.
bluez-gnome is still at 0.25-0ubuntu1 though, so i have no idea what fixed it (kernel modules?).