From: Martin G. <mgi...@uo...> - 2002-11-26 18:59:56
|
Hello I've just installed the latest MSYS RC and played around a little with it. Unfortunately after a few seconds I got the shell freezed: I simply resized the window and no further input is possible. Closing the window leaves a dead sh.exe process in memory. This behaviour is reproducable on all my own and my colleagues Win XP/2000 PCs. It only occurs when resizing the window by dragging its borders -- the minimize and maximize buttons work without any unwanted side effects. The list archive contains only one short 10 month old thread concerning this issue with no final solution. Does this effect only happen on our localized (german) win32 systems or can anyone else reproduce this behaviour and give some hints how to solve/work around this bug? Thanks for any help. Martin |
From: Anthony T. <an...@co...> - 2002-11-26 19:13:23
|
I had this same issue when using MSYS 1.0.8 RC-1 so I went back to MSYS 1.0.7 which doesn't have this issue. I thought I had mentioned it on the list a couple of months ago but there was no resolution then either (except go back to 1.0.7). On Tue, 2002-11-26 at 11:59, Martin Gieseking wrote: > Hello > > I've just installed the latest MSYS RC and played around a little with it. > Unfortunately after a few seconds I got the shell freezed: I simply resized > the window and no further input is possible. Closing the window leaves a > dead sh.exe process in memory. This behaviour is reproducable on all my own > and my colleagues Win XP/2000 PCs. It only occurs when resizing the window > by dragging its borders -- the minimize and maximize buttons work without > any unwanted side effects. > The list archive contains only one short 10 month old thread concerning > this issue with no final solution. Does this effect only happen on our > localized (german) win32 systems or can anyone else reproduce this > behaviour and give some hints how to solve/work around this bug? > > Thanks for any help. > > Martin > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T > handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys -- Anthony Tuininga an...@co... Computronix Distinctive Software. Real People. Suite 200, 10216 - 124 Street NW Edmonton, AB, Canada T5N 4A3 Phone: (780) 454-3700 Fax: (780) 454-3838 http://www.computronix.com |
From: Earnie B. <ear...@ya...> - 2002-11-26 19:50:22
|
Martin Gieseking wrote: > Hello > > I've just installed the latest MSYS RC and played around a little with > it. Unfortunately after a few seconds I got the shell freezed: I simply > resized the window and no further input is possible. Closing the window > leaves a dead sh.exe process in memory. This behaviour is reproducable > on all my own and my colleagues Win XP/2000 PCs. It only occurs when > resizing the window by dragging its borders -- the minimize and maximize > buttons work without any unwanted side effects. > The list archive contains only one short 10 month old thread concerning > this issue with no final solution. Does this effect only happen on our > localized (german) win32 systems or can anyone else reproduce this > behaviour and give some hints how to solve/work around this bug? > Hmm... I just tried with NT4 and Win2000 and can't reproduce the problem. Perhaps some more clues such as I did this and then resized or I just started MSYS and resized and then did this. You wouldn't happen to have an libX11.dll in your PATH somewhere? If so, try removing it from the PATH before starting MSYS. Earnie. |
From: Greg C. <chi...@mi...> - 2002-11-26 20:32:26
|
Earnie Boyd wrote: > > Martin Gieseking wrote: > > > > I've just installed the latest MSYS RC and played around a little with > > it. Unfortunately after a few seconds I got the shell freezed: I simply > > resized the window and no further input is possible. Closing the window > > leaves a dead sh.exe process in memory. This behaviour is reproducable > > on all my own and my colleagues Win XP/2000 PCs. It only occurs when > > resizing the window by dragging its borders -- the minimize and maximize > > buttons work without any unwanted side effects. > > The list archive contains only one short 10 month old thread concerning > > this issue with no final solution. Does this effect only happen on our > > localized (german) win32 systems or can anyone else reproduce this > > behaviour and give some hints how to solve/work around this bug? > > Hmm... I just tried with NT4 and Win2000 and can't reproduce the > problem. Perhaps some more clues such as I did this and then resized or > I just started MSYS and resized and then did this. I couldn't reproduce the problem here with win2k. I downloaded this file within the past hour: -rwxrwxrwx 1 Win32 Mingw32 2888995 Nov 26 15:13 MSYS-1.0.8-rc-3.exe and answered the install prompts in an unremarkable way, except that I installed to /msys/1.08/ . I executed this program -rwxrwxrwx 1 Win32 Mingw32 504602 Nov 26 10:02 /msys/1.08/bin/rxvt.exe and tried resizing it by dragging its borders horizontally only vertically only both horizontally and vertically at the same time and also minimizing it maximizing it moving it around switching to another application and back but it doesn't freeze. |
From: Earnie B. <ear...@ya...> - 2002-11-26 19:52:19
|
The rc-1 had other bugs that may have affected your results. Try the new rc-3 to see if it still exists. Earnie. Anthony Tuininga wrote: > I had this same issue when using MSYS 1.0.8 RC-1 so I went back to MSYS > 1.0.7 which doesn't have this issue. I thought I had mentioned it on the > list a couple of months ago but there was no resolution then either > (except go back to 1.0.7). > > On Tue, 2002-11-26 at 11:59, Martin Gieseking wrote: > >>Hello >> >>I've just installed the latest MSYS RC and played around a little with it. >>Unfortunately after a few seconds I got the shell freezed: I simply resized >>the window and no further input is possible. Closing the window leaves a >>dead sh.exe process in memory. This behaviour is reproducable on all my own >>and my colleagues Win XP/2000 PCs. It only occurs when resizing the window >>by dragging its borders -- the minimize and maximize buttons work without >>any unwanted side effects. >>The list archive contains only one short 10 month old thread concerning >>this issue with no final solution. Does this effect only happen on our >>localized (german) win32 systems or can anyone else reproduce this >>behaviour and give some hints how to solve/work around this bug? >> >>Thanks for any help. >> >>Martin >> >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: Get the new Palm Tungsten T >>handheld. Power & Color in a compact size! >>http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en >>_______________________________________________ >>Mingw-msys mailing list >>Min...@li... >>https://lists.sourceforge.net/lists/listinfo/mingw-msys > |
From: Anthony T. <an...@co...> - 2002-11-26 20:12:37
|
Well, that seems to have fixed the problem. The issue with pings that I mentioned earlier seems to have disappeared as well, so I am moving over to 1.0.8 (RC3) for a while and see if anything turns up. Thanks for fixing those problems! On Tue, 2002-11-26 at 12:52, Earnie Boyd wrote: > The rc-1 had other bugs that may have affected your results. Try the > new rc-3 to see if it still exists. > > Earnie. > > Anthony Tuininga wrote: > > I had this same issue when using MSYS 1.0.8 RC-1 so I went back to MSYS > > 1.0.7 which doesn't have this issue. I thought I had mentioned it on the > > list a couple of months ago but there was no resolution then either > > (except go back to 1.0.7). > > > > On Tue, 2002-11-26 at 11:59, Martin Gieseking wrote: > > > >>Hello > >> > >>I've just installed the latest MSYS RC and played around a little with it. > >>Unfortunately after a few seconds I got the shell freezed: I simply resized > >>the window and no further input is possible. Closing the window leaves a > >>dead sh.exe process in memory. This behaviour is reproducable on all my own > >>and my colleagues Win XP/2000 PCs. It only occurs when resizing the window > >>by dragging its borders -- the minimize and maximize buttons work without > >>any unwanted side effects. > >>The list archive contains only one short 10 month old thread concerning > >>this issue with no final solution. Does this effect only happen on our > >>localized (german) win32 systems or can anyone else reproduce this > >>behaviour and give some hints how to solve/work around this bug? > >> > >>Thanks for any help. > >> > >>Martin > >> > >> > >> > >> > >>------------------------------------------------------- > >>This SF.net email is sponsored by: Get the new Palm Tungsten T > >>handheld. Power & Color in a compact size! > >>http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > >>_______________________________________________ > >>Mingw-msys mailing list > >>Min...@li... > >>https://lists.sourceforge.net/lists/listinfo/mingw-msys > > -- Anthony Tuininga an...@co... Computronix Distinctive Software. Real People. Suite 200, 10216 - 124 Street NW Edmonton, AB, Canada T5N 4A3 Phone: (780) 454-3700 Fax: (780) 454-3838 http://www.computronix.com |
From: Martin G. <mgi...@uo...> - 2002-11-26 20:27:27
|
At 20:50 26.11.2002, you wrote: >Hmm... I just tried with NT4 and Win2000 and can't reproduce the >problem. Perhaps some more clues such as I did this and then resized or I >just started MSYS and resized and then did this. > >You wouldn't happen to have an libX11.dll in your PATH somewhere? If so, >try removing it from the PATH before starting MSYS. > >Earnie. The problem happens *always* when resizing the window by dragging the borders. It doesn't matter whether I previously entered some commands or not. I've just downloaded RC3 and the old 1.0.7-i386-2 version; both get freezed when resizing the window. :-( I also looked for a libX11.dll but there is none on my Windows partition (I didn't install cygwin). Martin |
From: Earnie B. <ear...@ya...> - 2002-11-26 20:39:13
|
Martin Gieseking wrote: > At 20:50 26.11.2002, you wrote: > >> Hmm... I just tried with NT4 and Win2000 and can't reproduce the >> problem. Perhaps some more clues such as I did this and then resized >> or I just started MSYS and resized and then did this. >> >> You wouldn't happen to have an libX11.dll in your PATH somewhere? If >> so, try removing it from the PATH before starting MSYS. >> >> Earnie. > > > > The problem happens *always* when resizing the window by dragging the > borders. It doesn't matter whether I previously entered some commands or > not. I've just downloaded RC3 and the old 1.0.7-i386-2 version; both get > freezed when resizing the window. :-( > I also looked for a libX11.dll but there is none on my Windows partition > (I didn't install cygwin). > What do you have in your environment, i.e. what is the output of the set command from within the msys or the %COMSPEC% session? Is it possible that you have a `resize' binary on your path? If you rename msys\1.0\bin\rxvt.exe it will start sh.exe in a %COMSPEC% window and you won't have the freeze problem, but you won't have some nice effects as well, such as highlight and paste. Earnie. |
From: Greg C. <chi...@mi...> - 2002-11-26 22:21:43
|
Earnie Boyd wrote: > > Martin Gieseking wrote: > > At 20:50 26.11.2002, [Earnie] wrote: > > > >> You wouldn't happen to have an libX11.dll in your PATH somewhere? If > >> so, try removing it from the PATH before starting MSYS. > > > > I also looked for a libX11.dll but there is none on my Windows partition > > (I didn't install cygwin). > > What do you have in your environment, i.e. what is the output of the set > command from within the msys or the %COMSPEC% session? > > Is it possible that you have a `resize' binary on your path? Another thought--make sure you're running the installed msys.bat and not just bin/rxvt.exe . I did the latter by accident and the path didn't get set up correctly, so weird things happened. Example: I have a native win32 'less' on my windows path, and it was getting called in an rxvt session, which of course is not good. I wouldn't have though of doing this, except I read the documentation again and saw doc/README.rtf | STARTING Msys: | Starting Msys should just be a matter of clicking | on the MSYS icon on your desktop or Start menu. So far so good. | If you have the File Manager window open, you may | now click on it and have it start also. Well, there's a blue 'M' icon next to rxvt.exe, so I clicked it. Oops. Maybe it would be clearer to say something like If you have Windows Explorer open, you can also start MSYS by double clicking msys.bat . Please don't click the MSYS icons here, though--they won't do what you expect. |
From: Earnie B. <ear...@ya...> - 2002-11-26 22:31:19
|
Greg Chicares wrote: > > Another thought--make sure you're running the > installed msys.bat and not just bin/rxvt.exe . > I did the latter by accident and the path > didn't get set up correctly, so weird things > happened. Example: I have a native win32 'less' > on my windows path, and it was getting called > in an rxvt session, which of course is not good. > From the set listing that was given I know the session was started from the msys.bat script. > I wouldn't have though of doing this, except > I read the documentation again and saw > > doc/README.rtf > > | STARTING Msys: > | Starting Msys should just be a matter of clicking > | on the MSYS icon on your desktop or Start menu. > > So far so good. > > | If you have the File Manager window open, you may > | now click on it and have it start also. > > Well, there's a blue 'M' icon next to rxvt.exe, > so I clicked it. Oops. Maybe it would be clearer > to say something like > > If you have Windows Explorer open, you can also > start MSYS by double clicking msys.bat . Please > don't click the MSYS icons here, though--they > won't do what you expect. > Thanks, I will look at changing the wording of the documentation. Earie. |
From: Martin G. <mgi...@uo...> - 2002-11-26 21:08:18
|
At 21:39 26.11.2002, you wrote: The problem happens *always* when resizing the window by dragging the borders. It doesn't matter whether I previously entered some commands or not. I've just downloaded RC3 and the old 1.0.7-i386-2 version; both get freezed when resizing the window. :-( >>I also looked for a libX11.dll but there is none on my Windows partition >>(I didn't install cygwin). > >What do you have in your environment, i.e. what is the output of the set >command from within the msys or the %COMSPEC% session? > >Is it possible that you have a `resize' binary on your path? > >If you rename msys\1.0\bin\rxvt.exe it will start sh.exe in a %COMSPEC% >window and you won't have the freeze problem, but you won't have some nice >effects as well, such as highlight and paste. > >Earnie. A search for a resize binary ended with no result. I also tried your suggestion and renamed rxvt.exe. The appearing window really looks much simpler but the freeze effect still happens. Maybe you can locate some misconfigurations in my environment, so I attach the output of 'set'. Martin !::='::\' !C:='C:\mingw\msys\1.0\bin' ALLUSERSPROFILE='C:\Dokumente und Einstellungen\All Users' APPDATA='C:\Dokumente und Einstellungen\Martin Gieseking\Anwendungsdaten' BASH=/bin/sh BASH_VERSINFO=([0]="2" [1]="04" [2]="0" [3]="1" [4]="release" [5]="i686-pc-msys") BASH_VERSION='2.04.0(1)-release' BGCOLOR=LightYellow CLIENTNAME=Console COLORFGBG='default;default' COLORTERM=rxvt COLUMNS=80 COMMONPROGRAMFILES='C:\Programme\Gemeinsame Dateien' COMPUTERNAME=PC COMSPEC='C:\WINDOWS\system32\cmd.exe' CONFIG_SITE=/etc/config.site DEVMGR_SHOW_NONPRESENT_DEVICES=1 DIRSTACK=() DISPLAY=:0 EUID=500 FGCOLOR=Navy GROUPS=() HISTFILE='/home/Martin Gieseking/.bash_history' HISTFILESIZE=500 HISTSIZE=500 HOME='/home/Martin Gieseking' HOMEDRIVE=C: HOMEPATH='\' HOSTNAME=PC HOSTTYPE=i686 IFS=' ' LINES=25 LOGNAME='Martin Gieseking' LOGONSERVER='\\PC' MACHTYPE=i686-pc-msys MAILCHECK=60 MAKE_MODE=unix MINGW32BGCOLOR=LightYellow MINGW32FGCOLOR=Navy MSYSBGCOLOR=White MSYSFGCOLOR=Black MSYSTEM=MINGW32 NUMBER_OF_PROCESSORS=1 OLDPWD='/home/Martin Gieseking' OPTERR=1 OPTIND=1 OS=Windows_NT OSTYPE=msys PATH='.:/usr/local/bin:/mingw/bin:/bin:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/COMMAND:/c/WINDOWS/system32/WBEM:/c/Programme/Gemeinsame Dateien/GIS/Tools:/mingw/bin:/c/bcc/bin:/c/Programme/SSH:/c/programme/vim/vim61:/c/tex/texmf/miktex/bin:/c/WINDOWS:/c/WINDOWS/COMMAND' PATHEXT='.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PIPESTATUS=([0]="0") PPID=1144 PROCESSOR_ARCHITECTURE=x86 PROCESSOR_IDENTIFIER='x86 Family 6 Model 4 Stepping 2, AuthenticAMD' PROCESSOR_LEVEL=6 PROCESSOR_REVISION=0402 PROGRAMFILES='C:\Programme' PROMPT='$p$g' PS1='\[\033]0;$MSYSTEM:\w\007 \033[32m\]\u@\h \[\033[33m\w\033[0m\] $ ' PS2='> ' PS4='+ ' PWD=/c SESSIONNAME=Console SHELL=/bin/sh SHELLOPTS=braceexpand:hashall:histexpand:monitor:history:interactive-comments:emacs SHLVL=1 SYSTEMDRIVE=C: SYSTEMROOT='C:\WINDOWS' TEMP=/tmp TERM=msys TMP=/tmp UID=500 USERDOMAIN=PC USERNAME='Martin Gieseking' USERPROFILE='C:\Dokumente und Einstellungen\Martin Gieseking' WINBOOTDIR='C:\WINDOWS' WINDIR='C:\WINDOWS' WINDOWID=167838872 _=o i='/etc/profile.d/*.sh' |
From: Earnie B. <ear...@ya...> - 2002-11-26 21:26:47
|
Martin Gieseking wrote: > > Maybe you can locate some misconfigurations in my environment, so I > attach the output of 'set'. > Yes. > Martin > -8<- > DISPLAY=:0 I have specific code in msys.bat to remove this variable. How is it that you have it in yours? Earnie. |
From: Martin G. <mgi...@uo...> - 2002-11-26 21:51:49
|
At 22:38 26.11.2002, you wrote: >Earnie Boyd wrote: >>Martin Gieseking wrote: >> >>> >>>Maybe you can locate some misconfigurations in my environment, so I >>>attach the output of 'set'. >>Yes. >> >>>Martin >>-8<- >> >>>DISPLAY=:0 >> >>I have specific code in msys.bat to remove this variable. How is it that >>you have it in yours? > >I meant to say, how is it that you have it set in your environment? It's a good question. I don't really know. When starting msys.bat with renamed rxvt in a (black) console window the DISPLAY variable isn't set/doesn't exist. But with the regular rxvt.exe it appears. I haven't installed any X server and can't explain yet why and where it is set. Unsetting DISPLAY in the shell doesn't change anything concerning the freezing. Martin |
From: Earnie B. <ear...@ya...> - 2002-11-26 21:38:49
|
Earnie Boyd wrote: > Martin Gieseking wrote: > >> >> Maybe you can locate some misconfigurations in my environment, so I >> attach the output of 'set'. >> > > Yes. > >> Martin >> > -8<- > >> DISPLAY=:0 > > > I have specific code in msys.bat to remove this variable. How is it > that you have it in yours? > I meant to say, how is it that you have it set in your environment? Earnie. |
From: Earnie B. <ear...@ya...> - 2002-11-26 22:13:31
|
Martin Gieseking wrote: > At 22:38 26.11.2002, you wrote: > >> Earnie Boyd wrote: >> >>> Martin Gieseking wrote: >>> >>>> >>>> Maybe you can locate some misconfigurations in my environment, so I >>>> attach the output of 'set'. >>> >>> Yes. >>> >>>> Martin >>> >>> -8<- >>> >>>> DISPLAY=:0 >>> >>> >>> I have specific code in msys.bat to remove this variable. How is it >>> that you have it in yours? >> >> >> I meant to say, how is it that you have it set in your environment? > > > It's a good question. I don't really know. When starting msys.bat with > renamed rxvt in a (black) console window the DISPLAY variable isn't > set/doesn't exist. But with the regular rxvt.exe it appears. I haven't > installed any X server and can't explain yet why and where it is set. > Unsetting DISPLAY in the shell doesn't change anything concerning the > freezing. > Yeah, it's in mine as well, must be set by rxvt after checking to see if it's preexisting. You say that it freezes even in the "black" console window? If yes then I'm not sure what's wrong. Perhaps using a different codepage would help? Does it seem to work except for the freezing on resizing? Earnie. |
From: Martin G. <mgi...@uo...> - 2002-11-26 22:29:42
|
At 23:13 26.11.2002, you wrote: >>>>>DISPLAY=:0 >>>> >>>> >>>>I have specific code in msys.bat to remove this variable. How is it >>>>that you have it in yours? >>> >>> >>>I meant to say, how is it that you have it set in your environment? >> >>It's a good question. I don't really know. When starting msys.bat with >>renamed rxvt in a (black) console window the DISPLAY variable isn't >>set/doesn't exist. But with the regular rxvt.exe it appears. I haven't >>installed any X server and can't explain yet why and where it is set. >>Unsetting DISPLAY in the shell doesn't change anything concerning the freezing. > >Yeah, it's in mine as well, must be set by rxvt after checking to see if >it's preexisting. > >You say that it freezes even in the "black" console window? If yes then >I'm not sure what's wrong. Perhaps using a different codepage would help? > >Does it seem to work except for the freezing on resizing? > >Earnie. No, sorry. I started the wrong executable. In the black console window everything works fine even if it is resized. So it does in the rxvt window when leaving its size unchanged. As far as I could evaluate msys yet the only thing that doesn't work correctly is the resizing. Martin |