https://bugs.kde.org/show_bug.cgi?id=488652
sulf...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |CONFIRMED
Ever confirmed|0 |1
--- Comment #8 from sulf...@gmail.com ---
Looking at bug 487063, I'd say the main suspect is the kernel line (6.9), not
the distribution (which is the only distribution at hand).
Before reboot:
> rfkill --output-all list 6
6: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
> bluetoothctl show
Controller *** (public)
Manufacturer: 0x001d (29)
Version: 0x08 (8)
Name: BlueZ 5.76
Alias: ***
Class: 0x00000000 (0)
Powered: no
PowerState: off
Discoverable: no
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
...
After reboot:
> rfkill --output-all list 0
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
> bluetoothctl show
Controller *** (public)
Manufacturer: 0x001d (29)
Version: 0x08 (8)
Name: BlueZ 5.76
Alias: ***
Class: 0x007c0000 (8126464)
Powered: yes
PowerState: on
Discoverable: no
...
Configuration says Bluetooth should be inactive at login. If I suspend and then
resume, Bluetooth remains inactive, as configured.
--
You are receiving this mail because:
You are watching all bug changes.
