From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18798 invoked by alias); 10 Dec 2011 12:24:40 -0000 Received: (qmail 18735 invoked by uid 22791); 10 Dec 2011 12:24:24 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL,TW_GT,TW_JS X-Spam-Check-By: sourceware.org Received: from granite1.mail.cornell.edu (HELO authusersmtp.mail.cornell.edu) (128.253.83.141) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 10 Dec 2011 12:24:10 +0000 Received: from [192.168.1.3] (cpe-67-249-194-47.twcny.res.rr.com [67.249.194.47]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id pBACO8Ul012555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 10 Dec 2011 07:24:09 -0500 (EST) Message-ID: <4EE34F66.4030001@cornell.edu> Date: Tue, 13 Dec 2011 18:51:00 -0000 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: Problems with emacs built against gtk3 References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <1322654060.7644.0.camel@YAAKOV04> <4ED62104.7080008@cornell.edu> <84k46519yl.fsf@aol.com> In-Reply-To: <84k46519yl.fsf@aol.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2011-12/txt/msg00024.txt.bz2 On 12/9/2011 8:39 PM, nyc4bos@aol.com wrote: > Ken Brown writes: > >> On 11/30/2011 6:54 AM, Yaakov (Cygwin/X) wrote: >>> On Wed, 2011-11-30 at 11:17 +0100, Pavel Holejsovsky wrote: >>>> On 11/30/2011 4:51 AM, Yaakov (Cygwin/X) wrote: >>>>>> 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. >>>>> >>>>> I cannot reproduce this. Does installing font-cantarell-otf help? >>>>> Perhaps another font? >>>> >>>> I can reproduce it, in fact almost every gtk-enabled application spits >>>> that out. I tried stracing, and I think (but I'm not sure) that the >>>> warning appears after pango tries to load >>>> /usr/lib/pango/1.6.0/modules/pango-basic-fc.dll -> there is no >>>> /usr/lib/pango directory on my system, and it seems that no package in >>>> cygwin or ports repository provides it. >>> >>> That's the clue I needed. I switched pango to builtin modules over a >>> year ago in Ports to help minimize fork() errors, but that didn't reach >>> the distro until now. If I'm right, removing /etc/pango/pango.modules >>> should fix it. >> >> That fixes it. Thanks. > > Unless I do: > > GSETTINGS_BACKEND=memory emacs& > > I get the following error: > > $ > (emacs:4048): 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:4048): WARNING **: Abnormal program termination spawning command line `dbus-launch --autolaunch=614770a5ea44ec425e4c57144ed14d5c --binary-syntax --close-stderr': > > [1]+ Segmentation fault emacs > > > I have no /etc/pango/pango.modules file Removing /etc/pango/pango.modules was to get rid of a pango warning that a lot of people were getting. Yaakov explained how to get rid of the error you're talking about here: http://cygwin.com/ml/cygwin-xfree/2011-11/msg00045.html 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/