RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 885818 - cannot connect to shared network via bluetooth
Summary: cannot connect to shared network via bluetooth
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bluez
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: beta
: 7.0
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 886071
TreeView+ depends on / blocked
 
Reported: 2012-12-10 17:29 UTC by Vladimir Benes
Modified: 2014-06-13 12:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 886071 (view as bug list)
Environment:
Last Closed: 2014-06-13 12:35:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vladimir Benes 2012-12-10 17:29:11 UTC 
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 ")
Comment 1 Jirka Klimes 2013-01-08 14:22:06 UTC 
This looks like an issue of bluez. It removed 'Connect' method, but then introduced it again. New bluez build should be made.

Removing commit:
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=9c62de94e5044038bcaae6cd6c0ec783fbee607a

Reverting commit:
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=0624791ea6e917d6c9ecb8e7e6e5a1327199448d

See also:
https://bbs.archlinux.org/viewtopic.php?id=150485
Comment 2 Dan Williams 2013-01-08 17:58:49 UTC 
bluez-4.101 is busted here.  We need some patches, eg from:

https://launchpad.net/ubuntu/quantal/+source/bluez/4.101-0ubuntu4/+files/bluez_4.101-0ubuntu4.debian.tar.gz

the git-XXXX ones are relevant for this specific issue.
Comment 3 Bastien Nocera 2013-01-10 14:21:04 UTC 
Fixed in bluez-4.101-6.fc18
Comment 4 Vladimir Benes 2013-01-18 08:08:18 UTC 
works well now, I can connect to a gsm network via phone and bluetooth.
-> VERIFIED
Comment 5 Ludek Smid 2014-06-13 12:35:31 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.