[GRASS5] RE: [bug #4140] (grass) Nviz doesn't start either from GUI or CLI

[Patton, Eric]

Maciek,

Perhaps there's another clue here; when I run nviz from CLI, I get:

GRASS 6.1.cvs (Cheticamp):~ > nviz elevation=Cheticamp98.5.ave.fill
Loading Data
Update elev null mask
Loading Data
translating colors from fp
*Segmentation fault*
(my emphasis)

Same error occurs with different rasters.

Hmmm....g.region -p gives:

GRASS 6.1.cvs (Cheticamp):~ > g.region -p
projection: 1 (UTM)
zone:       20
datum:      ** unknown (default: WGS84) **
ellipsoid:  wgs84
north:      5176119.54768
south:      5166572.33329
west:       628593.997416
east:       652873.00618
nsres:      9.92433928
ewres:      10.10362412
rows:       962
cols:       2403

Nothing too unusual here?

~ Eric.
 

-----Original Message-----
From: Maciek Sieczka via RT
To: epatton at nrcan.gc.ca
Sent: 3/6/2006 11:54 AM
Subject: [bug #4140] (grass) Nviz doesn't start either from GUI

On Mon, 6 Mar 2006 15:18:49 +0100
Markus Neteler <neteler at itc.it> wrote:

> On Mon, Mar 06, 2006 at 01:08:36PM +0100, Request Tracker wrote:
> > this bug's URL: http://intevation.de/rt/webrt?serial_num=4140
> >
------------------------------------------------------------------------
-
> > 
> > Subject: Nviz doesn't start either from GUI or command line in
> > 6.1cvs generic binary snapshot
> > 
> > Platform: GNU/Linux/x86
> > grass obtained from: Trento Italy site
> > grass binary for platform: Downloaded precompiled Binaries
> > GRASS Version: 6.1cvs binary 2006-03-04
> > 
> > Upon typing nviz on command line and selecting an elevation raster
> > in the nviz GUI, the green status bar builds to 100% but nothing
> > happens afterward. The message box area of the nviz GUI reads:
> > 
> > Update elev null mask
> > Loading Data
> > translating colors from fp
> > 
> > but no other errors are indicated. The exact same behavior is
> > observed if nviz is run from the display manager GUI.
>  
> Eric,
> 
> can you please post the related
> g.region -p
> ?

Also please try running your NVIZ command from the CLI and see what
happens. I just suppose there might be a segfault, which will be not
visible in the GUI output.

Maciek

---------------------