X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_NEUTRAL,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
Message-ID:	<4FCA634D.1080206@cornell.edu>
Date:	Sat, 02 Jun 2012 15:02:37 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Performance problems with emacs-X11 in current cygwin
References:	<4FC7D9E6 DOT 5050609 AT alice DOT it> <4FCA1FF0 DOT 8090703 AT alice DOT it> <4FCA2CA9 DOT 7080704 AT cornell DOT edu>
In-Reply-To:	<4FCA2CA9.7080704@cornell.edu>
X-PMX-CORNELL-SPAM-CHECKED:	Pawpaw
X-Original-Sender:	kbrown AT cornell DOT edu - Sat Jun 2 15:02:41 2012
X-PMX-CORNELL-REASON:	CU_White_List_Override
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 6/2/2012 11:09 AM, Ken Brown wrote:
> We can revert by using the CTM (Cygwin Time Machine):
>
> http://www.fruitbat.org/Cygwin/index.html#cygwintimemachine
>
> I'm hoping to do that this weekend on my XP machine and see if I can pin
> down when the problem started. I made some incorrect statements about
> that earlier in the thread.
>
> The problem was first reported on the list on May 11:
>
> http://cygwin.com/ml/cygwin-xfree/2012-05/msg00007.html ,
>
> and the poster said he had updated on May 10. This is the day it was
> announced that the GNOME libraries were updated to 3.4.1 and that cygwin
> was updated to 1.7.15.
>
> The CTM has a snapshot dated 2012-05-08, which is probably a good place
> to start.

That worked for me.  I reverted all GNOME components to the versions in 
that CTM snapshot, and then I upgraded them one at a time until the 
emacs problem appeared.  This happened when I upgraded libglib2.0_0 from 
2.30.2-1 to 2.32.2-1, so I downgraded it again.  I also had to keep the 
following old versions:

   libgtk2.0_0-2.24.10-1
   libgdk_pixbuf2.0_0-2.24.1-1
   libpango1.0_0-1.29.4-2

When I tried to upgrade any of those, emacs would immediately exit with 
error 127.  I guess they rely on features of the newer libglib.  All of 
my other packages are up to date, and I can't detect any problems with 
emacs-X11-23.4-2 or emacs-X11-24.0.96-2.

I'm trying to keep a fairly minimal set of packages installed on my XP 
system, so other people may find that they have additional packages that 
need to be downgraded to work around this problem.

I hope someone (Yaakov?) will take a look at the glib changes between 
2.30.2 and 2.32.2 and try to find the cause of this problem.

I don't use gvim, so I don't know whether the same downgrades will help 
with the gvim problem.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -