Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Sun, 6 Apr 2003 21:00:50 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: "Henry S. Thompson" <ht AT cogsci DOT ed DOT ac DOT uk>
cc: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: rxvt-2.7.10-3 (shortcut prob)
In-Reply-To: <f5bu1dbr2xp.fsf@erasmus.inf.ed.ac.uk>
Message-ID: <Pine.GSO.4.44.0304062054260.21921-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 6 Apr 2003, Henry S. Thompson wrote:

> Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu> writes:
>
> > On 6 Apr 2003, Henry S. Thompson wrote:
> >
> > > Steve O <bub AT io DOT com> writes:
> > >
> > > > > no longer works -- it launches the window and hangs without ever
> > > > > displaying anything.  Typing a character crashes it.
> > > >
> > > > Your trace shows rxvt receiving a ^G and lots of nulls at startup
> > > > which is odd.  I couldn't tell too much more since your trace
> > > > looks a lot different than a trace I made.  You appear to have
> > > > an older cygwin1.dll.  Maybe upgrading will fix this?
> > >
> > > Thanks for looking at this at all.  I'm running the latest cygwin
> > > (1.3.22-1), so I don't think that's the explanation . . oops, I
> > > _thought_ I was running 1.3.22, and so did part of cygcheck, but other
> > > parts showed 1.3.20, so I re-installed and all is now OK.  Not clear
> > > to me how this happened, but thanks v. much for steering me in the
> > > right direction.
> > >  ht
> >
> > Henry,
> >
> > A few quick questions: Did you stop all Cygwin processes before running
> > setup.exe?
>
> I believe I left one bash running by mistake.
>
> > If not, did you reboot after upgrading the "cygwin" package?
>
> Yes, although not immediately.
>
> > Did setup.exe ask you to?
>
> Yes.
>
> What _didn't_ happen was the "you've got two cygwins" problems I would
> expect based on passed experience with that sort of scenario, so I
> assumed I was OK.
>
> ht

Henry,

Did the reboot help?  Or did you reinstall before the reboot?
FYI, you would not have gotten the two cygwin DLLs problem since the new
DLL would not be seen as a DLL until the reboot (the extension would have
been ".new").
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/