LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-09-2021, 04:05 AM   #1
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 442

Rep: Reputation: 328Reputation: 328Reputation: 328Reputation: 328
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?
 
Old Today, 03:45 AM   #2
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 1,367

Rep: Reputation: 1136Reputation: 1136Reputation: 1136Reputation: 1136Reputation: 1136Reputation: 1136Reputation: 1136Reputation: 1136Reputation: 1136
Quote:
Originally Posted by kgha View Post
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.

Last edited by LuckyCyborg; Today at 04:35 AM.
 
Old Today, 07:32 AM   #3
avian
Member
 
Registered: Aug 2014
Posts: 69

Rep: Reputation: Disabled
Quote:
Originally Posted by kgha View Post
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?
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.
 
1 members found this post helpful.
Old Today, 10:52 AM   #4
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 442

Original Poster
Rep: Reputation: 328Reputation: 328Reputation: 328Reputation: 328
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.
 
Old Today, 11:29 AM   #5
avian
Member
 
Registered: Aug 2014
Posts: 69

Rep: Reputation: Disabled
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.
 
1 members found this post helpful.
Old Today, 12:34 PM   #6
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 442

Original Poster
Rep: Reputation: 328Reputation: 328Reputation: 328Reputation: 328
Thanks, debug shows no errors but differences. Can't interpret them, but reported the issue with debug log enclosed.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Logitech MX Ergo trackball - has RF & bluetooth connectivity - can BT be turned off? cilbuper Linux - Hardware 1 08-22-2018 11:24 PM
[SOLVED] Screen remains off after resuming from suspend to ram after upgrading kernel. Arcosanti Slackware 6 11-12-2015 01:50 PM
Keyboard Doesn't Work After Resuming from Suspend to Ram beartooth91 Slackware 11 03-05-2009 01:18 PM
how to execute a command automatically after resuming from suspend to RAM? bjharker Linux - General 5 11-24-2008 08:00 AM
monitor does not turn on after resuming from suspend nappaji Puppy 2 08-24-2006 08:19 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:05 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration