Bug 10647 - hcid fails without dbus when started thru udev rule
Summary: hcid fails without dbus when started thru udev rule
Status: CLOSED LATER
Alias: None
Product: Sisyphus
Classification: Development
Component: bluez-utils (show other bugs)
Version: unstable
Hardware: all Linux
: P2 major
Assignee: Andrey Rahmatullin
QA Contact: qa-sisyphus
URL: http://article.gmane.org/gmane.linux....
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 20:20 MSK by Andrey Rahmatullin
Modified: 2008-10-06 19:45 MSD (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Rahmatullin 2007-01-11 20:20:29 MSK 
In our default configuration hcid is started when udev finds BT device, through 
/etc/udev/rules.d/80-bluetooth.rules. This means that during system boot it is 
started just after udev, before starting of messagebus. But hcid fails to start 
if it doesn't find messagebus.

The only solution for this problem is suggested in bug Url: hcid should start 
normally and repeatedly try to connect to messagebus.
Comment 1 Andrey Rahmatullin 2007-02-09 01:16:34 MSK 
Temporary patch (retry for 1 minute) is applied in 3.9-alt1.
Comment 2 Andrey Rahmatullin 2007-05-11 00:53:09 MSD 
Don't think there will be a better solution.
Comment 3 Andrey Rahmatullin 2008-10-06 19:45:06 MSD 
Will be.