Summary: | `AutoEnable=true` in config file causes Bluetooth to get powered off after login into plasma | ||
---|---|---|---|
Product: | [Plasma] Bluedevil | Reporter: | Rocket Aaron <i> |
Component: | general | Assignee: | David Rosca <nowrep> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | flinux, nate, plasma-bugs |
Priority: | NOR | ||
Version: | 5.21.3 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Rocket Aaron
2021-03-20 13:43:14 UTC
We have a user reporting on Solus the same issue https://discuss.getsol.us/d/6604-kde-plasma-disable-bluetooth-after-login/4, can be solved by setting AutoEnable=false but it isn't the greatest solution (In reply to flinux from comment #1) > We have a user reporting on Solus the same issue > https://discuss.getsol.us/d/6604-kde-plasma-disable-bluetooth-after-login/4, > can be solved by setting AutoEnable=false but it isn't the greatest solution Little correction, it did not solve it. But after copying our main.conf from the stateless folder into the /etc path and removing the file again, it seems to be working now At this time, I can't reproduce the reported behavior. Maybe it got fixed somehow? Kernel: linux 5.14.8-arch1-1 BlueZ: 5.61 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Perhaps. Regardless, the way this is handled has changed completely in Plasma 5.23, so the bug would manifest differently, if at all. Let's close this now, and we can see how it works out for you in Plasma 5.23. |