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
