Tue, Apr 4 2006
10:48:23
|
|
Request created by guest
|
|
Subject: gis.m: hangs when displaying vectors
Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 2006-03-29
When displaying vectors with gis.m it goes into sort of an infinite loop, doesn't
display anything, and the output is being flooded with tones of messages. Impossible
to quit, have to kill.
Maciek
|
|
Wed, Apr 5 2006
10:10:14
|
|
Mail sent by msieczka
|
|
For an update: with today's CVS from a while ago this issue still applies.
Displaying vectors is impossible. Once I try displaying vector, gis.m Output
window goes crazy, gis.m freezes. After closing the gis.m window by force (not
always possible, sometimes have to use kill -9) there is a following output in
the terminal, if it is telling you anything:
PNG: GRASS_TRUECOLOR status: TRUE
PNG: collecting to file:
//home/grassdata/wro_gps_ll/PERMANENT/.tmp/quercus/11232.0.ppm,
GRASS_WIDTH=642, GRASS_HEIGHT=428
Graphics driver [gism] started
invalid command name ".gronsole.gronsole"
while executing
"$gronsole annotate $cmd [list gism running]"
(procedure "runcmd" line 4)
invoked from within
"runcmd "g.mremove -f region=mon_$mon ""
(procedure "MapCanvas::cleanup" line 6)
invoked from within
"MapCanvas::cleanup $mon $destroywin"
(command bound to event)
invalid command name ".gronsole.gronsole"
while executing
"$gronsole annotate $cmd [list gism running]"
(procedure "runcmd" line 4)
invoked from within
"runcmd "g.mremove -f region=mon_*""
(procedure "Gm::cleanup" line 29)
invoked from within
"Gm::cleanup $destroywin"
(command bound to event)
can't read "_widget(.#BWidgetClass#SelectColor,var)": no such element in array
while executing
"string length $_widget($path,var)"
(procedure "SelectColor::_destroy" line 4)
invoked from within
"SelectColor::_destroy .#BWidgetClass#SelectColor"
(command bound to event)
wrong # args: should be "Gm::cleanup destroywin"
while executing
"Gm::cleanup "
invoked from within
"if { "." == "."} { Gm::cleanup }"
(command bound to event)
Please note, that if I use "Zoom to current region" prior to displaying the
vector, it displays fine. But if I try to display my vector right after it's
added, there is a freeze as described.
Is anybody else having this bug?
Maciek
|
|
Fri, Apr 7 2006
10:53:37
|
|
Mail sent by msieczka
|
|
The error might be hard to spot. I can't reproduce it in all locations. So
here is a samll in which gis.m freezes.
Please download it at:
http://www.biol.uni.wroc.pl/sieczka/udostepnione/grass/wro_gps.tar.bz2
[39 KB].
And do the following to reproduce the error:
1. Enter PERMANENT in the location.
2. gis.m
3. Add a vector (eg. siatka_cross) to layers.
4. Press "Display active" in "Map Display 1" window.
5. See how gis.m freezes.
Maciek
|
|
Fri, Jun 23 2006
21:40:25
|
|
Status changed to resolved by mbarton
|
|
Fri, Jun 23 2006
21:40:25
|
|
Taken by mbarton
|
|
Fri, Jun 23 2006
21:40:25
|
|
Mail sent by mbarton
|
|
This was never reproduced consistently and seems to be resolved with current
version.
Michael |
|