Bluetooth turned off when resuming after suspend - related to kernel upgrade?
 

As per the thread title. This started after yesterday's -current upgrade when I also upgraded the kernel from 5.10 to 5.12.

Bluetooth can be turned on easily in the blueman applet, so no big deal, even if I would prefer having it turned on automatically.

Anyone with the similar experience and/or an explanation? Is there a way to change the behaviour?

On Slackware-current updated fully up to Fri Jun 11 19:09:59 UTC 2021 the Bluetooth (audio) works fine after the system's suspend or hibernate. Then I assume that overall the Bluetooth driver(s) and service(s) does a fine job themselves.

With the note that I use the PipeWire as audio-server, and this specially because I observed that it works much better with the Bluetooth audio devices, like are (some of) my cheap Chinese speakers and headphones.

I'll take a stab in the dark.

Could be kernel related, could even be firmware related, as the firmware package was updated on the first of the two big update days. If you wanted to experiment you could temporarily roll that back to the previous package (kernel-firmware-20210518_f846292-noarch-1.txz, can be found in the cumulative archive https://slackware.uk/cumulative/slac...slackware64/a/ ) and see if it fixes it... once confirmed/eliminated, move on from there.

Thanks for the suggestions. kernel-firmware can be ruled out, I didn't upgrade that one until after I noticed the behaviour.

But I took a closer look at the changelog (which I should have done earlier, of course) and noticed that blueman was upgraded 7 June. Reverted to blueman-2.1.4 and bluetooth is active after resume.

This doesn't explain why I (and apparently noone else) experience a changed behaviour with blueman-2.2.1.

Could be worth doing a debug level log (blueman-applet --loglevel debug) with 2.1.4 as you suspend and resume. Then doing the same with 2.2.1 and seeing if any useful differences or extra errors are noted. Its basically the first step in their troubleshooting guide before reporting an issue.

Thanks, debug shows no errors but differences. Can't interpret them, but reported the issue with debug log enclosed.

After reporting the issue at github.com/blueman-project/blueman, I've learnt that it's the expected behaviour for Bluetooth to be "off" after resume. What I experienced with blueman-2.1.4 (BT immediately active after resume) is unexpected.

Two ways of changing this:
1) check the "Auto power-on" box in blueman's PowerManager plugin (but that didn't work for me for some reason), or
2) edit /etc/bluetooth/main.conf line 238 > AutoEnable=true (works fine)

Still no clue to what's behind the changed behaviour. I'll mark the thread as solved all the same.