Bug 1824299

Summary: No default controller available in bluetoothctl.
Product: [Fedora] Fedora Reporter: Clayton Workman <efrost>
Component: IoTAssignee: Peter Robinson <pbrobinson>
Status: CLOSED EOL QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 32   
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 17:37:55 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:

Description Clayton Workman 2020-04-15 18:42:44 UTC
Description of problem:
bluetoothctl command "show" returns "No default controller available" on Raspberry Pi 3b.

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

How reproducible:
3 reboots with same result

Steps to Reproduce:
1. systemctl start bluetooth
2. bluetoothctl
3. show

Actual results:
"No default controller available"

Expected results:
Information returned about bluetooth controller.

Additional info:
This is on a Raspberry Pi3b using Fedora-IoT-32-20200414.0

Comment 1 Fedora Program Management 2021-04-29 17:01:20 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-05-25 17:37:55 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.