It is quite clear the developer is behaving decidedly irrationally (not to mention aggressively) on this one and is insisting, for reasons best known to himself, that users should not be permitted to enter their own PIN and each device's hard-coded PIN should be hard-coded into the source. His argument that users will pick insecure PINs is akin to suggesting users should not be able to pick their own passwords and instead should have their 10 digit alphanumeric password chosen for them whether they like it or not.
I have to say that this is bizarre. It worked fine and now it is broken. His view is that each piece of hardware that will not pair is a separate bug. I think we should therefore humour him (after all he has done the hard work here even if he does have bizarre views) and file a separate bug for each and every piece of hardware that will not pair. The upshot of this is that every downstream distro will have to address this issue separately as I don't believe that anyone will share his view. Consequently we shall eventually end up with the solution that the users want and he doesn't but it will involve much more work for everyone, including him. Perhaps if thirty bugs are reported, he may come to his senses but I doubt it. He will probably come here and threaten to have me kicked from LaunchPad instead - that seems to be more his style. -- bluetooth-wizard unable to pair to fixed pin devices https://bugs.launchpad.net/bugs/284994 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
