Comment 41 for bug 292042

I'm experiencing the exact same situation that hyperspaced described 6months ago (2nd post).

Use the gnome app, the keyboard is correctly recognized as a "Logitech Cordless Mediadiaboard Pro (TM)". I'm asked to input a pin, which I do using said keyboard. It confirms my correct entry of the password, and adds it to its list of devices. And that's where the fun ends, it never works afterwards. Neither the mouse, nor the keyboard do anything.

If I forgo the gnome app and install bluez-compat and use "hidd -connect AA:BB:CC:DD:EE:FF" I can get it to work instantly! However, the connection isn't permanent. Rebooting the system or letting the keyboard go into sleep mode (10mins) breaks the connection. Obviously needing a kb to run the script and not having a working kb create a bit of a vicious circle.

This is using Jaunty i386, but I've also tried every bluetooth capable livecd I have (including fedora/suse) all to no avail. They all use bluez apparently. I've tried compiling the latest bluez (4.39) from source - same issue.

At this point I'm at the limits of my knowledge, this is my first foray in using bluetooth. I'm more than happy to provide any info or logs that may help get this resolved.

I've also tried blueman. While a nicer interface, has the same issues.