On Tue, January 30, 2007 11:20, Marcel Holtmann said: > I think all these problems on Apple based system are caused by a race > condition in the startup and init routines for the Bluetooth adapter. I > am pretty sure that I finally fixed this. At least my Quad G5 running > Edgy now has no problems anymore. > > The main problem was that the command for setting the scan mode failed. > And this means that the adapter was available, but neither page scan nor > page inquiry were set. This results in a non-connectable and non- > discoverable Bluetooth adapter. However HID mice and keyboards wanna > reconnect to the adapter and if it is in non-connectable mode (page scan > off) then they simply can't. > > This race condition was present on all architectures, but for some > strange reason only the Apple machines with the HID proxy adapters > suffered from it. > > Anyhow this has been fixed with the bluez-utils-3.9 release and for > Feisty it might be a good idea to simply sync with the new upstream > source.
I disagree, the problem is not only on Apples! See my previous posts. It's also on x86. Or else it's a related but different problem, but "for the rest of us", we can't tell the difference. -- Amedee -- Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty https://launchpad.net/bugs/32415 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
