[GRASS-dev] Re: [GRASS GIS] #65: Starting up gis.m& hangs (probably on g.region)

GRASS GIS trac at osgeo.org
Thu May 8 15:35:11 EDT 2008


#65: Starting up gis.m& hangs (probably on g.region)
----------------------+-----------------------------------------------------
  Reporter:  pvbgis   |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect   |      Status:  reopened                 
  Priority:  major    |   Milestone:  6.3.1                    
 Component:  default  |     Version:  6.3.0 RCs                
Resolution:           |    Keywords:  wingrass                 
----------------------+-----------------------------------------------------
Changes (by pvbgis):

  * status:  closed => reopened
  * resolution:  worksforme =>
  * milestone:  6.4.0 => 6.3.1

Comment:

 Hi Markus

 Sorry for the late response.. and more sorry even to have to tell you it
 still doesn't work with 6.3.0 :-(.

 As an update, it hangs when starting up via the default GUI and via MSYS.
 However, I can do text-base startup. The g.region -p  command gives me the
 region information, no problem.

 However, when trying gis.m I get as far as the startup screen + output
 screen before it freezes. When killing the g.region everything seems to
 work fine, I can even view the region settings using the region menu, but
 the trouble starts again when trying to change the region or when trying
 to display a map. When killing the g.region process, the map does draw
 though, but even when trying to zoom, or refresh the map, same story
 again.

 I got an error message once (I couldn't replicate it). What it seem to
 show was the code defining a dialog:

 begin_dialog{g.regoin}{
 label{}
 desc{manages the boundary definition for the geographic region.}
 key{general}
 }
 add_flag 1{
 name{d}
 desc{Set from default regoin}
 answer 0
 label{}
 quisection{existing}
 }
 add_flag2{
 .
 .
 etc... till add_flag 12

 Curiously enough (for me anyway), even when the GUI is frozen, I can still
 use the g.region -p command in text-mode.

 Hope this helps in some way to pin down the problem

 Paulo

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


More information about the grass-dev mailing list