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 I want to add my bluetooth headset I get segfault all the time
Version-Release number of selected component (if applicable):
gnome-bluetooth-3.6.0-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.start /usr/bin/bluetooth-wizard
2.add headphone device
Actual results:
segfault
Expected results:
device successfully added
Additional info:
backtrace attached
hmm strange.. after I failed to find previously written backtrace I cannot reproduce anymore.. closing now.. will reopen if it occurs again (suspend/rfkill, etc)
-> CLOSED
I've finally managed to reproduce.. it's crashing again now. I suspect something like this:
0. suspend/resume (maybe several times)
1. suspend
2. dock
3. resume
4. add bluetooth device via wizard
I have the same problem. No need to suspend/resume, I don't do it. My reproducer:
1. Start bluetooth-wizard
2. Wait a sec until bluetooth device is found
3. Click to the device you want connect to
Actual result:
Segmentation fault
Expected result:
Go next in wizard..
Few more information:
The situation with segfault request to click to searched up bluetooth device before the wizard has all information - there is only MAC address, no device name yet. Clicking on that device causes segfault as reported above.
If I wait until the name of device is shown, everything goes fine.
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.