This bug still exists for me in a fresh install of Maverick, and it was in Jaunty also. Sometimes the program will use a custom PIN and sometimes it will not, possibly due to the order I clicked things, as per #8. I previously used Blueman for pairing until my Bluetooth DUN stopped working with Blueman. Blueman may be a workaround for pairing some of your devices. From what I've seen, devices paired in either one will show up in the other, but the pairing may be missing functionality.
Re #6: I have not run the tests from #241000 (http://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000), but since that bug is marked as closed, i would agree that this is similar but not a duplicate, and thus needs its own attention. This has been open for over a year, are there any developers looking at this yet? This seems like an important issue for Bluetooth usability. I'm a programmer and I would be willing to poke around, but I have never worked on an Ubuntu package before and I don't know where to start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/480959 Title: Bluetooth almost impossible to pair - too short timeout, pin sel fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
