public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Emacs slow startup
Date: Fri, 05 Oct 2018 13:29:00 -0000	[thread overview]
Message-ID: <9ccd11f9-fa1d-b1ac-69d9-fa78b7d8e5d1@cornell.edu> (raw)
In-Reply-To: <b4msh1mbnhv.fsf@jpl.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1291 bytes --]

On 10/3/2018 7:48 PM, Katsumi Yamaoka wrote:
> Hi,
> 
> Since a couple of months ago, Emacs takes about a minute to start.
> This happens with both emacs-X11 (the one Cygwin distributes) and
> the one I built, and everytime I get the following error:
> 
> ** (emacs:10672): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
> 
> I googled it and found an article in which someone wrote that
> installing at-spi2-core solves it.  Although the version 2.26.2
> has already been installed in my system, I tried downgrading it
> to 2.24.1.  It did the trick!  Emacs startup got fast as before.

I can confirm that downgrading at-spi2-core gets rid of the warning.  But, FWIW, 
I don't see any difference in Emacs's performance.  (I wasn't experiencing the 
slow startup that you reported.)

Ken
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

      parent reply	other threads:[~2018-10-05 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 23:48 Katsumi Yamaoka
2018-10-04 15:09 ` Yisu Peng
2018-10-05 13:29 ` Ken Brown [this message]

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=9ccd11f9-fa1d-b1ac-69d9-fa78b7d8e5d1@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.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. 
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).