Re: Xprint startup errors

[Jonas Gall <jogall@gmail.com>]

David Baron wrote:
> Possibly due to some inodes that got deleted after an improper shutdown, 
> possibly due to an Xorg backport which in the end was not used, I am now 
> getting the following errors on Xprint start:
> 
> No matching visual for __GLcontextMode with visual class = 0 (32775), 
> nplanes=8
No error. Just the message that the GL engine in the XPrint server
found a visual mismatch.

>
> Could not init font path element /usr/share/fonts/truetype/commercial, 
> removingfrom list!
> Could not init font path element /usr/share/fonts/ttf, removing from list!
> Could not init font path element /usr/share/fonts, removing from list!
> Could not init font path element /usr/share/fonts/afms, removing from list!
> Could not init font path element /usr/share/fonts/afms/adobe, removing from 
> list!
> Could not init font path element /usr/X11R6/lib/X11/fonts, removing from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/PEX, removing from 
> list!
This means: Broken or missing fonts.dir. Some Debian font packages
ship broken fonts.dir entries. Watch for font filenames with spaces,
too.

> 
> I reinstalled fonts, refreshed the cache. A cyrillic font that was on this 
> list seems now OK but these remain. (I doubt if I actually use any of this, 
> but) How to straighten this out?
Did you refresh fonts.scale and then font.dir? 
# cd /usr/share/fontxyz
# rm -f fonts.dir fonts.scale
# mkfontscale
# mkfontdir
usually does the trick for me

Jonas
-- 
 .-.   .-.    Yes, I am an agent of Satan, but my duties
(_  \ /  _)   are largely ceremonial.
     |
     |        jogall@gmail.com