Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 430549

Summary: hcid failing to connect to system messagebus
Product: Red Hat Enterprise Linux 5 Reporter: Adam Stokes <astokes>
Component: bluez-utilsAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED NOTABUG QA Contact: desktop-bugs <desktop-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 5.0CC: anton, cmeadors, cww, dfediuck, jarod, tao
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-05 17:52:28 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:
Attachments:
Description Flags
initscript alteration to address this issue.
none
initscript alteration to address this issue. none

Description Adam Stokes 2008-01-28 18:30:47 UTC 
Description of problem:
It seems hcid (the process for bluetooth) depends on the messagebus service. So,
when messagebus service is not available, hcid daemon outputs the error message
to /var/log/messages.

Version-Release number of selected component (if applicable):
bluez-utils 3.7

How reproducible:
100%

Steps to Reproduce:
1. Attempt to shutdown the box with bluetooth services enabled.
2.
3.
  
Actual results:
hcid loses connection to system messagebus service :
hcid[xxxx]: Can't open system message bus connection: Failed to connect to
socket /var/run/dbus/system_bus_socket: Connection refused

Expected results:
Connection is available to messagebus until not needed.

Additional info:
Comment 1 Adam Stokes 2008-01-28 18:30:47 UTC 
Created attachment 293177 [details]
initscript alteration to address this issue.
Comment 2 Adam Stokes 2008-01-28 18:34:42 UTC 
Created attachment 293178 [details]
initscript alteration to address this issue.
Comment 3 RHEL Program Management 2008-01-28 18:35:52 UTC 
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Comment 7 RHEL Program Management 2009-03-26 16:50:35 UTC 
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Comment 8 Jarod Wilson 2009-06-11 20:44:24 UTC 
*** Bug 222699 has been marked as a duplicate of this bug. ***
Comment 15 RHEL Program Management 2010-08-09 18:25:51 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.