Re: [Bluez-devel] D-BUS fixes for hcid

[sjoerd@spring.luon.net (Sjoerd Simons)]

On Wed, Jun 16, 2004 at 05:18:45PM +0300, Johan Hedberg wrote:
> On Wed, Jun 16, 2004, Achim Bohnet wrote:
> > On debian, dbus-1-utils installs a xsession startup script
> > that checks for use-session-dbus in /etc/X11/Xsession.options
> > Therefore dbus daemon knows the $DISPLAY.

$DISPLAY is indeed in the enviroment when started by the debian x-session. But
dbus doesn't (and shouldn't) care about it. There is nothing that says
that a dbus session bus is connected to an X session (could be console
only session just as well)..

> However, hcid uses the system D-BUS which knows nothing about the
> session (system D-BUS and session D-BUS are run as two separate
> processes). This is an interesting problem, because from a lowlevel
> (BT-stack) standpoint we want to use the system bus, but from a higher
> level (pin-code dialog) standpoint the session bus would be apropriate.

 From both standpoints you'll want to use the system bus. A bluetooth pin query
 is not linked to a specific users session, but to complete system.

 The current sollution is correct imho, when a users wants to answer pin
 queries he/she should have something running that monitors the system bus for
 them.  That something could be a gnome applet/notification icon, a kde
 thingie or a simple command line program that doesn't really matter.

 The activation stuff could be nice for non-interactive pin handlers, but you
 can already use the ``old'' pin_helper option of hcid for that.

  Sjoerd
-- 
Men love to wonder, and that is the seed of science.