Bug 465984 - Bluetooth service not active on boot even if enabled
Summary: Bluetooth service not active on boot even if enabled
Status: RESOLVED UPSTREAM
Alias: None
Product: Bluedevil
Classification: Unmaintained
Component: daemon (other bugs)
Version First Reported In: 5.27.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-18 07:26 UTC by Andrea Calzavacca
Modified: 2023-02-22 02:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea Calzavacca 2023-02-18 07:26:14 UTC
SUMMARY
after updating to 5.27 on arch when the computer boots bluetooth.service fails even if resulting active and have to be enabled manually from plasma settings panel


STEPS TO REPRODUCE
1. enable bluetooth.service
2. reboot

OBSERVED RESULT
here the state of bluetooth.service on boot
''systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sat 2023-02-18 08:12:38 CET; 2min 35s ago
       Docs: man:bluetoothd(8)
   Main PID: 511 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38064)
     Memory: 3.7M
        CPU: 90ms
     CGroup: /system.slice/bluetooth.service
             └─511 /usr/lib/bluetooth/bluetoothd

feb 18 08:14:57 graphene bluetoothd[511]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aptx_ll_dupl>
feb 18 08:14:57 graphene bluetoothd[511]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aptx_ll_dupl>
feb 18 08:14:57 graphene bluetoothd[511]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/faststream
feb 18 08:14:57 graphene bluetoothd[511]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/faststream_d>
feb 18 08:14:57 graphene bluetoothd[511]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/opus_05
feb 18 08:14:57 graphene bluetoothd[511]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/opus_05
feb 18 08:14:57 graphene bluetoothd[511]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/opus_05_duplex
feb 18 08:14:57 graphene bluetoothd[511]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/opus_05_dupl>
feb 18 08:14:58 graphene bluetoothd[511]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monito>
feb 18 08:15:00 graphene bluetoothd[511]: Failed to set mode: Authentication Failed (0x05)
lines 1-22/22 (END)
''

EXPECTED RESULT
bluetooth service start fine as before 5.27

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux 6.1.12-arch1-1 (64-bit)
(available in About System)
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-02-22 02:25:12 UTC
KDE code isn't involved here; you'll need to follow up with the Bluetooth devs. I suspect that this was caused by another change that just so happened to arrive at the same time as the Plasma 5.27 update.