Bug 2149308 - bluetoothctl segfault, LEAdvertisingManager not found
Summary: bluetoothctl segfault, LEAdvertisingManager not found
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gopal krishna tiwari
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-29 14:34 UTC by Petr Sklenar
Modified: 2023-07-01 12:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-01 12:08:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Sklenar 2022-11-29 14:34:23 UTC
Description of problem:
after some time bluetooth stop to work for me:
https://bugzilla.redhat.com/show_bug.cgi?id=2083909

debuging with bluetoothctl ends with segfault

Version-Release number of selected component (if applicable):
bluez-5.65-3.fc37.x86_64

How reproducible:


Steps to Reproduce:
$ bluetoothctl
Agent registered

[bluetooth]# scan on
No default controller available
[bluetooth]# advertise on
LEAdvertisingManager not found
Segmentation fault (core dumped)

Actual results:
segfault

Expected results:


Additional info:

Comment 1 Petr Sklenar 2022-11-29 14:39:55 UTC
fyi after the reboot when BT controller is working:

✔ 15:38 ~ $ bluetoothctl
Agent registered
[CHG] Controller B8:9A:2A:70:E2:24 Pairable: yes
[bluetooth]# advertise on
[CHG] Controller B8:9A:2A:70:E2:24 SupportedInstances: 0x05 (5)
[CHG] Controller B8:9A:2A:70:E2:24 ActiveInstances: 0x01 (1)
Advertising object registered
Tx Power: off
Name: off
Appearance: off
Discoverable: on

Comment 2 Ben Cotton 2023-02-07 15:00:09 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 3 Peter Robinson 2023-07-01 12:08:43 UTC
Please use tools like abrt to file a bug report with a full back trace so there's complete information on the crash


Note You need to log in before you can comment on or make changes to this bug.