public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Problems with emacs built with gsettings support
Date: Sun, 15 Apr 2012 12:20:00 -0000	[thread overview]
Message-ID: <4F8ABCFC.7050103@cornell.edu> (raw)
In-Reply-To: <4F8355E4.60609@cornell.edu>

I haven't made in progress in trying to debug this problem.  I think I 
will probably have to build the next release of emacs without GSettings 
support.  (This is a shame, but it's not a regression; emacs has never 
had the possibility of supporting GSettings prior to emacs-24.)  If 
there are any emacs users out there who care about this, read on.

First, here's a summary of what I know.  Everything I say is independent 
of whether I build emacs with gtk2 or gtk3.

* If emacs is built with GSettings support, it seems to work fine on 
Windows XP.

* It also works fine on my 64-bit Windows 7 systems if I

   export GSETTINGS_BACKEND=memory

* It fails on my Windows 7 systems otherwise.  The failure consists of 
emacs crashing with a segmentation fault shortly after it starts.  This 
could happen after a few minutes or a few hours, but it always happens.

* I haven't found any indication that this is a BLODA problem, but I 
can't rule it out either.

It would be very helpful if other people could try it on Windows 7. 
Here are the steps for testing, which are simpler than what I posted 
earlier in the thread:

1. Install my test build of emacs-X11-24.0.95-7 by running

   setup.exe -K http://sanibeltranquility.com/cygwin/kbrown.gpg

and adding http://sanibeltranquility.com/cygwin to the list of mirrors. 
  This was built with gtk3, so you'll have to let setup install a bunch 
of dependencies unless you already have libgtk3_0 installed.

2. Start the X server using the Start Menu shortcut, with no ~/.startxwinrc.

3. In the resulting xterm window:

eval `dbus-launch --sh-syntax`
emacs -Q &

4. Wait a few hours, if necessary, to see if emacs crashes.  You can use 
it or just leave it alone (but don't use it for anything important).

5. Send a note to the list reporting success or failure, with details 
about your system.

6. If it fails, you can rerun setup.exe to restore your previous version 
of emacs.  Or, if you'd like, you can install my build of 
emacs-X11-24.0.95-6, which was built without GSettings support.

Thanks in advance to anyone who is willing to test.

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/


      reply	other threads:[~2012-04-15 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 19:22 Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] Angelo Graziosi
2012-04-07 22:11 ` Angelo Graziosi
2012-04-08 11:18   ` Ken Brown
2012-04-08 14:10   ` Angelo Graziosi
2012-04-09 22:41     ` Problems with emacs built with gsettings support Angelo Graziosi
2012-04-09 21:34   ` Ken Brown
2012-04-15 12:20     ` Ken Brown [this message]

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=4F8ABCFC.7050103@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).