I've had this problem on and off for several releases at least since 2008. Machine is an older Dell Inspiron 9400 with a built in Bluetooth, which is provided by the BCM4311 (wifi+bluetooth chip), but which the system sees as if it was part of the USB system:

jsa@poulsbo:~> lsusb Bus 005 Device 024: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth

Synopsis: Resume from suspend will often leave my Bluetooth controller in the powered off state. Not always, but usually, for and suspend over night, or long duration. My BT mouse will therefore not work. Luckily I have a touchpad which is good enough in emergencies. I've found over several years that simply using the keyboard key combo to toggle airplane mode on (killing all radios) and after a 3 seconds toggling it off again would solve this problem. Recent versions of the KDE Configure System Settings (the bluetooth option in KDE System settings, which Opensuse insists on labeling "Configure Desktop" in the kde menu), can determine this situation (bluetooth controller powered off) and will offer to fix it. See: image here: https://paste.opensuse.org/75459363 I want to find out what that KDE settings utility does when "Fix it" is clicked and build it into a systemd resume script, in /usr/lib/systemd/system-sleep/ (which I already have working for other things) But what exactly does the pictured "Fix It" option do? Anyone know: Where is the source for that module? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org