Timeline for bluetooth does not work after resuming computer from suspend; modprobing bluetooth modules does not help
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2019 at 12:08 | history | edited | Rui F Ribeiro | CC BY-SA 4.0 | deleted 13 characters in body |
| Mar 3, 2019 at 9:48 | comment | added | Alex Jones | Note: I don't face this problem on the same laptop anymore. Probably fixed at 'kernel level' | |
| Mar 2, 2019 at 22:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 28, 2018 at 20:36 | answer | added | Santiago | timeline score: 1 | |
| Jan 17, 2017 at 8:54 | comment | added | Alex Jones | @Jeremy31 right now I have resume my laptop from suspend, I checked rfkill list all and show that bluetooth is not hard and soft blocked | |
| Jan 12, 2017 at 22:58 | comment | added | Jeremy31 | Check rfkill list all as it looks like bluetooth may have been disabled | |
| Oct 3, 2016 at 6:30 | comment | added | Alex Jones | @MartinNyolt here is the link to some outputs. systemctl, dmesg,bluetoothctl don't give any kind of error, I checked all of them when my bluetooth wasn't starting | |
| Sep 21, 2016 at 9:08 | comment | added | Martin Nyolt | Sorry, then I misunderstood you saying that restarting the service failed - I thought you meant the actual systemctl restart failed. But the essence of my previous comment is the same: without more information from you, we cannot do much. What is the output of bluetoothctl, for instance? Is there any error message when turning on the power with bluetoothctl? Does dmesg say anything? Please give more diagnostic. | |
| Sep 21, 2016 at 7:17 | comment | added | Alex Jones | @MartinNyolt systemd wouldn't show error, according to systemd there is nothing wrong with bluetooth service but still bluetooth won't work | |
| Sep 20, 2016 at 12:49 | comment | added | Martin Nyolt | At least, systemd tells you some reason why the service could not be started, e.g. the exit code. This should also be in the journal - the relevant except would be helpful. | |
| Sep 20, 2016 at 9:10 | history | asked | Alex Jones | CC BY-SA 3.0 |