Bug 879477 - bluetooth tethering doesn't work
Summary: bluetooth tethering doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Don Zickus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 884334 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-23 06:22 UTC by Samuel Sieb
Modified: 2013-08-27 00:18 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-27 00:18:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
advertise the right interface (554 bytes, patch)
2012-11-23 18:21 UTC, Samuel Sieb 		no flags Details | Diff
View All

Description Samuel Sieb 2012-11-23 06:22:23 UTC 
Bluetooth tethering fails due to the following error:

Nov 22 22:15:47 hostname NetworkManager[688]: <warn> Error connecting with bluez: Method "Connect" with signature "s" on interface "org.bluez.Network" doesn't exist

I checked the upstream bluez repository and that's the right signature, but the bluez version in Fedora doesn't have it.  The web interface doesn't seem to have the annotate or blame options so I can't tell when it was changed.  But NetworkManager is expecting that interface signature.
Comment 1 Samuel Sieb 2012-11-23 18:21:37 UTC 
Created attachment 650594 [details]
advertise the right interface

With this patch, I can successfully tether my phone over bluetooth.
Comment 2 Christopher Beland 2013-02-20 20:28:31 UTC 
*** Bug 884334 has been marked as a duplicate of this bug. ***
Comment 3 Fedora Admin XMLRPC Client 2013-08-26 14:25:30 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 4 Samuel Sieb 2013-08-27 00:18:30 UTC 
I just realized this has been fixed.  At some point there was a new version released which I upgraded to from my version and it's still working.
Note You need to log in before you can comment on or make changes to this bug.