Bug 470736

Summary:	Bluedevil ignores configuration when logging into plasma-wayland
Product:	[Unmaintained] Bluedevil	Reporter:	zylsjsp
Component:	daemon	Assignee:	David Rosca <nowrep>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nicolas.fella, plasma-bugs-null
Priority:	NOR	Keywords:	wayland-only
Version First Reported In:	5.27.5
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=469119
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description zylsjsp 2023-06-07 08:14:10 UTC

SUMMARY
When I log into plasma-wayland through whether sddm or startplasma-wayland, bluetooth power turns off ( I'm tracing this on another tty running bluetoothctl ) no matter what is configured in System Settings/Bluetooth/Configure…/On login. Also, set AutoEnable=true in /etc/bluetooth/main.conf has no effect in bluetooth status.
The issue happens with a high possibility, while there's no such issue with X11 session.

STEPS TO REPRODUCE
1. Start a plasma-wayland session ( logged in )
2. Wait until plasma-shell has been loaded
3. Observe the bluetooth status from bluedevil interface

OBSERVED RESULT
Bluetooth switched to off no matter what is set

EXPECTED RESULT
Bluetooth restored previous status as is set in "Configure…"

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.6-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
I don't know how bluedevil controls bluetoothd, so I guess maybe the configuration file ( if it does exist ) is based on X11, and you could check the configuration file for wayland session ( if it exists and not synchronized with gui options in settings ).

Comment 1 zylsjsp 2023-06-08 07:20:20 UTC

I found a temporary solution as mentioned in Bug 469119. I think bluedevil on Wayland could not write to ~/.config/bluedevilglobalrc properly ( but read works well ). On X11 session, bluedevil can synchroize with configuration file properly.

Comment 2 Nicolas Fella 2023-06-10 16:58:52 UTC


*** This bug has been marked as a duplicate of bug 469119 ***