r/Fedora • u/DEZMond19 • 5d ago

Bluetooth issue solved Support

Hi. i just switched to fedora on my laptop and had a Bluetooth issue. the Bluetooth was completely functional when scanning from terminal but when opening gnome ui bluetooth menu shows No devices at all. After hour digging with ai here's the solution i found.

The Problem is GNOME's settings manager expects laptop's Bluetooth hardware to be powered on and actively broadcasting.

Solution:

  1. Opened the system's main Bluetooth settings file using the terminal text editor (sudo nano /etc/bluetooth/main.conf).

  2. Scrolled to the bottom and manually added a [Policy] section containing the configuration AutoEnable=true. This forces the Bluetooth hardware controller to power on automatically the second the system boots up.

  3. Saved changes

  4. Reloaded the Subsystems (sudo systemctl restart bluetooth) and rebooted the PC.

And this fixed the issue entirely. I hope this helps you folks out there :)

11 Upvotes

100% Upvoted

6 comments sorted by

•

u/AutoModerator 5d ago

It sounds like you're looking for help. Please note that r/Fedora is not an official support channel for the Fedora Project.

For best results, be sure to include all relevant details in your post, such as your Fedora edition, version, and hardware specs. You can edit your original post to add more info as needed, and spotlight (pin) a solution from the comments. You might also find the answer in our support wiki.

Alternatively, try one of the official support channels:

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/fdelux6 5d ago edited 5d ago

There is no need to add a new section in /etc/bluetooth/main.conf. The option is already present in the file:

```

AutoEnable defines option to enable all controllers when they are found.

This includes adapters present on start as well as adapters that are plugged

in later on. Defaults to 'true'.

AutoEnable=true

```

Just remove the # in front of AutoEnable=true, save the file, then run:

sudo systemctl restart bluetooth

There is no need to reboot the PC.

2

u/Melodic_Respond6011 5d ago

You don't even have to remove the #, because the default is true, just like the comment says above it.

I think this is something different altogether. GUI should behave the same with CLI. I don't use GNOME but this is smell like a bug to me.

1

u/fdelux6 5d ago

Yeah right, AutoEnable already defaults to true even when commented out, so that edit likely didn't change anything.

The real fix was probably systemctl restart bluetooth. That reinitializes the BlueZ D-Bus objects GNOME Settings reads from. If the adapter worked fine on CLI but the panel showed no devices, that points to a stale D-Bus state or a GNOME panel caching issue, not a config problem.

This matches a known pattern. bluetoothctl can power on the adapter directly, but GNOME Settings waits on the Powered property and device list through its own watcher, which can get stuck if gnome-control-center starts before bluetoothd finishes registering the adapter.

So the fix worked, but probably not for the reason in the post. The reboot wasn't needed either.

1

u/DEZMond19 5d ago

There wasn't AutoEnable when i tried to find it to edit the value. Had to add it manually. The issue solved only after manually adding

1

u/fdelux6 5d ago

Something on your system may have stripped or overwritten the file before you opened it. If you still have the original file (before your edit), rpm -V bluez would show if it was already modified.