From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: 3-line Emacs window after Gnome updates
Date: Thu, 23 Mar 2017 21:11:00 -0000 [thread overview]
Message-ID: <ecc33764-0eac-bcb6-7d2b-f5f87801ed49@cornell.edu> (raw)
In-Reply-To: <CAK-n8j7NBYf9WKxcaH5j7dV3fboKsWMHiGSLKdkyrUq-45EdVA@mail.gmail.com>
n 3/23/2017 1:18 PM, Jim Reisert AD1C wrote:
>> Yaakov released a ton of Gnome updates Wednesday 3/22. Now when I
>> start Emacs in an xterm, I get the following error, and the resulting
>> Emacs window is only 3-lines tall:
I can confirm this.
>> ** (emacs:8440): WARNING **: Error retrieving accessibility bus
>> address: org.freedesktop.DBus.Error.Spawn.ChildExited: Process
>> org.a11y.Bus exited with status 1
I see this when I log in as an administrator, but not when I'm an
ordinary user. We've discussed this before, and I think it's harmless.
>> 0 [main] emacs 8440 dlclose:
>> C:\Cygwin64\lib\gio\modules\cyggsettingsgconfbackend.dll count 1
>> 260 [main] emacs 8440 dll_list::detach: HERE
>> C:\Cygwin64\lib\gio\modules\cyggsettingsgconfbackend.dll
I don't see this...
> Another message:
>
> (emacs:8260): Gtk-WARNING **: Allocating size to Emacs 0x6004de270
> without calling gtk_widget_get_preferred_width/height().
... or this.
> How does the
> code know the size to allocate?
Do you have an emacs.geometry setting in your ~/.Xresources? Or any
kind of size setting in your emacs initialization files? If not, I
guess emacs or X11 has a default.
I'll look into the 3-line window and see if I can figure out what's
going on.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-03-23 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 15:47 Jim Reisert AD1C
2017-03-23 19:08 ` Jim Reisert AD1C
2017-03-23 21:11 ` Ken Brown [this message]
2017-03-23 21:55 ` Yaakov Selkowitz
2017-03-24 13:04 ` Ken Brown
2017-03-24 13:45 ` Ken Brown
2017-03-24 0:02 ` Jim Reisert AD1C
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=ecc33764-0eac-bcb6-7d2b-f5f87801ed49@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).