Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1940713 - bluetoothd errors and coredump [NEEDINFO]
Summary: bluetoothd errors and coredump
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Don Zickus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-19 00:26 UTC by Mads Kiilerich
Modified: 2021-06-16 10:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:
pbrobinson: needinfo? (mads)

Attachments (Terms of Use)
journalctl --follow (8.96 KB, text/plain)
2021-03-19 00:31 UTC, Mads Kiilerich 		no flags Details
View All

Description Mads Kiilerich 2021-03-19 00:26:35 UTC 
When trying to register a noname bluetooth speaker, I encounter some hiccups, and checking the logs I get messages indicating something is very wrong. It seems like the device starts to work after trying a couple of times.

For example, the following keywords suggest severe problems:
new_conn_reply 
dbus_message_iter_append_basic
coredump
battery provider

bluez-5.56-4.fc34.x86_64
pipewire-0.3.24-1.fc34.x86_64

Bonus question: coredump isn't picked up by abrt. Should it? Any idea why it doesn't?
Comment 1 Mads Kiilerich 2021-03-19 00:31:37 UTC 
Created attachment 1764532 [details]
journalctl --follow
Comment 2 Peter Robinson 2021-06-16 10:57:36 UTC 
Please use abrt to report a backtrace with full debug symbols.
Note You need to log in before you can comment on or make changes to this bug.