From: Glenn Morris <rgm@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: emacs/lisp/net dbus.el
Date: Wed, 19 Aug 2009 12:51:53 -0400 [thread overview]
Message-ID: <rp7hwz691y.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <nqws50jkwb.fsf@alcatel-lucent.de> (Michael Albinus's message of "Wed, 19 Aug 2009 09:57:40 +0200")
Michael Albinus wrote:
> Could you, please, check whether the D-Bus processes do run already
> before the build? I have embedded the dbus-init-bus calls into a check
> for $DBUS_SESSION_BUS_ADDRESS; this environment variable exists only
> when you have a running D-Bus session bus.
>
> In your case, no additional D-Bus processes shall be launched by
> compiling or loading dbus.el. If so, then it might be due to other
> reasons (maybe a bug which persists longer).
This still happens. It's definitely a new dbus process (not least
because when I logout from my ssh session, it hangs waiting for these
dbus processes to be killed).
This is a RHEL5 system. I have an X session running. This is started as:
ssh-agent execs dbus-launch
dbus-launch execs ~/.xsession
(this seems to create a dbus-daemon process as well)
If I just do
emacs -Q -l dbus
in my X session, no new dbus processes are started.
But if I do:
ssh my-local-host
emacs -Q -l dbus
then two new dbus processes are started:
dbus-launch --autolaunch STRING --binary-syntax --close-stderr
dbus-daemon -fork --print-pid 5 --print-address 7 --session
These persist after Emacs exits, and I have to kill them before I can
logout of my ssh connection.
next prev parent reply other threads:[~2009-08-19 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1MdQLx-0006Su-W6@cvs.savannah.gnu.org>
2009-08-19 3:51 ` emacs/lisp/net dbus.el Glenn Morris
2009-08-19 7:17 ` Michael Albinus
2009-08-19 7:36 ` Glenn Morris
2009-08-19 7:57 ` Michael Albinus
2009-08-19 16:51 ` Glenn Morris [this message]
2009-08-20 13:01 ` Michael Albinus
2009-08-20 18:49 ` Glenn Morris
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=rp7hwz691y.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.