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.
Seems to be a change in Bluez 4.101; rebuilding bluez-4.101 for F17 gives me the same result.
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.
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.
(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.
bluez-4.101-6.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/bluez-4.101-6.fc18
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).
*** Bug 905917 has been marked as a duplicate of this bug. ***
Yay, with bluez-4.101-6 I can connect. Still can't *disconnect* though...
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.