10647 2007-01-11 20:20:27 +0300 hcid fails without dbus when started thru udev rule 2008-10-06 19:45:07 +0400 1 1 4 Development Sisyphus bluez-utils unstable all Linux CLOSED LATER http://article.gmane.org/gmane.linux.bluez.devel/10601 P2 major --- 1 wrar wrar genix mike mithraen shrek week wrar qa-sisyphus oldest_to_newest 44430 0 wrar 2007-01-11 20:20:29 +0300 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. 45191 1 wrar 2007-02-09 01:16:34 +0300 Temporary patch (retry for 1 minute) is applied in 3.9-alt1. 50095 2 wrar 2007-05-11 00:53:09 +0400 Don't think there will be a better solution. 79247 3 wrar 2008-10-06 19:45:06 +0400 Will be.