Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] dbus connection failed
Date: Mon, 19 Mar 2007 16:08:47 +0100	[thread overview]
Message-ID: <1174316927.3690.13.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <BAY135-F92F7BB3CB583DBE9AAD04B8710@phx.gbl>

Hi Vincent.

> I am trying to use the DBUS API in my pin exchange script.  I got a DBUS 
> connection error when I execute this line:
> 
>    DBusConnection *conn = dbus_bus_get(DBUS_BUS_SYSTEM, &err);
> 
> When I print out err.message, I got a bunch of non-printable character so I 
> could not quite figure out what the error is.
> 
> However, I took the same DBUS line and put in a stand-alone program and it 
> works fine.
> 
> In my /etc/dbus-1/system.d, there is bluetooh.conf which is identifcal to 
> the config that ships with Bluez.  I even explicitly include bluetooth.conf 
> in my /etc/dbus-1/system.conf file.
> 
> I tried Bluez-Utils 3.7 and 3.9 and with the same results.
> 
> Is there any special trick to connect to DBUS system bus from within Bluez?

take a look at the example code in bluez-utils. I think that
passkey-agent.c is the easiest one.

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-03-19 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 23:50 [Bluez-users] dbus connection failed Vincent Yau
2007-03-19 15:08 ` Marcel Holtmann [this message]

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=1174316927.3690.13.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --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