From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3851 invoked by alias); 1 Dec 2011 23:04:45 -0000 Received: (qmail 3843 invoked by uid 22791); 1 Dec 2011 23:04:44 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL,TW_GT 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; Thu, 01 Dec 2011 23:04:29 +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 pB1N4RJM025845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 1 Dec 2011 18:04:28 -0500 (EST) Message-ID: <4ED807FA.7050700@cornell.edu> Date: Fri, 02 Dec 2011 10:36: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> <4ED6390C.2040708@cornell.edu> In-Reply-To: <4ED6390C.2040708@cornell.edu> Content-Type: text/plain; charset=UTF-8; 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/msg00003.txt.bz2 On 11/30/2011 9:09 AM, Ken Brown wrote: > On 11/29/2011 10:51 PM, Yaakov (Cygwin/X) wrote: >> On Sat, 2011-11-26 at 08:40 -0500, Ken Brown wrote: >>> 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': >>>> >>>> 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 >> >> This appears to be the same bug. The solution is to launch a DBus >> session bus *before* starting emacs (or any other gtk3 programs for that >> matter), IOW: >> >> $ eval `dbus-launch --sh-syntax` >> $ emacs-X11& > > That gets rid of the warning, but emacs still dies after a few seconds > (no error message, no stackdump), unless I uninstall dconf-service. I'll > see if I can get more information by running emacs under gdb. I'd > appreciate any suggestions you might have as to where I should look. > > I forgot to say in my first post that the emacs I'm testing is a pretest > of the upcoming emacs-24.1. If I'm not able to figure out what's going > on, maybe I'll make an experimental version available so that you can > try to reproduce the problem. I have some further information: The problem is related to the GSettings backend. If I uninstall dconf-service and start emacs, I get a warning that the GSettings `memory' backend will be used. Emacs then works fine. If I reinstall dconf-service but set GSETTINGS_BACKEND=memory before starting emacs, it again works fine. Does this provide any clue as to what the problem might be? 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/