[Bug 284994] Re: bluetooth-wizard unable to pair to fixed pin devices

Bug Watch Updater 284994 at bugs.launchpad.net
Fri Oct 27 08:14:04 UTC 2017


Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=472686.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-11-23T13:19:42+00:00 Jóhann wrote:

Description of problem:

Have been trying to connect a RIKALINE GPS Bluetooth dongle
and to do so I need to be able to enter the devices pin code
but when using the Bluetooth device wizard it detects the device 
fine then it tries to pair with the devices with some random pin number it ask me to enter a pin on the device ( for a split second ) the fails to connect 

Now the problem here is on this particular device I cannot enter
a pin code I need to set the pin code manually on the client that is trying to connect to the device to be able to pair with it.

I believe this causing a trouble for a lot of people since theres a lot of
devices out there that have a default pin of 1234 or 0000 etc...

[root at localhost bluetooth]# hcitool scan && hcitool inq 
Scanning ...
	00:00:00:00:54:4D	Rikaline
Inquiring ...
	00:00:00:00:54:4D	clock offset: 0x75a1	class: 0x000000


The default pin is 0000

Version-Release number of selected component (if applicable):

gnome-bluetooth-0.11.0-5.fc10.x86_64
gnome-bluetooth-libs-0.11.0-5.fc10.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Click the bluetooth icon 
2. Setup new device 
3. 
  
Actual results:

The wizard fails to pair with device.

Expected results:

The wizard to be able to pair with the device 
if it fails with a random pin then try common ones ( 1234 or 0000 etc ) if that fails prompt the user to enter the pin then try to pair with it again.

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/87

------------------------------------------------------------------------
On 2008-11-26T05:49:01+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/91

------------------------------------------------------------------------
On 2009-02-23T23:23:47+00:00 Andrey wrote:

This seems to be upstream issue. Ubuntu 8.10 has the same issue:

https://bugs.launchpad.net/fedora/+source/bluez-gnome/+bug/284994

Upstream Gnome bug (with a bit hot discussion) posted here:

http://bugzilla.gnome.org/show_bug.cgi?id=560316

Follow-up in Gnome mailing list here:

http://thread.gmane.org/gmane.linux.bluez.kernel/717/focus=721

Does anybody (from Fedora developers) know if there are any [positive]
change ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/110

------------------------------------------------------------------------
On 2009-02-25T09:06:43+00:00 Andrey wrote:

Some updates:

1. Upstream bugzilla has more than 20 bugs opened with requests to
support specific devices (including one from me personally):

http://bugzilla.gnome.org/buglist.cgi?product=bluez-
gnome&bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&bug_status=UNCONFIRMED&component=wizard

2. Vincent Untz has proposed a patch to solve the issue here:

http://bugzilla.gnome.org/show_bug.cgi?id=570457

He also posted this patch in the mailing list:

http://article.gmane.org/gmane.linux.bluez.kernel/1399

I have not found any feedback so far (2 weeks away now) neither in
Bugzilla, nor in mailing list, nor in the code tree.

Jiri, can you please be so kind to discuss the issue with responsible
Gnome developer (Bastien Nocera) ? He seems to be a bit hard talking to
regular users, may be developer-to-developer discussion will be more
efficient ? Of course, if this is acceptable for you.

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/111

------------------------------------------------------------------------
On 2009-02-25T11:38:04+00:00 Jiri wrote:

Hi, I take a look at this asap (tommorow probably) and try to come up
with some solution.

Jirka

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/112

------------------------------------------------------------------------
On 2009-02-28T12:21:59+00:00 Andrey wrote:

Jiri, it seems that Bastien has made pretty substantial changes in the
upstream. I wonder what should be further steps with this bug - should
we wait until the next release of gnome-bluetooth ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/114

------------------------------------------------------------------------
On 2009-03-04T16:11:56+00:00 Bastien wrote:

gnome-bluetooth != bluez-gnome.

I never saw this bug because you posted it against a package which
contains a bunch of outdated libs only used by gnome-phone-manager.

FWIW, fixed in bluez-gnome in a nasty way, a proper fix will be in the
gnome-bluetooth fork of bluez-gnome when it lands in rawhide.

"yum --enablerepo=rawhide update bluez-gnome" should do the trick for
you. I also added your device to the PIN database in gnome-bluetooth SVN
trunk.

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/116


** Changed in: bluez-gnome (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/284994

Title:
  bluetooth-wizard unable to pair to fixed pin devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez-gnome/+bug/284994/+subscriptions



More information about the Ubuntu-bluetooth mailing list