From: Sumeet Verma <sumeet.verma@st.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] hcid not working - bluez 3.9
Date: Fri, 30 Mar 2007 05:46:36 +0000 (UTC) [thread overview]
Message-ID: <loom.20070330T074518-49@post.gmane.org> (raw)
Hi
I have been trying to bring up bluez-utils-3.9 and hcid is not working. It
says
[root@dlhl0330 tools]# hcid -n
hcid[29560]: Bluetooth HCI daemon
hcid[29560]: Can't connect to system message bus: Failed to connect to
socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
hcid[29560]: Unable to get on D-Bus
I have looked into the mailing list and followed the mentioned procedure. I
have installed dbus-0.61 and started the system bus by calling dbus-launch
[root@dlhl0330 dbus]# dbus-launch
DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-
BcAG8pbfI2,guid=adea0b46b6c8607cd9bc4162ffe90200';
DBUS_SESSION_BUS_PID=29606;
[root@dlhl0330 dbus]#
I can see the dbus-daemon running when is do ps -e
system_bus_socket is present at the location /var/run/dbus/system_bus_socket
Is there any way I can configure hcid to take the system_bus_socket
from /var/run/dbus instead of /usr/local/var/run/dbus
Please suggest.
Sumeet
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-03-30 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 5:46 Sumeet Verma [this message]
2007-03-31 13:46 ` [Bluez-users] hcid not working - bluez 3.9 Marcel Holtmann
2007-04-02 6:23 ` Sumeet VERMA
2007-04-02 12:14 ` Claudio Takahasi
2007-04-09 8:23 ` Sumeet VERMA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20070330T074518-49@post.gmane.org \
--to=sumeet.verma@st.com \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox