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.

Created attachment 588451 [details]
Backtrace for bluetooth-wizard

Description of problem:
bluetooth-wizard can't pair with another computer.

Version-Release number of selected component (if applicable):
gnome-bluetooth-3.4.0-3.el7.x86_64
gnome-bluetooth-libs-3.4.0-3.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Run bluetooth-wizard
2. Select device (another computer) from list and click "Continue".
3. Check PIN and click "Matches"
  
Actual results:
Devices aren't paired. Pairing timeouts on "Setting up 'xxx' failed."

Expected results:
Devices pairs and wizard successfully finishes.

Additional info:
(bluetooth-wizard:2963): GLib-GIO-WARNING **: Type of return value is incorrect, got `(s)', expected `()'

(bluetooth-wizard:2963): Bluetooth-WARNING **: CreateDevice failed: Timeout was reached

** (bluetooth-wizard:2963): WARNING **: Setting up 'xxx' failed: Timeout was reached

It happens exactly the same in F17, with gnome-bluetooth-3.4.0-2.fc17.x86_64 .
See BZ #819203

This is not RHEL 7.0 Alpha 2 blocker. Changing to Public Beta blocker.

It's already fixed upstream and in Fedora. Somebody will have to resync the package.

Putting as MODIFIED as the fix already happened upstream and in Fedora.

Pairing is fixed.

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.