From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3472 invoked by alias); 2 Dec 2011 10:36:11 -0000 Received: (qmail 3463 invoked by uid 22791); 2 Dec 2011 10:36:10 -0000 X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_GT,TW_GV,URI_BLOGSPOT X-Spam-Check-By: sourceware.org Received: from mail-qw0-f50.google.com (HELO mail-qw0-f50.google.com) (209.85.216.50) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 02 Dec 2011 10:35:56 +0000 Received: by qabg14 with SMTP id g14so2437101qab.2 for ; Fri, 02 Dec 2011 02:35:56 -0800 (PST) Received: by 10.224.18.147 with SMTP id w19mr2422688qaa.40.1322822155946; Fri, 02 Dec 2011 02:35:55 -0800 (PST) Received: from [192.168.0.100] (S0106000cf16f58b1.wp.shawcable.net. [24.79.200.150]) by mx.google.com with ESMTPS id hk1sm4874167qab.8.2011.12.02.02.35.53 (version=SSLv3 cipher=OTHER); Fri, 02 Dec 2011 02:35:54 -0800 (PST) Message-ID: <1322822150.6352.13.camel@YAAKOV04> Subject: Re: Problems with emacs built against gtk3 From: "Yaakov (Cygwin/X)" To: cygwin-xfree@cygwin.com Date: Fri, 02 Dec 2011 13:01:00 -0000 In-Reply-To: <4ED807FA.7050700@cornell.edu> References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 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/msg00004.txt.bz2 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.) Yaakov Cygwin/X [1] http://cygwinports.blogspot.com/2011/07/this-lemur-can-be-found-outside-of.html [2] http://developer.gnome.org/gio/2.30/ch03.html -- 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/