From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Performance problems with emacs-X11 in current cygwin
Date: Sat, 02 Jun 2012 19:03:00 -0000 [thread overview]
Message-ID: <4FCA634D.1080206@cornell.edu> (raw)
In-Reply-To: <4FCA2CA9.7080704@cornell.edu>
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
next prev parent reply other threads:[~2012-06-02 19:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 21:02 Angelo Graziosi
2012-06-01 11:01 ` Performance problems with emacs-X11 in current cygwin (attn: glib and gvim maintainer) Ken Brown
2012-06-01 11:21 ` atelp
2012-06-01 11:57 ` Ken Brown
2012-06-01 16:23 ` Stephen L
2012-06-01 18:39 ` Ken Brown
2012-06-01 19:10 ` K Stahl
2012-06-02 14:15 ` Performance problems with emacs-X11 in current cygwin Angelo Graziosi
2012-06-02 15:09 ` Ken Brown
2012-06-02 19:03 ` Ken Brown [this message]
2012-06-03 9:08 ` Yaakov (Cygwin/X)
2012-06-03 12:11 ` Ken Brown
2012-06-03 17:01 ` Ken Brown
2012-06-06 11:05 ` Stephen L
2012-06-08 12:59 ` Ken Brown
2012-06-08 15:33 ` Achim Gratz
2012-06-08 16:46 ` Ken Brown
2012-06-08 19:35 ` Andrey Repin
2012-06-11 0:45 ` Ken Brown
2012-06-11 2:54 ` Yaakov (Cygwin/X)
2012-06-11 11:39 ` Ken Brown
2012-06-11 15:11 ` Ken Brown
2012-06-12 13:02 ` Ken Brown
2012-06-11 13:56 ` K Stahl
2012-06-11 14:54 ` Ken Brown
2012-06-11 16:15 ` K Stahl
2012-06-11 17:59 ` Ken Brown
2012-06-11 18:56 ` K Stahl
2012-06-13 18:40 ` Ken Brown
2012-06-13 21:07 ` Ken Brown
2012-06-13 21:40 ` Christopher Faylor
2012-06-14 19:19 ` Ryan Johnson
2012-06-14 19:48 ` Ken Brown
2012-06-13 23:58 ` K Stahl
-- strict thread matches above, loose matches on Subject: below --
2012-06-05 6:29 Pach Roman (DGS-EC/ESG2)
[not found] <AF5E26A9B961BF4681B5C1593D7D03C020AFDD6C1D@SI-MBX06.de.bosch.com>
2012-06-04 15:49 ` Ken Brown
2012-06-01 6:17 Pach Roman (DGS-EC/ESG2)
2012-06-01 23:14 ` Ken Brown
2012-05-25 8:26 Angelo Graziosi
2012-05-30 11:26 ` Stephen L
2012-05-30 14:39 ` Ken Brown
2012-05-31 11:09 ` Stephen L
2012-05-31 13:06 ` Ken Brown
2012-05-24 12:37 Berglund Magnus (SE)
2012-05-24 13:01 ` Ken Brown
2012-05-24 14:51 ` K Stahl
2012-05-25 14:35 ` Ken Jackson
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=4FCA634D.1080206@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@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).