Linux bluetooth development
 help / color / mirror / Atom feed
From: "Claudio Takahasi" <cktakahasi@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcid not working - bluez 3.9
Date: Mon, 2 Apr 2007 09:14:42 -0300	[thread overview]
Message-ID: <e1effdeb0704020514j39031a5cq8a74247e13614434@mail.gmail.com> (raw)
In-Reply-To: <009501c774ef$78f86920$8935c70a@dlh.st.com>

On 4/2/07, Sumeet VERMA <sumeet.verma@st.com> wrote:
> Hi Marcel,
> How would I know that the system bus is up and running? Basically I think
> the problem is the socket system_bus_socket is created in /var/run/dbus
> instead of /usr/local/var/run/dbus.
>
> I tried to configure the dbus-0.61 package with the following string
>
> ./configure --prefix=/usr/local --disable-gtk --disable-selinux
> --with-session-socket-dir=/usr/local/var/run/dbus
> --with-dbus-user=messagebus --with-test-socket-dir=/usr/local/var/run/dbus
> But still it doesn't work.
>
> Any pointers?
>
> Regards,
>
> Sumeet

Hi Sumeet,

Here are my message BUS processes  running:

1001      4725     1  0 08:36 ?        00:00:00 /usr/bin/dbus-daemon
--fork --print-pid 8 --print-address 6 --session
104       6791     1  0 09:07 ?        00:00:00 /usr/bin/dbus-daemon --system

Check the following lock file in order to verify if the system BUS is running:
/var/run/dbus/pid

Remove this file if the system message BUS is not running and execute
"dbus-daemon --system"

BR,
Claudio.
-- 
---------------------------------------------------------
Claudio Takahasi
Instituto Nokia de Tecnologia - INdT


> -----Original Message-----
> From: bluez-users-bounces@lists.sourceforge.net
> [mailto:bluez-users-bounces@lists.sourceforge.net] On Behalf Of Marcel
> Holtmann
> Sent: Saturday, March 31, 2007 7:16 PM
> To: BlueZ users
> Subject: Re: [Bluez-users] hcid not working - bluez 3.9
>
> Hi Sumeet,
>
> > 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
>
> the session bus is not the same as the system bus. You need a running system
> bus for hcid. And normally your distribution ensures that it is setup
> correctly.
>
> Regards
>
> Marcel

-------------------------------------------------------------------------
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

  reply	other threads:[~2007-04-02 12:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30  5:46 [Bluez-users] hcid not working - bluez 3.9 Sumeet Verma
2007-03-31 13:46 ` Marcel Holtmann
2007-04-02  6:23   ` Sumeet VERMA
2007-04-02 12:14     ` Claudio Takahasi [this message]
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=e1effdeb0704020514j39031a5cq8a74247e13614434@mail.gmail.com \
    --to=cktakahasi@gmail.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