https://bugs.kde.org/show_bug.cgi?id=470736
Bug ID: 470736
Summary: Bluedevil ignores configuration when logging into
plasma-wayland
Classification: Plasma
Product: Bluedevil
Version: 5.27.5
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: daemon
Assignee: now...@gmail.com
Reporter: zyls...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: ---
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 ).
--
You are receiving this mail because:
You are watching all bug changes.
