[GRASS-user] problems with d.mon windows
Tyler Smith
tyler at plantarum.ca
Tue May 2 09:05:16 PDT 2017
Hi,
I've been having some problems interacting with graphics windows. I'm
using Grass version 7.2.0, installed from the Debian repository.
Starting from the command line this happens:
grass -text
GRASS 7.2.0 (ecozones):~ > d.mon start=wx0
GRASS 7.2.0 (ecozones):~ > Failed to import the site module
Traceback (most recent call last):
File "/usr/lib/python3.5/site.py", line 580, in <module>
main()
File "/usr/lib/python3.5/site.py", line 566, in main
known_paths = addusersitepackages(known_paths)
File "/usr/lib/python3.5/site.py", line 287, in addusersitepackages
user_site = getusersitepackages()
File "/usr/lib/python3.5/site.py", line 263, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File "/usr/lib/python3.5/site.py", line 253, in getuserbase
USER_BASE = get_config_var('userbase')
File "/usr/lib/python3.5/sysconfig.py", line 595, in get_config_var
return get_config_vars().get(name)
File "/usr/lib/python3.5/sysconfig.py", line 538, in get_config_vars
_init_posix(_CONFIG_VARS)
File "/usr/lib/python3.5/sysconfig.py", line 410, in _init_posix
from _sysconfigdata import build_time_vars
File "/usr/lib/python3.5/_sysconfigdata.py", line 6, in <module>
from _sysconfigdata_m import *
ImportError: No module named '_sysconfigdata_m'
At this point, GRASS thinks wx0 is running:
GRASS 7.2.0 (ecozones):~ > d.mon -l
List of running monitors:
wx0
But I can't see it anywhere.
Yesterday I was able to get wx0 started, but I got strange and
inconsistent errors with the d.what.vect interface (i.e., clicking on
the icon in the window then clicking on a vector object in the window).
I can't reproduce that anymore as now I can't even get the monitor
started.
Have I broken something? How can I get my map windows back?
Thanks,
Tyler
--
plantarum.ca
More information about the grass-user
mailing list