[GRASS GIS] #570: startup problem with standalone GRASS install

[GRASS GIS]

#570: startup problem with standalone GRASS install
-------------------------+--------------------------------------------------
 Reporter:  timmie       |       Owner:  [hidden email]
     Type:  defect       |      Status:  new                      
 Priority:  normal       |   Milestone:  6.4.0                    
Component:  default      |     Version:  unspecified              
 Keywords:               |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------
 please see attachments of error when the program is started with GRASS
 Icon

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  [hidden email]
      Type:  defect        |      Status:  new                      
  Priority:  normal        |   Milestone:  6.4.0                    
 Component:  default       |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:                          
  Platform:  MSWindows XP  |         Cpu:  Unspecified              
---------------------------+------------------------------------------------
Changes (by neteler):

  * platform:  Unspecified => MSWindows XP
  * version:  unspecified => 6.4.0 RCs

Comment:

 See also http://trac.osgeo.org/osgeo4w/ticket/82

 Please specify the Windows version

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570#comment:1>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  [hidden email]
      Type:  defect        |      Status:  new                      
  Priority:  normal        |   Milestone:  6.4.0                    
 Component:  default       |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:                          
  Platform:  MSWindows XP  |         Cpu:  Unspecified              
---------------------------+------------------------------------------------
Comment (by timmie):

 * Windows XP
 * Python is already installed (PythonXY)

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570#comment:2>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  [hidden email]
      Type:  defect        |      Status:  new                      
  Priority:  normal        |   Milestone:  6.4.0                    
 Component:  Installation  |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:                          
  Platform:  MSWindows XP  |         Cpu:  Unspecified              
---------------------------+------------------------------------------------
Changes (by hamish):

  * component:  default => Installation

Comment:

 I expect an incompatibility with the PythonXY installation.
 (ie pyXY is built without some needed library function)

 can you install a secondary python install (generic 2.5) to run with
 grass?

 what version of pythonXY? is it supposed to be a full python install +
 scientific tools, or has it dumped normal python things it thinks a
 scientist won't use?

 from the dos box screenshot it looks like you try with grass 6.4.0rc4.

 can you translate the error messages into english for those of us  too
 ignorant to understand?


 cheers,
 Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:3>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  [hidden email]
      Type:  defect        |      Status:  new                      
  Priority:  normal        |   Milestone:  6.4.0                    
 Component:  Installation  |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:                          
  Platform:  MSWindows XP  |         Cpu:  x86-32                  
---------------------------+------------------------------------------------
Changes (by timmie):

  * cpu:  Unspecified => x86-32

Comment:

 > I expect an incompatibility with the PythonXY installation. (ie pyXY is
 built without some needed library function)
 You may have a look at the standard plugins of PythonXY here:
 http://www.pythonxy.com/standard.php

 It's really neat for straight off installation for science.

 > can you install a secondary python install (generic 2.5) to run with
 grass?
 Just bare Python 2.5?
 I can try as long as it does not spoil my sys.path
 More an more FOSS programs have python. On windows, everyone installs its
 own version of python into the programs directory...

 > what version of pythonXY?
 latest. 2.1.12

 > is it supposed to be a full python install + scientific tools,
 Yes.

 > or has it dumped normal python things it thinks a scientist won't use?
 I don't think so.

 > from the dos box screenshot it looks like you try with grass 6.4.0rc4.
 Yes. from the standalone installer.

 > can you translate the error messages into english for those of us too
 ignorant to understand?
 I will try:
 https://trac.osgeo.org/grass/attachment/ticket/570/bug_grass.jpg
 => prozedureinsprungspunkt: starting point of procedure
 => wurde in der DLL [...] nicht gefunden : was not found in the DLL [...]

 https://trac.osgeo.org/grass/attachment/ticket/570/bug_grass2.jpg
 => DLL Load failed: Die angegebene Prozedur wurde nicht gefunden :  DLL
 Load failed: the procedure called was not found

 Is there a list of python modules that are required for GRASS to run?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:4>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  [hidden email]
      Type:  defect        |      Status:  new                      
  Priority:  normal        |   Milestone:  6.4.0                    
 Component:  Installation  |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:                          
  Platform:  MSWindows XP  |         Cpu:  x86-32                  
---------------------------+------------------------------------------------
Comment (by timmie):

 I've just seen that GRASS also conatins a menu item for "Old Gui" very
 good. I would like to see these choices (GUI, OLd GUI, command line) as
 well in the OSGEO4W install...

 I check and GRASS seems to run with the old GUI.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:5>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  [hidden email]
      Type:  defect        |      Status:  new                      
  Priority:  normal        |   Milestone:  6.4.0                    
 Component:  Installation  |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:                          
  Platform:  MSWindows XP  |         Cpu:  x86-32                  
---------------------------+------------------------------------------------
Comment (by timmie):

 As we suppose that this is a python import error:
 I would suggest that there are axceptions with error messages added to the
 points where python needs some distinct modules.


 Disclaimer: I never looked at the code of the Python GUI

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:6>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  [hidden email]
      Type:  defect        |      Status:  new                      
  Priority:  normal        |   Milestone:  6.4.0                    
 Component:  Installation  |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:                          
  Platform:  MSWindows XP  |         Cpu:  x86-32                  
---------------------------+------------------------------------------------
Comment (by cnielsen):

 Related errors have been posted elsewhere. The path given in the error
 "C:\Programs\GIS..." is from my system where I built the installer.
 Somewhere this path is getting saved even when the installer is supposed
 to be generic. As I mentioned in other posts, if anyone can tell me how to
 fix this I will gladly do so, I'm just a packager :).

 -Colin

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570#comment:7>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie  
      Type:  defect        |      Status:  assigned
  Priority:  normal        |   Milestone:  6.4.0    
 Component:  Installation  |     Version:  6.4.0 RCs
Resolution:                |    Keywords:          
  Platform:  MSWindows XP  |         Cpu:  x86-32  
---------------------------+------------------------------------------------
Changes (by neteler):

 * cc: [hidden email] (added)

Comment:

 Timmie,

 if you change "Assigned to:" to yourself, then no more email posting to
 grass-dev happens. Not sure if it is what you want.

 Markus

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:11>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie  
      Type:  defect        |      Status:  assigned
  Priority:  normal        |   Milestone:  6.4.0    
 Component:  Installation  |     Version:  6.4.0 RCs
Resolution:                |    Keywords:          
  Platform:  MSWindows XP  |         Cpu:  x86-32  
---------------------------+------------------------------------------------
Comment (by timmie):

 I tried

 etc/Init.bat
 lines 120ff.

 ::set
 PYTHONPATH=%PYTHONPATH%;%WINGISBASE%\etc\python;%WINGISBASE%\etc\wxpython
 set PYTHONPATH=%WINGISBASE%\etc\python;%WINGISBASE%\etc\wxpython

 But no success.

 there is not %PYTHONPATH% in Grass.bat

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:12>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie  
      Type:  defect        |      Status:  assigned
  Priority:  normal        |   Milestone:  6.4.0    
 Component:  Installation  |     Version:  6.4.0 RCs
Resolution:                |    Keywords:          
  Platform:  MSWindows XP  |         Cpu:  x86-32  
---------------------------+------------------------------------------------
Comment (by timmie):

 If I set in
 grass64.bat
 set PYTHONHOME=C:\Programme\pythonxy\python

 I get at least the wxpython startup window.
 After selecting a mapset and pressing enter, the GUI crashes again.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:13>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie  
      Type:  defect        |      Status:  closed  
  Priority:  normal        |   Milestone:  6.4.0    
 Component:  Installation  |     Version:  6.4.0 RCs
Resolution:  fixed         |    Keywords:          
  Platform:  MSWindows XP  |         Cpu:  x86-32  
---------------------------+------------------------------------------------
Changes (by timmie):

  * status:  assigned => closed
  * resolution:  => fixed

Comment:

 I got it fixed on my computer.
 It was a problem with the win32 packages for python.

 After copying them over from
 c:\Programme\pythonxy\python\Lib\site-packages\win32\
 c:\Programme\pythonxy\python\Lib\site-packages\win32com\
 c:\Programme\pythonxy\python\Lib\site-packages\win32comext\
  everything works.

 The GUI is really nice and fast. congratulations to thos who made it.

 Where can upload a ZIP for verification?
 I would like to know whether this is specific for my setup or others may
 have the same problem.
 I can suppose that peaple working a lot with Python may even have 3 python
 installs:
 python25, python26, python3000

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:14>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie  
      Type:  defect        |      Status:  closed  
  Priority:  normal        |   Milestone:  6.4.0    
 Component:  Installation  |     Version:  6.4.0 RCs
Resolution:  fixed         |    Keywords:          
  Platform:  MSWindows XP  |         Cpu:  x86-32  
---------------------------+------------------------------------------------
Comment (by timmie):

 Since maxium file size was reached I uploaded to:
 http://www.datafilehost.com/download-5ef16604.html

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:15>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie  
      Type:  defect        |      Status:  reopened
  Priority:  normal        |   Milestone:  6.4.0    
 Component:  Installation  |     Version:  6.4.0 RCs
Resolution:                |    Keywords:          
  Platform:  MSWindows XP  |         Cpu:  x86-32  
---------------------------+------------------------------------------------
Changes (by timmie):

  * status:  closed => reopened
  * resolution:  fixed =>

Comment:

 One small issue:
 When GRASS is started from the menu shortcut, there is still an empty dos
 CLI in the background.

 I think there should somewhere be called
 pythonw.exe instead of python.exe

 But I do not know how to correct this as I do not understand the
 interactions between
 Grass64.bat -wxpython
 and
 etc/Init.bat

 Maybe someone can help here?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:16>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[Moritz Lennert]

On 05/05/09 15:55, GRASS GIS wrote:

> #570: startup problem with standalone GRASS install
> ---------------------------+------------------------------------------------
>   Reporter:  timmie        |       Owner:  timmie  
>       Type:  defect        |      Status:  reopened
>   Priority:  normal        |   Milestone:  6.4.0    
>  Component:  Installation  |     Version:  6.4.0 RCs
> Resolution:                |    Keywords:          
>   Platform:  MSWindows XP  |         Cpu:  x86-32  
> ---------------------------+------------------------------------------------
> Changes (by timmie):
>
>   * status:  closed => reopened
>   * resolution:  fixed =>
>
> Comment:
>
>  One small issue:
>  When GRASS is started from the menu shortcut, there is still an empty dos
>  CLI in the background.

AFAIK, this DOS CLI is necessary for the functioning of GRASS, notably
running the temp file cleaning operations at the end. So, until we have
reengineered the Windows startup logic, I don't think we can get rid of it.

Moritz
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[Glynn Clements]

Moritz Lennert wrote:

> >  When GRASS is started from the menu shortcut, there is still an empty dos
> >  CLI in the background.
>
> AFAIK, this DOS CLI is necessary for the functioning of GRASS, notably
> running the temp file cleaning operations at the end. So, until we have
> reengineered the Windows startup logic, I don't think we can get rid of it.

If enough users are likely to want to use the wxPython GUI as the main
interface, I'd consider adding a Python-based startup as an
alternative to grassXX[.bat] and Init.{sh,bat}.

This should be invoked via pythonw on Windows, and should redirect
std{out,err} to files. Also, if GISBASE isn't already defined, set it
from a registry key.

A command-line-only interface is of relatively little use on Windows,
due to the absence of monitors.

--
Glynn Clements <[hidden email]>
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[Markus Neteler]

On Wed, May 6, 2009 at 11:58 AM, Glynn Clements
<[hidden email]> wrote:

>
> Moritz Lennert wrote:
>
>> >  When GRASS is started from the menu shortcut, there is still an empty dos
>> >  CLI in the background.
>>
>> AFAIK, this DOS CLI is necessary for the functioning of GRASS, notably
>> running the temp file cleaning operations at the end. So, until we have
>> reengineered the Windows startup logic, I don't think we can get rid of it.
>
> If enough users are likely to want to use the wxPython GUI as the main
> interface, I'd consider adding a Python-based startup as an
> alternative to grassXX[.bat] and Init.{sh,bat}.

Yes, this would help to sort out a series of problems.

Markus
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[hamish-2]

>  When GRASS is started from the menu shortcut, there is still an
> empty dos CLI in the background.

fwiw there's a bug in the current osgeo4w 6.4.0svn package whereas
that empty DOS box is actually the GRASS terminal prompt but stalled
until the GUI exits. (GUI doesn't background)
see http://trac.osgeo.org/osgeo4w/ticket/83

also note in Colin's stand-alone 6.4.0svn installer the DOS box is now
automatically minimized.


Hamish



     

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[hamish-2]

Glynn:
> A command-line-only interface is of relatively little use on Windows,
> due to the absence of monitors.

it is still useful for batch scripting purposes, which is one of our great
strengths.


fwiw, currently the OSGeo4W installer gives 3 startup options:
 TclTk, Text, and wxPython

the stand-alone installer gives: GRASS-wx (no term), GRASS-wx with a msys
terminal, GRASS DOS box only, and GRASS tcltk (no term)


Hamish



     

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie  
      Type:  defect        |      Status:  reopened
  Priority:  normal        |   Milestone:  6.4.0    
 Component:  Installation  |     Version:  6.4.0 RCs
Resolution:                |    Keywords:          
  Platform:  MSWindows XP  |         Cpu:  x86-32  
---------------------------+------------------------------------------------
Comment (by hamish):

 timmie wrote:
 > Where can upload a ZIP for verification?

 verification of what? what's in the ZIP file?

 > One small issue: When GRASS is started from the menu shortcut,
 > there is still an empty dos CLI in the background.

 as discussed on grass-dev,
  - in the OSGeo4W installer you get a grass terminal session in a dos box
 using the wx gui
  - in the OSGeo4W installer you get a blank dos box when using the tcltk
 gui until you exit the gui when it becomes a grass terminal session (patch
 in osgeo4w bug # 83 http://trac.osgeo.org/osgeo4w/ticket/83)
  - in Colin's stand-alone installer the empty dos box is now minimized by
 default. maybe some valuable error messages could end up there; maybe
 Glynn will rewrite grass.bat into a general launch_grass.py.


 Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:17>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev