This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2104395 - bluetoothd segfault on specific keyboard connection
Summary: bluetoothd segfault on specific keyboard connection
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: bluez
Version: 9.0
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: D. Marlin
QA Contact: Vilém Maršík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-06 07:01 UTC by Gabriel JEAN
Modified: 2023-09-28 17:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-01 16:38:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
Unit log between two crashes (81.39 KB, text/plain)
2022-07-07 17:18 UTC, Gabriel JEAN 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1930 0 None Migrated None 2023-09-01 16:33:42 UTC
Red Hat Issue Tracker RHELPLAN-127057 0 None None None 2022-07-06 07:18:00 UTC

Description Gabriel JEAN 2022-07-06 07:01:05 UTC 
Description of problem:

After a successful pairing of a Lenovo TrackPoint Keyboard II via Gnome settings, connection will be made, and bluetoothd will enter a segfault loop. Whenever the keyboard reconnects, the segfault appears.

Version-Release number of selected component (if applicable):

rpm -aqv | grep blue
bluez-libs-5.56-8.el9.x86_64
bluez-5.56-8.el9.x86_64
bluez-obexd-5.56-8.el9.x86_64
gnome-bluetooth-libs-3.34.5-3.el9.x86_64
gnome-bluetooth-3.34.5-3.el9.x86_64
NetworkManager-bluetooth-1.36.0-5.el9_0.x86_64


How reproducible:

Reproducible with this keyboard and el9, tried with Asus BT-500 dongle (rtl) and Intel bt, same.

Steps to Reproduce:
1. Pair a TrackPoint keyboard II
2. Connect it.

Actual results:

Will occurs on each reconnection after bluetoothd recovery (same address):

[  190.524243] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0014/input/input81
[  190.524569] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0014/input/input82
[  190.524666] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0014/input/input84
[  190.524773] hid-generic 0005:17EF:60E1.0014: input,hidraw8: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 50:eb:71:97:dd:0c
[  190.525263] bluetoothd[4568]: segfault at 59 ip 000055e50ff38583 sp 00007ffed3c5b930 error 6 in bluetoothd[55e50ff01000+ab000]
[  190.525271] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07


Expected results:

Keyboard should just work :)

Additional info:

Can't reproduce on Fedora, can reproduce on CentOS 9 Stream.

No issue with other kind of devices I have at hand (headset, mice etc...)
Comment 1 gopal krishna tiwari 2022-07-06 14:11:16 UTC 
Can you please share the bluez logs once the issue reproduce ?

How to ? 

~~~

enable debugging by adding a -d after

ExecStart=/usr/libexec/bluetooth/bluetoothd

in /usr/lib/systemd/system/bluetooth.service

Save, then:

$ systemctl daemon-reload
$ systemctl restart bluetooth


Now you get your information in /var/log/syslog
or 
journalctl --unit=bluetooth -f

~~~~

Thanks
Gopal
Comment 2 Gabriel JEAN 2022-07-07 17:18:19 UTC 
Created attachment 1895261 [details]
Unit log between two crashes

I attached the log to this bug.
Comment 4 Doug Ledford 2023-08-31 15:50:59 UTC 
This bug is scheduled for migration to Jira.  When that happens, this bugzilla issue will be permanently closed with the status MIGRATED and all future interaction on this issue will need to happen in the Jira issue.  The new issue will be part of the RHEL project (a project for Jira only issues, which will sync once, then close the bugzilla issue and all future updates will happen in Jira), not part of the RHELPLAN project (which is part of the automated bugzilla->Jira mirroring and which allows ongoing updates to the bugzilla bug and syncs those updates over to Jira).

For making sure you have access to Jira in order to continue accessing this issue, follow one of the appropriate knowledge base articles:

KB0016394 - https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016394
KB0016694 - https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016694
KB0016774 - https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016774

For general issues with Jira, open a ticket with rh-issues
Comment 5 RHEL Program Management 2023-09-01 16:33:03 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6 RHEL Program Management 2023-09-01 16:38:03 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.

Users watching this BZ may not be automatically added to the Jira ticket.  Be sure to add yourself to the Watchers field in the Jira issue if you desire to continue following this issue.
Comment 7 Doug Ledford 2023-09-08 17:30:47 UTC 
Additional information on creating a Jira account to access the migrated issue can be found here:

https://access.redhat.com/articles/7032570
Note You need to log in before you can comment on or make changes to this bug.