Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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):
network-manager-applet-1.0.6-2.el7.x86_64
How reproducible:
always
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
Actual results:
no list available, you have to go to control-center and to see mac address of the device (graphical style)
Expected results:
should be visible from nm-connection-editor
Additional info:
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.
Otherwise LGTM!
(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)
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.
https://rhn.redhat.com/errata/RHSA-2016-2581.html