public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-xfree@cygwin.com
Subject: Re: Problems with emacs built against gtk3
Date: Fri, 02 Dec 2011 13:01:00 -0000 [thread overview]
Message-ID: <1322822150.6352.13.camel@YAAKOV04> (raw)
In-Reply-To: <4ED807FA.7050700@cornell.edu>
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/
next prev parent reply other threads:[~2011-12-02 10:36 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
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) [this message]
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=1322822150.6352.13.camel@YAAKOV04 \
--to=yselkowitz@users.sourceforge.net \
--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).