From: Paul Eggert <eggert@cs.ucla.edu>
To: 14474@debbugs.gnu.org
Subject: bug#14474: 24.3.50; Zombie subprocesses (again)
Date: Sun, 26 May 2013 10:37:52 -0700 [thread overview]
Message-ID: <51A24870.8020909@cs.ucla.edu> (raw)
In-Reply-To: <87ppwevddb.fsf@web.de>
A workaround, for me at least, is to propagate the
DBUS_SESSION_BUS_ADDRESS environment variable into
the child process with a different userid.
For example, here is a failing session, where I became the user 'exp'
and later observed the problem in a shell window:
$ env | grep DBUS
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-bpx4rxPk7z,guid=6e491bf38a5b2b6fce17d0a251a221bf
$ sudo sh
# su exp
$ env | grep DBUS
$ emacs
** (emacs:15115): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-x2KgryK9C8: Connection refused
And here is a session that worked. The key difference is that
I used su's '-E' option:
$ env | grep DBUS
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-bpx4rxPk7z,guid=6e491bf38a5b2b6fce17d0a251a221bf
$ sudo -E sh
# su exp
$ env | grep DBUS
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-bpx4rxPk7z,guid=6e491bf38a5b2b6fce17d0a251a221bf
$ emacs
** (emacs:15441): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-x2KgryK9C8: Connection refused
In both cases, the dbus library complains to stderr that it can't connect
to /tmp/dbus-x2KgryK9C8 (I don't know where it's getting that name from).
When DBUS_SESSION_BUS_ADDRESS is unset, the dbus library arranges to run
the shell script /usr/bin/dbus-launch, which seems to cause the problem.
But when DBUS_SESSION_BUS_ADDRESS is set, the dbus library falls back
on its contents and doesn't invoke dbus-launch.
next prev parent reply other threads:[~2013-05-26 17:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 23:38 bug#14474: 24.3.50; Zombie subprocesses (again) Michael Heerdegen
2013-05-25 23:49 ` Michael Heerdegen
2013-05-26 2:55 ` Eli Zaretskii
2013-05-26 17:37 ` Paul Eggert [this message]
2013-05-26 18:33 ` Michael Heerdegen
2013-05-27 1:36 ` Paul Eggert
2013-05-27 12:46 ` Colin Walters
2013-05-27 17:36 ` Paul Eggert
2013-05-28 16:56 ` Paul Eggert
2013-05-28 20:42 ` Michael Heerdegen
2013-06-04 17:12 ` Michael Heerdegen
2020-09-09 13:52 ` Lars Ingebrigtsen
2013-05-28 17:04 ` Jan Djärv
2013-06-01 1:03 ` Paul Eggert
2013-06-01 1:22 ` Colin Walters
2013-06-01 6:14 ` Paul Eggert
2013-06-01 14:33 ` Stefan Monnier
2013-06-03 16:09 ` Colin Walters
2013-06-04 7:20 ` Paul Eggert
2013-06-05 17:21 ` Paul Eggert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A24870.8020909@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=14474@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).