Bug 529027

Summary:	rfcomm.conf: bind option ignored
Product:	[Fedora] Fedora	Reporter:	Stefan Bradl <madrenegade>
Component:	bluez	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	anton, bnocera, dwmw2, marcel, plautrba
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:	2009-10-14 18:10:06 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 Stefan Bradl 2009-10-14 17:13:47 UTC

Description of problem:
devices with the option "bind yes;" in /etc/bluetooth/rfcomm.conf
should be automatically bound at startuo but they are not.


Steps to Reproduce:
1. try to use a device from rfcomm.conf with the "bind yes" option
  
Actual results:
no communication possible

Expected results:
same as after manually running "rfcomm bind rfcomm0"

Additional info:

Comment 1 Bastien Nocera 2009-10-14 18:10:06 UTC

Install bluez-compat

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