Created attachment 1160020 [details] screenshot showing Blueman error message Description of problem: After resuming from suspend, bluetooth stops working. The Blueman applet states "Resource Not Ready.." and gives the error message shown in the attached screenshot. Attempting to restart the bluetooth via: sudo modprobe -r btusb; sudo modprobe btusb as mentioned in a previous bug does not fix the problem. The bluetooth device is the Intel 7265 combo wifi/bluetooth card. The wifi still works after resume. The bluetooth resumes working normally after a full restart with no other action required. Version-Release number of selected component (if applicable): Fedora 24 Beta. Problem was not present before upgrading from Fedora 23. How reproducible: Steps to Reproduce: 1. Use a bluetooth mouse (or possibly other BT device, not tested) 2. Suspend the laptop via menu option or closing lid 3. Resume laptop 4. Bluetooth no longer works. Everything else works as expected. Actual results: Bluetooth no longer functions following resume from suspend Expected results: Bluetooth continues to work as normal Additional info: This is my first time manually reporting a bug, please let me know if you need further information or if I didn't follow correct procedure.
Thanks for your report. Can you try with 2.0.4-2 from updates-testing? We saw some issues with dbus/systemd.
https://bodhi.fedoraproject.org/updates/FEDORA-2016-4162d4878a
I downloaded that update with koji and installed (I'm not sure if that's how I'm supposed to do that, I didn't see it in dnf update). Anyway, after a reboot it broke my bluetooth altogether. When I tried to click on the Blueman applet, it said my bluetooth was disabled, and asked me to click to enable it. Doing so did not fix the problem. I'm now getting the same error as before, but fresh after a reboot where it would previously work, no need to suspend/resume to trigger the problem.
Rebooting again did not fix the problem. Downgrading the package back to 2.0.4-1 and rebooting restored BT initial functionally. However, confirmed that bluetooth still stops functioning after suspend/resume.
This is more likely to be a bluez or kernel issue
Hi, What version of Bluez are you running? (yum list bluez) The latest is 5.39. Cheers, Don
Bluez 5.39-1.fc24 x86_64
I am not sure if this is related, but when I return from suspend in gnome, I seem to be magically in "airplane mode" which turns off both bluetooth and wifi.
I'm also not sure if it's relevant, but I'm using Cinnamon instead of Gnome and "airplane mode" doesn't work for me in the first place. All the other media hotkey combinations do, but not that one (though I can still disable wifi through the network manager applet). Also, my wifi still works just fine after returning from suspend, it's just the bluetooth that stops (even though they're both the same card).
(In reply to seeker_moc from comment #9) > it's just the bluetooth that stops (even > though they're both the same card). They maybe on the same card but they are separate devices, the wifi is connected by PCIE slot and the bluetooth part is connected by USB. $ lspci |grep -i intel 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) $ lsusb |grep -i intel Bus 005 Device 002: ID 8087:07dc Intel Corp. FTR my bluetooth prevents suspend when active and has done so since buying it (F22).
Not sure if it means anything, but I show: $ lspci |grep -i intel 04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 48) $ lsusb |grep -i intel Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 003 Device 003: ID 8087:0a2a Intel Corp. I'm not sure which USB device is the Bluetooth, but I can confirm that I have 3 Intel devices both before standby when BT is working, and after resume, when BT no longer works, so it's not like the device disappears altogether. Also, I think I mentioned this before, but this didn't happen on F23, only after I upgraded to F24 Beta.
Try this, run hciconfig and use the correct device id (hci0 ?) to run sudo hciconfig hci0 up also post the outputs here
That fixed the problem. Thanks for your help. If it helps any, prior to standby hciconfig shows: hci0: Type: BR/EDR Bus: USB BD Address: 60:57:18:2B:21:DA ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:31526 acl:1830 sco:0 events:234 errors:0 TX bytes:2576 acl:37 sco:0 commands:148 errors:0 After standby: hci0: Type: BR/EDR Bus: USB BD Address: 60:57:18:2B:21:DA ACL MTU: 1021:5 SCO MTU: 96:6 DOWN RX bytes:1457 acl:0 sco:0 events:175 errors:0 TX bytes:30825 acl:0 sco:0 commands:174 errors:0 Running "sudo hciconfig hci0 up" returns it to the "UP RUNNING" state and restores BT functionality.
Thanks! hciconfig hci0 up fixed it for me, too.
Can you test this build please? http://koji.fedoraproject.org/koji/taskinfo?taskID=14263121
That blueman build does not fix this problem, however, it does fix bug 1338081.
Possibly related to bug 1336297 on F23. Note: that one can be reproduced without suspend/resume, and affects all BT functionality I can test here (mouse and PAN with Android phone).
Problem still present after updating to Bluez 5.40. Hciconfig workaround is still valid.
Fixed here with bug 1336297 (kernel update).
Can confirm, fixed with kernel 4.6.3