Description of problem: Bluetooth IP configuration failed, unable to set up bluetooth Version-Release number of selected component (if applicable): Fedora 20, bluez 5 How reproducible: Turning on the bluetooth through network manager, automatically falls back to off Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Log lines Jan 12 00:09:38 localhost systemd-udevd[8125]: renamed network interface bnep0 to enp0s26u1u4 Jan 12 00:09:38 localhost NetworkManager: Internet Systems Consortium DHCP Client 4.2.5 Jan 12 00:09:38 localhost NetworkManager: Copyright 2004-2013 Internet Systems Consortium. Jan 12 00:09:38 localhost NetworkManager: All rights reserved. Jan 12 00:09:38 localhost NetworkManager: For info, please visit https://www.isc.org/software/dhcp/ Jan 12 00:09:38 localhost NetworkManager: Error getting hardware address for "bnep0": No such device Jan 12 00:09:38 localhost NetworkManager: This version of ISC DHCP is based on the release available Jan 12 00:09:38 localhost NetworkManager: on ftp.isc.org. Features have been added and other changes Jan 12 00:09:38 localhost NetworkManager: have been made to the base software release in order to make Jan 12 00:09:38 localhost NetworkManager: it work better with this distribution. Jan 12 00:09:38 localhost NetworkManager: Please report for this software via the Red Hat Bugzilla site: Jan 12 00:09:38 localhost NetworkManager: http://bugzilla.redhat.com Jan 12 00:09:38 localhost NetworkManager: exiting.
Created attachment 848823 [details] network manager screen shot
https://ask.fedoraproject.org/en/question/38232/f20-bluetooth-startup-error-and-unable-to-enable-once-i-login/ More information on this
systemctl status bluetooth.service bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled) Active: active (running) since Wed 2014-01-29 10:41:48 PST; 5 days ago Docs: man:bluetoothd(8) Main PID: 473 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─473 /usr/libexec/bluetooth/bluetoothd Feb 02 22:58:55 localhost bluetoothd[473]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink Feb 03 01:15:12 localhost bluetoothd[473]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/A2DPSource Feb 03 01:15:12 localhost bluetoothd[473]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/A2DPSink Feb 03 01:15:12 localhost bluetoothd[473]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource Feb 03 01:15:12 localhost bluetoothd[473]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink Feb 03 10:28:18 localhost bluetoothd[473]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/A2DPSource Feb 03 10:28:18 localhost bluetoothd[473]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/A2DPSink Feb 03 10:28:18 localhost bluetoothd[473]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource Feb 03 10:28:18 localhost bluetoothd[473]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink Feb 03 15:27:41 localhost bluetoothd[473]: connect error: Host is down (112)
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.