[ANNOUNCEMENT] Updated: rxvt-2.7.10-3 (shortcut prob)

Igor Pechtchanski pechtcha@cs.nyu.edu
Mon Apr 7 14:55:00 GMT 2003


On 7 Apr 2003, Henry S. Thompson wrote:

> Igor Pechtchanski <pechtcha@cs.nyu.edu> writes:
>
> > On 6 Apr 2003, Henry S. Thompson wrote:
> >
> > > Igor Pechtchanski <pechtcha@cs.nyu.edu> writes:
> > >
> > > > On 6 Apr 2003, Henry S. Thompson wrote:
> > > >
> > > > > Steve O <bub@io.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?
>
> No.
>
> > Or did you reinstall before the reboot?
>
> No.
>
> > 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").
>
> Right.   Thanks again, but Let's drop this, in-so-far as I don't have a
> well-documented story of the steps I went through.
>  ht

Henry,

NNTR.  The reason for this line of questioning is that if the
replace-on-reboot feature in setup.exe doesn't work, we'd really like to
know about it.  There have been sporadic reports of this, but nothing that
would pin down the problem.  Thanks for your patience in answering these
questions.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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/



More information about the Cygwin mailing list