any idea what to change?
May I (as a user) do something or do I need a superuser?
Should we reinstall a newer cvs?
I there a mirror somewhere where we can find ready-to-use and up-to-date debian-packeges?
any idea what to change?
May I (as a user) do something or do I need a superuser?
Should we reinstall a newer cvs?
Apparently stroke fonts fail -- do things like d.legend or d.text print
text? 'unset GRASS_FONT' ?
self compilied? from original source or debian build?
I there a mirror somewhere where we can find ready-to-use and
up-to-date debian-packeges?
Hi all,
I use in university a cvs of GRASS 6.3 in debian.
The other day I got a problems with fonts in i.class and today the same
using i.points.
There are no words on the buttons. onlay grey beams (Balken)
in Konsole I got the message
WARNING: unable to open font map '/usr/lib/grass/fonts/.hmp': No such
file
Sorry, meant to reply to this earlier. The usual solution for this is to run:
g.mkfontcap -o
to re-generate the font file.
Did you compile GRASS yourself? Were the compiled binaries moved to some other location in the filesystem without running "make install" - if so, the locations of the GRASS built-in fonts in the fontcap file would be wrong and it needs to be regenerated.
On Jan 30, 2008 2:29 PM, Paul Kelly <paul-grass@stjohnspoint.co.uk> wrote:
On Sat, 26 Jan 2008, Philipp Steigenberger wrote:
...
> WARNING: unable to open font map '/usr/lib/grass/fonts/.hmp': No such
> file
Sorry, meant to reply to this earlier. The usual solution for this is to
run:
g.mkfontcap -o
to re-generate the font file.
Did you compile GRASS yourself? Were the compiled binaries moved to some
other location in the filesystem without running "make install" - if so,
the locations of the GRASS built-in fonts in the fontcap file would be
wrong and it needs to be regenerated.
Paul,
any chance to catch this warning and run g.mkfontcap -o automatically
if needed? That people move binaries around will happen regularly.
HI Paul,
the GRASS cvs I didn’t compile by myself. It was installed into the system. This days I couldn’t run g.mkfontcap, cause I hadn’t the permission.
Now that I have the superuser rights I already compiled GRASS svn - without makeinstall;
I’ll try the g.mkfontcap tomorrow with the cvs GRASS just to look if it will work.
cheers
Philipp
Paul Kelly schrieb:
On Sat, 26 Jan 2008, Philipp Steigenberger wrote:
Hi all,
I use in university a cvs of GRASS 6.3 in debian.
The other day I got a problems with fonts in i.class and today the same
using i.points.
There are no words on the buttons. onlay grey beams (Balken)
in Konsole I got the message
WARNING: unable to open font map ‘/usr/lib/grass/fonts/.hmp’: No such
file
Sorry, meant to reply to this earlier. The usual solution for this is to run:
g.mkfontcap -o
to re-generate the font file.
Did you compile GRASS yourself? Were the compiled binaries moved to some other location in the filesystem without running “make install” - if so, the locations of the GRASS built-in fonts in the fontcap file would be wrong and it needs to be regenerated.
> > WARNING: unable to open font map '/usr/lib/grass/fonts/.hmp': No such
> > file
>
> Sorry, meant to reply to this earlier. The usual solution for this is to
> run:
> g.mkfontcap -o
> to re-generate the font file.
>
> Did you compile GRASS yourself? Were the compiled binaries moved to some
> other location in the filesystem without running "make install" - if so,
> the locations of the GRASS built-in fonts in the fontcap file would be
> wrong and it needs to be regenerated.
Paul,
any chance to catch this warning and run g.mkfontcap -o automatically
if needed? That people move binaries around will happen regularly.
There are potentially other things which can cause it, and we don't
want to overwrite the fontcap file if it has been edited by the user.
the GRASS cvs I didn't compile by myself. It was installed into the
system. This days I couldn't run g.mkfontcap, cause I hadn't the permission.
Now that I have the superuser rights I already compiled GRASS svn -
without makeinstall;
I'll try the g.mkfontcap tomorrow with the cvs GRASS just to look if it
will work.
If you don't have permission to modify etc/fontcap, you can use e.g.
"g.mkfontcap -s > ~/.gfontcap" to create a personal copy then use e.g.
"export GRASS_FONT_CAP=$HOME/.gfontcap" to make GRASS use that file
instead of the system copy.
the GRASS cvs I didn't compile by myself. It was installed into the
system. This days I couldn't run g.mkfontcap, cause I hadn't the permission.
Now that I have the superuser rights I already compiled GRASS svn -
without makeinstall;
I'll try the g.mkfontcap tomorrow with the cvs GRASS just to look if it
will work.
If you don't have permission to modify etc/fontcap, you can use e.g.
"g.mkfontcap -s > ~/.gfontcap" to create a personal copy then use e.g.
"export GRASS_FONT_CAP=$HOME/.gfontcap" to make GRASS use that file
instead of the system copy.
Glynn,
In this way it works. But do I have to put this
into the .grass.bashrc, that don’t have to export it every time I open a new bash?
(
I opened a new bash and got there:
GRASS:~/gw$ echo $GRASS_FONT_CAP
…
GRASS:~/gw$
)
For my new GRASS svn it doesn’t matter, but for me its in general interesting to know how to work with export in such cases. Is there a file where the bash saves all the env-variables and how to influence it.
> If you don't have permission to modify etc/fontcap, you can use e.g.
> "g.mkfontcap -s > ~/.gfontcap" to create a personal copy then use e.g.
> "export GRASS_FONT_CAP=$HOME/.gfontcap" to make GRASS use that file
> instead of the system copy.
>
>
Glynn,
In this way it works. But do I have to put this
into the .grass.bashrc, that don't have to export it every time I open a
new bash?
You only need to run g.mkfontcap once (or when you add new fonts), but
the "export" statement should go into ~/.grass.bashrc (or some other
shell startup script).
(
I opened a new bash and got there:
GRASS:~/gw$ echo $GRASS_FONT_CAP
....
GRASS:~/gw$
)
For my new GRASS svn it doesn't matter, but for me its in general
interesting to know how to work with /export/ in such cases. Is there a
file where the bash saves all the env-variables and how to influence it.
- But probably this is off-topic...
bash won't save environment variables, but it reads a number of files
at startup. The details are all in the bash(1) manpage, but some
subset of the following files will be read when an interactive shell
is started: