Bug 456293

Summary:	Bluetooth status isn't restored properly
Product:	[Unmaintained] Bluedevil	Reporter:	popov895 <popov895>
Component:	general	Assignee:	David Rosca <nowrep>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nate, nicolas.fella, plasma-bugs-null, popov895
Priority:	NOR
Version First Reported In:	5.25.2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Bluetooth applet Bluetooth disable log

Description popov895 2022-07-03 19:58:28 UTC

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

Comment 1 popov895 2022-07-04 07:40:30 UTC

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

Comment 2 Nate Graham 2022-07-05 17:53:41 UTC

Does the problem goes away when TLP is disabled?

Comment 3 popov895 2022-07-05 18:53:07 UTC

(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.

Comment 4 popov895 2022-07-06 09:41:17 UTC

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")

Comment 5 Nate Graham 2022-07-06 15:32:04 UTC

Thanks for the info.

Comment 6 popov895 2022-07-06 17:36:04 UTC

Just checked, there is no such problem on a live image, so it looks like it's just me.