| Summary: | bluetooth turned off after resume but gnome-shell bluetooth status shows it as on | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian G. Anderson <bikehead> |
| Component: | gnome-bluetooth | Assignee: | Bastien Nocera <bnocera> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | beland, bnocera, marc, observer1, redhat-bugzilla, ylavi |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-02-05 22:42:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Brian G. Anderson
2011-10-30 15:43:03 UTC
With the final release of F16, if I suspend my Dell, and resume the bluetooth light is off and I cannot re-enable it again. If I go to the system setting for bluetooth, the toggle switch will be on off and I cannot click it over to on. Only rebooting seems to clear the problem. So I wouldn't characterise this as a low impact problem any more. Fortunately, I found a work around where if I turn off bluetooth first and then suspend, I can resume and re-enable it without a hitch. I've added a script in /etc/pm/sleep.d that runs "rfkill block bluetooth" and now I can resume and get a working bluetooth mouse back. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Recreated issue on fedora 18. Yaniv I'm having the same issue in Fedora 18 The rfkill command doesn't help, is the only thing to run? The difference is that i'm using a bluetooth speaker. The only way to make bluetooth work again is disconnecting the usb dongle and reconnect it and then reconnect the speakers. I'm having the same issue in Fedora 19.
A simple hack "/usr/lib/systemd/system-sleep/bluetooth_wooden_hammer.sh" solves the issue:
--------------------------
#!/bin/bash
case "$1" in
pre)
rmmod btusb
;;
post)
modprobe btusb
;;
esac
--------------------------
Bluetooth Device:
Bus 001 Device 022: ID 8087:07da Intel Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x8087 Intel Corp.
idProduct 0x07da
bcdDevice 78.69
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Kernel is 3.11.2-201.fc19.x86_64
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |