From: Johan Hedberg <johan.hedberg@nokia.com>
To: Achim Bohnet <ach@mpe.mpg.de>
Cc: bluez-devel@lists.sourceforge.net, Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [Bluez-devel] D-BUS fixes for hcid
Date: Wed, 16 Jun 2004 17:18:45 +0300 [thread overview]
Message-ID: <20040616141845.GA8921@kone> (raw)
In-Reply-To: <200406161558.56578.ach@mpe.mpg.de>
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.
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.
It would be nice to know how the D-BUS designers have thought about
this kinds of problems.
> Johan: When 2 xservers are running on vt7 as :0 and vt8 as :1
> respectively. Do the 2 dbus daemons know which one is active?
No idea. But probably not.
Johan
next prev parent reply other threads:[~2004-06-16 14:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 11:27 [Bluez-devel] D-BUS fixes for hcid Johan Hedberg
2004-06-16 11:37 ` Marcel Holtmann
2004-06-16 11:57 ` Johan Hedberg
2004-06-16 12:05 ` Johan Hedberg
2004-06-16 12:18 ` Marcel Holtmann
2004-06-16 12:45 ` Johan Hedberg
2004-06-16 13:06 ` Marcel Holtmann
2004-06-16 13:46 ` Johan Hedberg
2004-06-16 13:53 ` Marcel Holtmann
2004-06-16 13:58 ` Achim Bohnet
2004-06-16 14:18 ` Johan Hedberg [this message]
2004-06-16 23:06 ` Marcel Holtmann
2004-06-17 9:48 ` Johan Hedberg
2004-06-17 12:05 ` Marcel Holtmann
2004-06-17 7:27 ` Sjoerd Simons
2004-06-18 7:30 ` Achim Bohnet
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=20040616141845.GA8921@kone \
--to=johan.hedberg@nokia.com \
--cc=ach@mpe.mpg.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.