Philip Brown wrote:
On Mon, May 29, 2006 at 12:06:02PM -0400, The Wanderer wrote:
kdrill 6.4: by Philip Brown -- [EMAIL PROTECTED]
Starting up kdrill... please wait a while.
Warning: Unable to load any usable ISO8859 font
Error: Aborting: no font found
I am uncertain as to precisely what is going wrong; I have not been
able to discover even what specific thing kdrill is trying to do -
say, open a file containing a particular font - which is failing.
(My last attempt to do so culminated in my upgrading libxaw7, which
removed a segfault but did not fix the problem.)
The error you are seeing, does not come from kdrill. it comes from
the low-level libraries. (libxaw).
...somehow that doesn't surprise me. (I *knew* I should have left out
that strace log...)
I dont think this is a bug in kdrill.
That's entirely possible... at best, it would seem to be a
package-dependency problem, such that a particular font which kdrill
needs to be installed isn't.
What this sort of error usually comes from, is when the X libraries
cannot even load the basic font "fixed" or some such.
...where would that font be found? The only things I find by 'locate -i
fixed | grep -i font' are /usr/share/consolefonts/grfixed.psf.gz and
eight various /usr/share/qte3/lib/fonts/fixed_*.qpf, none of which look
like anything I'd recognize as being X-font-related; I'm not sure what
I'd want to search on in order to find out what package would be
expected to contain the relevant font(s), much less where I'd have to
put them in order to have them load properly.
(For that matter, is there an explanation anywhere of what exactly the
various -*-*-font-* style font names mean, and what files they're
talking about? I've never been able to make the least bit of sense out
of them, and this time it looks like it's actually preventing me from
understanding what's going on somewhere.)
I'd kind of expect that if the X libraries were unable to load even the
most basic of fonts, other programs (say, xterm?) might not work
correctly - and everything else I've tried certainly seems to be
functioning as expected... but I imagine I'm just making an unwarranted
assumption somewhere.
I dont see how kdrill could stop that from happening.
You might want to remove $HOME/.kdrill, though, just to avoid any old
resource definition conflicts
Did that (and, temporarily, did the same with
/etc/X11/app-defaults/KDrill, where the font defaults are specified),
with no visible change.
--
The Wanderer
Warning: Simply because I argue an issue does not mean I agree with any
side of it.
Secrecy is the beginning of tyranny.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
