Linux bluetooth development
 help / color / mirror / Atom feed
From: "Kelvin Xu" <kyoxu@hotmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] pin code
Date: Mon, 05 Mar 2007 01:28:17 +0800	[thread overview]
Message-ID: <BAY117-F192F81B0DBADE11579F926BF850@phx.gbl> (raw)
In-Reply-To: <1173029811.5752.11.camel@aeonflux.holtmann.net>

Hi,

Thanks for the help.

How do i double check if my system bus is running andwhether the security 
settings are correct?

Regards,
Kelvin


>From: Marcel Holtmann <marcel@holtmann.org>
>Reply-To: BlueZ users <bluez-users@lists.sourceforge.net>
>To: BlueZ users <bluez-users@lists.sourceforge.net>
>Subject: Re: [Bluez-users] pin code
>Date: Sun, 04 Mar 2007 18:36:50 +0100
>
>Hi Kelvin,
>
> > i am faced with the sam problems as KS H. I have also cross compiled 
>dBus
> > and Bluez Util for ARM using Scratchbox.
> > I followed the similar steps provided by Prabhu. However, I do not have 
>the
> > message.pid entry in /var/run but have an additional "pid" entry in
> > /var/run/dbus.
> >
> > And when i try to execute hcid i received the following error:
> > # hcid -n -f /etc/bluetooth/hcid.conf
> > hcid[790]: Bluetooth HCI daemon
> > hcid[790]: Can't open system message bus connection: Failed to connect 
>to
> > socket /var/run/dbus/system_bus_socket: Connection refused
> > hcid[790]: Unable to get on D-Bus
> >
> > Please advice. Thank you
>
>this can mean two things. Either the system bus is not running or the
>security settings for hcid to claim the org.bluez namespace are not
>correctly set.
>
>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

_________________________________________________________________
Get an advanced look at the new version of Windows Live Messenger. 
http://get.live.com/messenger/overview


-------------------------------------------------------------------------
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-03-04 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 11:43 [Bluez-users] Re: pin code Kelvin Xu
2007-03-04 17:36 ` [Bluez-users] " Marcel Holtmann
2007-03-04 17:28   ` Kelvin Xu [this message]
2007-03-09  9:27   ` Kelvin Xu
  -- strict thread matches above, loose matches on Subject: below --
2007-01-23 13:46 KS H
2007-01-26  5:45 ` Prabhu nath
2007-12-17  9:10   ` 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=BAY117-F192F81B0DBADE11579F926BF850@phx.gbl \
    --to=kyoxu@hotmail.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