#2372: GRASS 7 on windows starts with minimized CMD window
-------------------------+--------------------------------------------------
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.0
Component: Startup | Version: svn-releasebranch70
Keywords: wingrass | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
This is an inverse bug of #1891
Steps to reproduce:
* Install Wingrass on a clean machine (without previous GRASS 7 install
or just remove AppData/Roaming/GRASS7 folder)
* Click on "GRASS GIS 7.0.0svn GUI" icon to launch GRASS
* Observe how GRASS fails to start.
Actual behaviour - GRASS starts a minimized CMD window with a welcome
message and prompt "Press Enter to continue". Unless user notices
minimized CMD window and makes a correct guess to restore the window to
read any messages there, he waits forever for GRASS to start.
Expected behaviour - GRASS starts with normal (non-minimized) CMD window
thus allowing user to read the Welcome message and press Enter to launch
GUI.
I had a chance to observe how 20 persons were hit by this bug. Thus a
claim "it doesn't affect users" is not a valid one.
Tested on Wingrass 7.0.0 yesterdays nightly.
Setting as a blocker for 7.0 release, as 1) it is ruining the first
impression about GRASS GIS and 2) it is trivial to fix.
Replying to [ticket:2372 marisn]:
>
> Setting as a blocker for 7.0 release, as 1) it is ruining the first
impression about GRASS GIS and 2) it is trivial to fix.
Replying to [ticket:2372 marisn]:
> This is an inverse bug of #1891
>
> Steps to reproduce:
> * Install Wingrass on a clean machine (without previous GRASS 7 install
or just remove AppData/Roaming/GRASS7 folder)
mmmhhh, just thinking more about it:
after installing the winGRASS-standalone on a fresh box, there should be
the AppData/Roaming?/GRASS7-folder, because the winGRASS-standalone
installer should do it for you, see:
Replying to [ticket:2372 marisn]:
> This is an inverse bug of #1891
>
> Steps to reproduce:
> * Install Wingrass on a clean machine (without previous GRASS 7 install
or just remove AppData/Roaming/GRASS7 folder)
please test/see if installing winGRASS7 standalone on a fresh box creates
for you AppData/Roaming/GRASS7 folder!
Replying to [comment:3 hellik]:
> Replying to [ticket:2372 marisn]:
> > This is an inverse bug of #1891
> >
> > Steps to reproduce:
> > * Install Wingrass on a clean machine (without previous GRASS 7
install or just remove AppData/Roaming/GRASS7 folder)
>
> please test/see if installing winGRASS7 standalone on a fresh box
creates for you AppData/Roaming/GRASS7 folder!
>
> thanks
I didn't try it on 'clean' machine but I removed the GRASS7 folder and
demolocation in Documents/grassdata and everything was created and worked
fine for me.
Replying to [comment:3 hellik]:
> please test/see if installing winGRASS7 standalone on a fresh box
creates for you AppData/Roaming/GRASS7 folder!
Yes, it does. Still only for the user running the installer. I later
created a new user and there was no AppData/Roaming/GRASS7 folder with all
consequences. That explains why I observed it - in a computer lab
installations are done by the administrator but students are using their
normal user accounts. A small modification to the initial report, but it
is still valid.
Replying to [comment:4 annakrat]:
>
> I didn't try it on 'clean' machine but I removed the GRASS7 folder and
demolocation in Documents/grassdata and everything was created and worked
fine for me.
>
Actually having a minimized CMD window has another downside - GRASS is
printing error messages in the CMD window. Just observed with a new user -
no GRASS7 folder (see the previous comment), CMD window is minimized and
nothing happens - the reason: in the CMD is displayed an error message
"... python.exe cant open ... grass70.py: permission denied ..." (that is
the #2290) - still it displays why the simple proposal of Hellik in the
1st comment would be a good idea.