After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 560316 - bluez-gnome wizard fails effectively for most non-keyboard devices
bluez-gnome wizard fails effectively for most non-keyboard devices
Status: RESOLVED DUPLICATE of bug 560315
Product: bluez-gnome
Classification: Deprecated
Component: wizard
unspecified
Other All
: Normal normal
: ---
Assigned To: bluez-gnome-maint@gnome.bugs
bluez-gnome-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2008-11-11 11:20 UTC by Sebastian Spaeth
Modified: 2008-11-11 12:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Spaeth 2008-11-11 11:20:07 UTC 
Please describe the problem:
Please see ubuntu bug https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/284994/

The bluez-gnome bluetooth wizard requires a random PIN to be entered or tries 1234 hardcoded in the source (recent svn seems to add a few more hardcoded numbers for a few more devices like TomToms).

This fails effectively for all devices that don't have a keyboard and use 0000 (or anything else but 1234), the dialog flashes up "enter pin" and disappears with "pairing failed".

The correct solution is really to offer a dialog in all cases so that people can enter the pin they want. Probably prepoluate the dialog field with a random number but make it still overridable by people.

A big thanks from all bluetooth GPS owners!

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Bastien Nocera 2008-11-11 12:49:14 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 560315 ***