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) > severity 284745 important can hcid start even without getting on dbus? if yes I would consider downgrading the severity > 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? I guess this happens every time you boot, right? filippo -- Filippo Giunchedi PGP key: 0x6B79D401 random quote follows: It's not that I'm afraid to die, I just don't want to be there when it happens. -- Woody Allen
signature.asc
Description: Digital signature
