** Changed in: bluez (Ubuntu)
Sourcepackagename: bluez-utils = bluez
--
bluez-utils can't start in dbus mode
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
hcid is no longer used in 4.x packages that are in intrepid. I'm
closing up this bug report.
** Changed in: bluez (Ubuntu)
Status: Confirmed = Won't Fix
--
bluez-utils can't start in dbus mode
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a
Same here. The pin helper options no longer work, any attempt at pairing
from my phone is rejected after asking for the password.
Clue: syslog ays:
Mar 29 12:02:17 kiste hcid[12218]: Default passkey agent (:1.16,
/org/bluez/applet) registered
Mar 29 12:02:17 kiste hcid[12218]: Got disconnected
i have the same problem BUT using dbus_pin_helper is NOT enabled:
# PIN helper
pin_helper /usr/bin/pinwrapper;
# D-Bus PIN helper
# dbus_pin_helper;
anyway, after
sudo /etc/init.d/bluez-utils restart
i have the following output:
hcid[8545]: Bluetooth HCI daemon
sdpd[8547]:
well, i can confirm that the message error dissapears after adding the
bluez-hcid.conf file and restart dbus and bluez-utils
this applies if you have
dbus_pin_helper;
enabled on /etc/bluetooth/hcid.conf
but it shows an additional error after this:
org.freedesktop.DBus.Error.ServiceUnknown:
probably i should fill a new bug but, this report has some info about
this.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190960
--
bluez-utils can't start in dbus mode
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
