Bug 2104395
| Summary: | bluetoothd segfault on specific keyboard connection | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Gabriel JEAN <zarock> | ||||
| Component: | bluez | Assignee: | D. Marlin <dmarlin> | ||||
| Status: | CLOSED MIGRATED | QA Contact: | Vilém Maršík <vmarsik> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 9.0 | CC: | darcari, hwkernel-mgr, rvr | ||||
| Target Milestone: | rc | Keywords: | MigratedToJIRA | ||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-09-01 16:38:03 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Gabriel JEAN
2022-07-06 07:01:05 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 Created attachment 1895261 [details]
Unit log between two crashes
I attached the log to this bug.
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 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. 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. Additional information on creating a Jira account to access the migrated issue can be found here: https://access.redhat.com/articles/7032570 |