Bug 442602 - Bluetooth Isn't Enabled At Boot Since Update To Plasma 5.23 Beta
Summary: Bluetooth Isn't Enabled At Boot Since Update To Plasma 5.23 Beta
Status: RESOLVED FIXED
Alias: None
Product: Bluedevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.22.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2021-09-17 14:43 UTC by Alberto Díaz López
Modified: 2021-10-23 15:04 UTC (History)
4 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Díaz López 2021-09-17 14:43:06 UTC 
SUMMARY
I updated yesterday to Plasma 5.22.90, since then, every time I boot up my ultrabook, the Bluetooth is disabled, I need to enable it manually.

STEPS TO REPRODUCE
1. Boot up your machine.
2. Login to Plasma.
3. Try to use any previously connected via Bluetooth device.

OBSERVED RESULT
Bluetooth is disabled, when I had it enabled before the update to Plasma 5.22.90.

EXPECTED RESULT
Bluetooth should be enabled as it was before the update.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.3
(available in About System)
KDE Plasma Version: 5.22.90
KDE Frameworks Version: 5.86
Qt Version: 5.15.2 (+KDE patches)
Comment 1 Nate Graham 2021-09-20 17:26:32 UTC 
Can you go to System Settings > Bluetooth > Configure > and tell me what the value of "On Login:" is?

Also, can you send the output of this command: `grep AutoEnable /etc/bluetooth/main.conf`
Comment 2 Nate Graham 2021-09-20 17:45:50 UTC 
I cannot reproduce the issue with "Remember previous status" selected; if I reboot while Bluetooth is enabled, it is active on login. If I reboot while Bluetooth is disabled, it is disabled on login.
Comment 3 Alberto Díaz López 2021-09-20 20:10:26 UTC 
(In reply to Nate Graham from comment #1)
> Can you go to System Settings > Bluetooth > Configure > and tell me what the
> value of "On Login:" is?
> 
> Also, can you send the output of this command: `grep AutoEnable
> /etc/bluetooth/main.conf`

Sure. The value was setting by default at "Remember previous status" initially. I changed it to "Enabled". Same result.

The output is the following:
# AutoEnable defines option to enable all controllers when they are found.
#AutoEnable=false
Comment 4 David Edmundson 2021-09-20 20:42:26 UTC 
Relevant MR: https://invent.kde.org/plasma/bluedevil/-/merge_requests/44
Comment 5 Nate Graham 2021-09-20 20:57:12 UTC 
Yeah, it's probably a regression from what somehow. Still investigating.
Comment 6 David Edmundson 2021-09-20 21:03:32 UTC 
Should we not be calling saveState in the DeviceMonitor destructor?
Comment 7 Nate Graham 2021-09-20 21:05:12 UTC 
IIRC something crashed when I put saveState() in there, which is why I ended up extracting part of its logic in the destructor instead. I can't quite remember the details though.
Comment 8 Nate Graham 2021-09-20 21:06:15 UTC 
Alberto, do you by any chance have more than one Bluetooth adapter?
Comment 9 Alberto Díaz López 2021-09-21 09:24:34 UTC 
(In reply to Nate Graham from comment #8)
> Alberto, do you by any chance have more than one Bluetooth adapter?

Nope, the Wireless card integrated only. I paired 2 devices, but with Bluetooth only.
Comment 10 Nate Graham 2021-10-23 01:45:06 UTC 
Has this continued in the final release for you? I still can't reproduce it, and we haven't had any other reports of it from other users.
Comment 11 Alberto Díaz López 2021-10-23 11:43:58 UTC 
Fixed on Plasma 5.23 yeah, sorry for not closing this as solved before, it's been a few days since Plasma 5.23 got released and since I got it stable on my distro :).
Comment 12 Nate Graham 2021-10-23 15:04:22 UTC 
Phew! Perhaps it was a packaging issue or something.