From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6958 invoked by alias); 2 Dec 2011 13:01:25 -0000 Received: (qmail 6948 invoked by uid 22791); 2 Dec 2011 13:01:24 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL,TW_GT,TW_GV 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; Fri, 02 Dec 2011 13:01: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 pB2D19gS018786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 2 Dec 2011 08:01:10 -0500 (EST) Message-ID: <4ED8CC12.5050607@cornell.edu> Date: Sat, 03 Dec 2011 02:30: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> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> In-Reply-To: <1322822150.6352.13.camel@YAAKOV04> 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/msg00005.txt.bz2 On 12/2/2011 5:35 AM, Yaakov (Cygwin/X) wrote: > On Thu, 2011-12-01 at 18:04 -0500, Ken Brown wrote: >> On 11/30/2011 9:09 AM, Ken Brown wrote: >>> On 11/29/2011 10:51 PM, Yaakov (Cygwin/X) wrote: >>>> 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 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? > > Okay, I got it. dconf-service needs a GVfs implementation, but the > default provider (from the gvfs package) is currently only available in > Ports. That's what I get for trying to be minimalistic wrt the distro. > > Of course, my gvfs package requires Avahi[1], so it may be an > interesting ITP; I'll try to do that next week, and hopefully this > thread will help expedite the review nonetheless. > > In the meantime, try setting the GIO_USE_VFS environment variable to > "local"[2], which will allow dconf-service to work despite the lack of > gvfs. (Why this isn't done automatically as a fallback, I have no > idea.) This doesn't do it. Emacs still dies after a short time. I don't know if that means that there's something else going on, but I'll retest it after you package gvfs. In the meantime, I'll continue with my workaround of setting GSETTINGS_BACKEND=memory. In case you (or anyone else) wants to experiment with this, you can get my build of the emacs-24 pretest by running setup.exe -K http://www.math.cornell.edu/~kbrown/kbrown.gpg and adding http://www.math.cornell.edu/~kbrown to the list of mirrors. 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/