Red Hat Bugzilla – Bug 1271581
available bluetooth devices should be listed in connection wizard
Last modified: 2016-11-03 15:18:11 EDT
Description of problem:
when adding both DUN and PAN connections via nm-connection-editor there are no available devices listed in Bluetooth tab. There should be similar menu as in ethernet area.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.add a bluetooth connection via nm-connection-editor (click through APN wizard in DUN case)
2.go to Bluetooth tab
3.fill in device address
no list available, you have to go to control-center and to see mac address of the device (graphical style)
should be visible from nm-connection-editor
Implemented and posted a patch upstream:
(In reply to Jirka Klimes from comment #1)
> Implemented and posted a patch upstream:
I pushed a small fixup to print the BT device's name instead of its MAC address twice. Can you double-check that it builds on git master?
Also pushed dcbw/nma10-editor-bluetooth-rh1271581 that backports it to nma-1-0 branch along with my fixup.
(In reply to Dan Williams from comment #3)
> I pushed a small fixup to print the BT device's name instead of its MAC
> address twice. Can you double-check that it builds on git master?
I have squashed the commit, thanks. But I had to also update the code for getting and verifying the address. It did not work for Bluetooth name which is probably why I didn't use the name before.
> Also pushed dcbw/nma10-editor-bluetooth-rh1271581 that backports it to
> nma-1-0 branch along with my fixup.
Used the branch, squashed my updates and merged.
> Otherwise LGTM!
master: 7444686 editor: populate available Bluetooth devices in Bluetooth page (rh #1271581)
nma-1-0: 90017ad editor: populate available Bluetooth devices in Bluetooth page (rh #1271581)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
I can see connection and mac address of paired device in nm-connection-editor
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.