public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Problems with emacs built against gtk3
Date: Sat, 26 Nov 2011 13:40:00 -0000 [thread overview]
Message-ID: <4ED0EC50.4090300@cornell.edu> (raw)
In-Reply-To: <4ED03512.7080607@cornell.edu>
On 11/25/2011 7:38 PM, Ken Brown wrote:
> When I build emacs against gtk3, it is unusable. Here are the symptoms
> when the resulting emacs is started in an xterm window:
>
> $ ./emacs -Q&
> [1] 3344
>
> (emacs:3344): GLib-WARNING **: In call to g_spawn_sync(), exit status of
> a child process was requested but SIGCHLD action was set to SIG_IGN and
> ECHILD was received by waitpid(), so exit status can't be returned. This
> is a bug in the program calling g_spawn_sync(); either don't request the
> exit status, or don't set the SIGCHLD action.
>
> ** (emacs:3344): WARNING **: Abnormal program termination spawning
> command line `dbus-launch --autolaunch=0b8f184fe6d82872ee8db8724ecfdb90
> --binary-syntax --close-stderr':
>
> (emacs:3344): Pango-WARNING **: No such file or directory
>
> A few seconds later, emacs dies (the window disappears and the process
> is gone, with no error messages), and two dbus processes remain:
>
> $ ps | grep dbus
> 5188 1 3344 5188 7 1002 19:07:31 /usr/bin/dbus-launch
> 6452 1 6452 6452 ? 1002 19:07:31 /usr/bin/dbus-daemon
>
> If I start emacs again without killing the dbus processes, I don't get
> the first two warnings but I still get the third. Again, emacs dies
> after a few seconds.
>
> I think the pango warning is Cygwin specific, but the rest of it might
> not be. Similar symptoms were reported on Fedora:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=654027
>
> But there are some differences, so I thought I should report it here
> just in case part of the problem is Cygwin specific. My cygcheck output
> is attached but probably not relevant.
Further info:
1. I don't think gtk3 is the culprit here after all. I uninstalled
libgtk3_0 and libgtk3-devel and rebuilt emacs, but the problem
persisted. It was only after uninstalling dconf-service (a dependency
of libgtk3_0) that things went back to normal [except for the pango
warning].
2. The pango warning can already be observed with the current Cygwin
emacs after the recent update of the GNOME libraries. To reproduce,
install the emacs-X11 package and start emacs with the command `emacs &'
in an xterm window.
Ken
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2011-11-26 13:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 0:39 Ken Brown
2011-11-26 13:40 ` Ken Brown [this message]
2011-11-30 3:52 ` Yaakov (Cygwin/X)
2011-11-30 10:25 ` Pavel Holejsovsky
2011-11-30 11:54 ` Yaakov (Cygwin/X)
2011-11-30 12:27 ` Ken Brown
2011-12-10 12:14 ` nyc4bos
2011-12-13 18:51 ` Ken Brown
2011-11-30 14:09 ` Ken Brown
2011-12-02 10:36 ` Ken Brown
2011-12-02 13:01 ` Yaakov (Cygwin/X)
2011-12-03 2:30 ` Ken Brown
2011-12-05 0:22 ` Yaakov (Cygwin/X)
2011-12-05 13:28 ` Ken Brown
2011-12-10 1:40 ` Ken Brown
2012-04-03 21:13 ` Ken Brown
2012-04-03 22:30 ` Yaakov (Cygwin/X)
2012-04-04 1:53 ` Ken Brown
2012-04-04 3:56 ` Yaakov (Cygwin/X)
2012-04-04 14:15 ` Ken Brown
2012-04-04 22:13 ` Yaakov (Cygwin/X)
2012-04-06 17:22 ` Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] Ken Brown
2011-12-05 0:13 ` Problems with emacs built against gtk3 nyc4bos
2011-11-28 8:49 Angelo Graziosi
2011-12-03 15:18 ` Angelo Graziosi
2011-12-05 0:38 ` Yaakov (Cygwin/X)
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=4ED0EC50.4090300@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-xfree@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).