+++ This bug was initially created as a clone of Bug #885818 +++ Description of problem: My phone is PAN device. There is an icon in nm-applet but when I click it I get error immediately that connection failed. See attached log from messages. Version-Release number of selected component (if applicable): gnome-bluetooth-3.6.1-1.el7.x86_64 bluez-4.101-5.el7.x86_64 NetworkManager-0.9.7.0-7.git20121004.el7.x86_64 kernel-3.6.0-0.29.el7.x86_64 dbus-1.6.8-3.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.add PAN device via bluetooth wizard and select "Use you mobile phone as a network device (PAN/NAP) 2.connect to network via GNOME Shell's nm-applet Actual results: "Connection Failed: Activation of Network Connection Failed" Error Expected results: successful connection Additional info: Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> Activation (5C:B5:24:8F:C1:D4) starting connection 'Xperia ray Network' Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> (5C:B5:24:8F:C1:D4): device state change: disconnected -> prepare (reason 'none') [30 40 0] Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> Activation (5C:B5:24:8F:C1:D4) Stage 1 of 5 (Device Prepare) scheduled... Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> Activation (5C:B5:24:8F:C1:D4) Stage 1 of 5 (Device Prepare) started... Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> Activation (5C:B5:24:8F:C1:D4) Stage 2 of 5 (Device Configure) scheduled... Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> Activation (5C:B5:24:8F:C1:D4) Stage 1 of 5 (Device Prepare) complete. Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> Activation (5C:B5:24:8F:C1:D4) Stage 2 of 5 (Device Configure) starting... Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> (5C:B5:24:8F:C1:D4): device state change: prepare -> config (reason 'none') [40 50 0] Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> Activation (5C:B5:24:8F:C1:D4) Stage 2 of 5 (Device Configure) complete. Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <warn> Error connecting with bluez: Method "Connect" with signature "s" on interface "org.bluez.Network" doesn't exist Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> (5C:B5:24:8F:C1:D4): device state change: config -> failed (reason 'bluetooth-failed') [50 120 44] Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <warn> Activation (5C:B5:24:8F:C1:D4) failed for connection 'Xperia ray Network' Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> (5C:B5:24:8F:C1:D4): device state change: failed -> disconnected (reason 'none') [120 30 0] Dec 10 19:17:18 dhcp131-78 NetworkManager[1083]: <info> (5C:B5:24:8F:C1:D4): deactivating device (reason 'none') [0] Dec 10 19:17:18 dhcp131-78 dbus-daemon[1028]: dbus[1028]: [system] Rejected send message, 7 matched rules; type="error", sender=":1.7" (uid=0 pid=1119 comm="/usr/sbin/bluetoothd -n ") interface="(unset)" member="(unset)" error name="org.bluez.Error.NotConnected" requested_reply="0" destination=":1.5" (uid=0 pid=1083 comm="/usr/sbin/NetworkManager --no-daemon ") Dec 10 19:17:18 dhcp131-78 dbus[1028]: [system] Rejected send message, 7 matched rules; type="error", sender=":1.7" (uid=0 pid=1119 comm="/usr/sbin/bluetoothd -n ") interface="(unset)" member="(unset)" error name="org.bluez.Error.NotConnected" requested_reply="0" destination=":1.5" (uid=0 pid=1083 comm="/usr/sbin/NetworkManager --no-daemon ")
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.