Bug 580723

Summary:	gnome-bluetooth cannot connect with Parani SD100 serial port BlueTooth adapter
Product:	[Fedora] Fedora	Reporter:	Aram Agajanian <agajania>
Component:	gnome-bluetooth	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	bnocera
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-12-03 16:09:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aram Agajanian 2010-04-08 21:12:16 UTC

Description of problem:
I am unable to connect to a Parani SD100 serial port Bluetooth adapter with gnome-bluetooth.

The Parani SD100 is used to communicate with the Scribbler robot. This is used by some colleges/schools for teaching computer programming. (See http://roboteducation.org).

It seems that one problem is that the SD100 does not have a PIN by default, and gnome-bluetooth requires that a PIN be set.

It is also unclear if gnome-bluetooth supports the Bluetooth serial port service at all.

Version-Release number of selected component (if applicable):
2.28.6-2.fc12

How reproducible:
Happens every time.

Steps to Reproduce:
1. Click on "Setup a new device..." option.
2. Click on SD100 entry in the list of detected devices.
3. (Optional) Try to choose a PIN option. None of these work as far as I can tell.
4. Click on the Forward button.
5. You are asked to enter a PIN into gnome-bluetooth or the SD100 (depending on the PIN option). The SD100 does not have a user interface to enter a PIN. gnome-bluetooth requires that a PIN be entered.

Actual results:
I have not been able to establish a connection with the SD100 using gnome-bluetooth.

Expected results:
A connection is established and the user can access /dev/rfcomm0 (or perhaps another rfcomm device).

Additional info:
I am able to connect to the SD100 with the blueman application. It is able to detect that the SD100 supports the Bluetooth serial port service. It also has an option "Proceed without Pairing" which allows you to connect without entering a PIN.

Comment 1 Bastien Nocera 2010-05-10 13:54:03 UTC

This is a problem in gnome-bluetooth indeed.

Please attach the output from:
hcitool scan
when the device is discoverable
and:
hcitool inq 00:11:22:33:44:55
obviously replacing 00:11:22:33:44:55 by the Bluetooth address of the device.

Comment 2 Aram Agajanian 2010-05-26 22:34:56 UTC

$ hcitool scan

Scanning ...
	00:01:95:07:BA:B8	PSD100v1.1.1-07BAB8

$ hcitool inq 00:01:95:07:BA:B8

Inquiring ...
	00:01:95:07:BA:B8	clock offset: 0x6a40	class: 0x001f00

Comment 3 Bastien Nocera 2010-08-03 14:41:09 UTC

This should be fixed by this commit:
http://git.gnome.org/browse/gnome-bluetooth/commit/?id=04c32da45caace7aa47b877df6917a101223338a

which should apply cleanly on top of the current F13 and F12 packages. Any chance you could test the patch? If you're having trouble compiling, let me know, and I'll build a package as soon as the scratch builds are back online for Fedora.

Comment 4 Aram Agajanian 2010-08-04 20:34:25 UTC

It doesn't seem to work for me.  I could be doing something wrong.

When using the Set up new device... option, the Device Search finds the Parani SD100.  The Type is listed as Unknown.

Under PIN options, there is now an option named "Do not pair".  However when I select that option and click on the Close button, it doesn't seem to be remembered.  When I bring up the PIN options again, Custom PIN is selected with a value of NULL.

I close the PIN options, select the PSD100v1.1.1-07B817, and then press the Foward button.  The message "Connecting to PSD100v1.1.1-08B817..." briefly appears.  Then, the message "Setting up PSD100v1.1.1-07B817 failed" appears. 

I don't find any rfcomm devices in /dev.

Comment 5 Bug Zapper 2010-11-03 17:33:37 UTC

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2010-12-03 16:09:20 UTC

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.