Bug 553519

Summary: bluetooth service fails with 'Unable to get on D-Bus'
Product: [Fedora] Fedora Reporter: sudheer <sudheer.divakaran>
Component: bluezAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 12CC: bnocera, dwmw2, marcel, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-04 00:43:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description sudheer 2010-01-08 04:46:22 UTC
Description of problem:

In my machine, the bluetooth service doesn't start. When I run 'bluetoothd -nd', it terminates with the error 'Unable to get on D-Bus'. The output of 'bluetoothd -nd' is as follows

bluetoothd[4147]: Bluetooth daemon 4.57
bluetoothd[4147]: Enabling debug information
bluetoothd[4147]: parsing main.conf
bluetoothd[4147]: discovto=0
bluetoothd[4147]: pairto=0
bluetoothd[4147]: pageto=8192
bluetoothd[4147]: name=%h-%d
bluetoothd[4147]: class=0x000100
bluetoothd[4147]: discov_interval=0
bluetoothd[4147]: Key file does not have key 'DeviceID'
bluetoothd[4147]: Unable to get on D-Bus





Version-Release number of selected component (if applicable): bluez- 4.57 (bluez-4.57-2.fc12.i686.rpm)

How reproducible:always

Steps to Reproduce:
1.service bluetooth start
    OR
2.bluetoothd -n -d

Comment 1 Bug Zapper 2010-11-04 01:34:47 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 2 Bug Zapper 2010-12-04 00:43:14 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.