Comment 34 for bug 284994

I wrote a followup - a web page for every owner of a bluetooth device
that needs a special PIN that would submit it as a new bug report is
possible...

Perhaps Ubuntu can write its own patch - it looks simple enough but I
would need time to add the panel (I've only done Gtk in Python).

The short answer is it cannot be hardcoded which is why every other
implementation (e.g. my Nokia tablet, or even my phone) doesn't do so.
 They typicall present something random but editable.

On Tue, Nov 11, 2008 at 8:23 AM, spaetz <email address hidden> wrote:
> 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 direct subscriber
> of the bug.
>