FS#74400 - [bluez] default config should set "AutoEnable=true" by default

Attached to Project: Arch Linux
Opened by Reik Keutterling (Spielkind) - Friday, 08 April 2022, 09:56 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 11 April 2022, 18:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
There were some changes/fixes in GNOME 42 which changed the behavior of the power state of the bluetooth controller.
See gnome bug report for details.

These changes suggest to change the default configuration of bluetooth.

Additional info:
* package version(s)
bluez 5.64-2
* config and/or log files etc.
/etc/bluetooth/main.conf
* link to upstream bug report, if any
https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/110

Steps to reproduce:
Update to GNOME42 suspend or reboot -> bluetooth controller is powered off.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 11 April 2022, 18:53 GMT
Reason for closing:  Upstream
Additional comments about closing:  We'll see...
Comment by Andreas Radke (AndyRTR) - Friday, 08 April 2022, 15:07 GMT
Arch always ships upstream default configuration. It's all documented here:

https://wiki.archlinux.org/title/Bluetooth#Auto_power-on_after_boot/resume
Comment by Reik Keutterling (Spielkind) - Friday, 08 April 2022, 15:15 GMT
Hm, I thought limited changes to upstream configurations are made.
But just read the principals (https://wiki.archlinux.org/title/Arch_Linux) and seems that this change wouldn't be a "distribution-specific issue".

So I guess you are right.
Comment by Andreas Radke (AndyRTR) - Monday, 11 April 2022, 18:53 GMT
https://github.com/bluez/bluez/issues/328

Loading...