Am Montag, 13. Februar 2006 17:52 schrieb Filippo Giunchedi: > On Mon, Feb 13, 2006 at 04:13:40PM +0100, Hendrik Sattler wrote: > > retitle 284745 bluez-utils: fails to work with current dbus > > how this is related to the previous title of the bug? (it was Subject: > needs extra hciconfig hci0 up before rfcomm becomes useable)
The effect is exactly as described before: hci0 is down and must be configured and brought manually. > > severity 284745 important > > can hcid start even without getting on dbus? if yes I would consider > downgrading the severity No, it can't: # /etc/init.d/bluetooth start Starting bluetooth: hcid sdpd rfcomm. # ps ax | grep hci 8320 pts/1 R+ 0:00 grep hci # ps ax | grep rfc 3442 ? S< 0:00 [krfcommd] 8322 pts/1 S+ 0:00 grep rfc It wouldn't make sense anyway. This bug makes hcid useless. > > Hi, > > > > the following happens on running "/etc/init.d/bluetooth start" in syslog: > > Feb 13 16:02:43 localhost hcid[4964]: Bluetooth HCI daemon > > Feb 13 16:02:43 localhost sdpd[4966]: Bluetooth SDP daemon > > Feb 13 16:02:43 localhost hcid[4964]: Can't get system message bus name: > > Connection ":1.2" is not allowed to own the service > > "org.bluez" due to security policies in the configuration file > > Feb 13 16:02:43 localhost hcid[4964]: Unable to get on D-BUS > > > > Thus, hcid is not on dbus and does not recognize any new devices. As the > > consequence, all new devices stay unconfigured. > > I can't reproduce this with unstable (same version of dbus/bluez-utils) do > you have some dbus config files changed? No, I did not change any dbus files. The bluez-utils does not contain any dbus configuration files, anyway. Only bluez-pin provides one. > I guess this happens every time you boot, right? Yes. Or everytime I pull the bluetooth donle out and put it back in. HS
pgpMjaqCZYMts.pgp
Description: PGP signature
