SUMMARY I've set `AutoEnable=true` in bluez's config file (/etc/bluetooth/main.conf), and it works in sddm, I'm able to access my bluetooth keyboard in sddm. But as soon as I login into plasma, bluetooth got powered off, all connected devices disconnected, and bluetooth icon in system tray turns grey. It works again after click "enable bluetooth" manually in system tray's popup. If I force uninstall bluedevil regardless of dependency, bluetooth works fine after login into plasma. STEPS TO REPRODUCE 1. set `AutoEnable=true` in bluez's main config file (/etc/bluetooth/main.conf) 2. connect any bluetooth input device, such as mouse or keyboard 3. restart computer, try to use previously connected device in sddm 4. login into plasma, and try to use the same device OBSERVED RESULT Input device works in sddm, but got disconnected as soon as login into plasma. And bluetooth got powered off. EXPECTED RESULT Bluetooth device should work both in sddm and plasma. SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux 5.11.7-arch1-1 (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
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.