all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: michael.albinus@gmx.de
To: Tim Van Holder <tim.vanholder@gmail.com>
Cc: 15154@debbugs.gnu.org
Subject: bug#15154: 24.3; Various GTK warnings on debian jessie/sid
Date: Thu, 22 Aug 2013 12:22:25 +0200	[thread overview]
Message-ID: <yqpgmwoakota.fsf@gmx.de> (raw)
In-Reply-To: <CAKMi--DFOQeFNH8x3UcDpW8LS8zqNL-q+rMrAHM+Eefnka=ETQ@mail.gmail.com> (Tim Van Holder's message of "Wed, 21 Aug 2013 19:01:25 +0200")

Tim Van Holder <tim.vanholder@gmail.com> writes:

> I typically run emacs via a ssh (PuTTY) session, using the
> Cygwin X server.
> Emacs was built from sources (24.3 release tarball), with GTK2
> auto-selected as X toolkit (even though it apparently uses GTK3).
>
> Starting emacs (-Q or otherwise), results in:
>
> ** (emacs:<pid>): WARNING **: Couldn't connect to accessibility bus:
> Failed to connect to socket /tmp/dbus-OfJcFmA1Hb: Connection
> refused
>
> Given that I explicitly disabled DBus stuff (to avoid dbus-launch
> processes that would prevent a clean ssh exit) when building emacs,
> this
> is already a bit odd. There is no such entry in /tmp (in fact there
> are
> no /tmp/dbus-* files at all), nor is there any envvar containing
> OfJcFmA1Hb.

That's not because of Emacs and its D-Bus integration. Linked GTK try to
connect to at-spi (Assistive Technology Service Provider Interface).

Check your Gnome configuration how to disable it. I suspect you must
disable /desktop/gnome/interface/at-spi-dbus, but I don't know it for
sure. You might check your settings with 

# gconftool-2 --get /desktop/gnome/interface/at-spi-dbus

Best regards, Michael.





  reply	other threads:[~2013-08-22 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 17:01 bug#15154: 24.3; Various GTK warnings on debian jessie/sid Tim Van Holder
2013-08-22 10:22 ` michael.albinus [this message]
2013-08-26  8:40   ` Tim Van Holder
2013-08-26 15:52 ` Jan Djärv

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=yqpgmwoakota.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=15154@debbugs.gnu.org \
    --cc=tim.vanholder@gmail.com \
    /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.