Created attachment 150372 [details] Bluetooth applet SUMMARY After disconnecting Bluetooth and rebooting it becomes not completely disabled. See the attachment for a better understanding of the issue. I noticed that after disabling Bluetooth, the content of ~/.config/bluedevilglobalrc is as follows: > [Adapters] > F8:63:3F:A2:EF:F8_powered=true > > [Devices] > connectedDevices= SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220701 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.6-1-default (64-bit) Graphics Platform: X11
Also rfkill shows different status of Bluetooth before and after reboot. Before reboot: > $ rfkill list bluetooth > 0: tpacpi_bluetooth_sw: Bluetooth > Soft blocked: yes > Hard blocked: no After reboot: > $ rfkill list bluetooth > 0: tpacpi_bluetooth_sw: Bluetooth > Soft blocked: no > Hard blocked: no > 2: hci0: Bluetooth > Soft blocked: no > Hard blocked: no
Does the problem goes away when TLP is disabled?
(In reply to Nate Graham from comment #2) > Does the problem goes away when TLP is disabled? No. Also adding `bluetoothBlocked=true` to ~/.config/bluedevilglobalrc has no effect.
Created attachment 150435 [details] Bluetooth disable log Looks suspicious: > localhost.localdomain dbus-daemon[677]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.54" (uid=1000 pid=1552 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.61" (uid=0 pid=1729 comm="/usr/libexec/bluetooth/bluetoothd")
Thanks for the info.
Just checked, there is no such problem on a live image, so it looks like it's just me.