I must say I find the upstream reaction rather less helpful and optimal. (http://bugzilla.gnome.org/show_bug.cgi?id=560315#c5)
bluez-gnome seems to intent to special case each non-keyboard device in their source code rather than just allowing people to enter a fixed PIN in the wizard. Hardcoding the stuff is bound to lag behind existing devices and seems a rather bloaty solution to me. Most of the time people would know best whether to use 1234 or 0000 or somesuch. Whatever. As a consequence, I stop caring about upstream and work around this with a custom shell script. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
