Bug 892929

Summary:	NetworkManager cannot establish connection via bluez
Product:	[Fedora] Fedora	Reporter:	Jiri Eischmann <eischmann>
Component:	bluez	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	18	CC:	bnocera, dcbw, dwmw2, marcel
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:	2013-02-05 17:03:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Eischmann 2013-01-08 09:41:49 UTC

Description of problem:
Connecting to the Internet via Bluetooth doesn't work in F18 because NetworkManager fails to setup connection via bluez. 

Version-Release number of selected component (if applicable):
Fedora 18 (up-to-date)
NetworkManager 0.9.7.0
bluez 4.101

How reproducible:


Steps to Reproduce:
1. The cell phone is paired using the GUI preferences in GNOME 3.6.
2. The device (cell phone) is marked to use as network device (PAN/NAP)
3. Clicking the device item in the "Broadband connections" submenu in the NetworkManager applet (GNOME).
  
Actual results:
Notification that says NM failed to setup the connection pops up.
This is what messages log says:
Jan  8 04:15:18 dhcp-29-228 NetworkManager[2129]: <warn> Error connecting with bluez: Method "Connect" with signature "s" on interface "org.bluez.Network" doesn't exist
Jan  8 04:15:18 dhcp-29-228 NetworkManager[2129]: <info> (00:1D:FE:7F:EA:74): device state change: config -> failed (reason 'bluetooth-failed') [50 120 44]
Jan  8 04:15:18 dhcp-29-228 NetworkManager[2129]: <warn> Activation (00:1D:FE:7F:EA:74) failed for connection 'Jiri Eischmann's HP Pre3 Network'
Jan  8 04:15:18 dhcp-29-228 NetworkManager[2129]: <info> (00:1D:FE:7F:EA:74): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jan  8 04:15:18 dhcp-29-228 NetworkManager[2129]: <info> (00:1D:FE:7F:EA:74): deactivating device (reason 'none') [0]

Expected results:
NM properly establishes the connection via bluez like in Fedora 17.

Comment 1 Dan Williams 2013-01-08 17:07:25 UTC

Seems to be a change in Bluez 4.101; rebuilding bluez-4.101 for F17 gives me the same result.

Comment 2 Dan Williams 2013-01-08 17:48:44 UTC

This is a bluez bug.  Soemtime between 4.99 and 4.101, the org.bluez.Network.Connect method signature was changed from:

	{ "Connect",		"s",	"s",	connection_connect,
						G_DBUS_METHOD_FLAG_ASYNC },

to:

	{ GDBUS_ASYNC_METHOD("Connect",
			NULL, NULL, connection_connect) },

note the two "NULL" arguments there; that indicates that the D-Bus API no longer expects arguments for connection_connect(), but that function call clearly expects them.  Thus, bluez (perhaps unintentionally) broke D-Bus API.

Comment 3 Dan Williams 2013-01-08 17:56:11 UTC

See https://launchpad.net/ubuntu/quantal/+source/bluez/4.101-0ubuntu4/+files/bluez_4.101-0ubuntu4.debian.tar.gz which already has the suggested patch for above.

Comment 4 Dan Williams 2013-01-08 17:57:49 UTC

(In reply to comment #3)
> See
> https://launchpad.net/ubuntu/quantal/+source/bluez/4.101-0ubuntu4/+files/
> bluez_4.101-0ubuntu4.debian.tar.gz which already has the suggested patch for
> above.

The git-XXXX ones are relevant for this specific issue.

Comment 5 Fedora Update System 2013-01-10 11:02:19 UTC

bluez-4.101-6.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/bluez-4.101-6.fc18

Comment 6 Fedora Update System 2013-01-10 21:27:05 UTC

Package bluez-4.101-6.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bluez-4.101-6.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-0559/bluez-4.101-6.fc18
then log in and leave karma (feedback).

Comment 7 Dan Williams 2013-02-04 18:25:28 UTC

*** Bug 905917 has been marked as a duplicate of this bug. ***

Comment 8 David Woodhouse 2013-02-04 21:38:54 UTC

Yay, with bluez-4.101-6 I can connect. Still can't *disconnect* though...

Comment 9 Fedora Update System 2013-02-05 17:03:48 UTC

bluez-4.101-6.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.