Created attachment 871248 [details] bluetooth failure Fresh install of Fedora 20 on an Asus Zenbook UX301LAA. I'm attempting to pare with other devices and I can't even scan. The settings pane for bluetooth has the switch set to 'OFF'. It can be switched to 'ON' but it does not reveal functionality for making the device visible or scanning for nearby devices. bluetoothctl list shows nothing. $ sudo dmidecode -t baseboard |grep -C3 Bluetooth On Board Device 11 Information Type: Other Status: Enabled Description: Bluetooth $ dmesg |grep -i blue [ 4.145782] Bluetooth: Core ver 2.17 [ 4.145796] Bluetooth: HCI device and connection manager initialized [ 4.145802] Bluetooth: HCI socket layer initialized [ 4.145804] Bluetooth: L2CAP socket layer initialized [ 4.145808] Bluetooth: SCO socket layer initialized [ 4.173189] Bluetooth: hci0: read Intel version: 370710018002030d00 [ 4.175735] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq [ 4.316368] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 4.596475] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.596478] Bluetooth: BNEP filters: protocol multicast [ 4.596485] Bluetooth: BNEP socket layer initialized How reproducible: Highly. Steps to Reproduce: 1. open bluetooth settings panel 2. switch bluetooth on Actual results: Nothing happens. Expected results: The "Visibility" switch would activate, and it would be possible to scan for devices. Additional info: I'm happy to provide more information about the
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.