Re: Startx fails after updating my slink system!!!
Bdale Garbee wrote:
>
> In article <[🔎] Pine.HPP.3.96n.990107103534.2062B-100000@mlucom6.urz.uni-halle.de> you wrote:
> : On Thu, 7 Jan 1999, Christian T. Steigies wrote:
>
> :> > > Fatal server error:
> :> ^^^^^ how about this?
> :> > > could not open default font 'fixed'
> : I've seen it but I havn't any explanation for this. As I said I didn't
> : changed *ANY* package from the x11 section. After this failure I
> : purged xbase xserver-common xserver-mach64 xfonts-base xfonts-* and
> : reinstalled them to be sure. But the damn behaviour remains.
> : What could be the reason in failing to open the default font???
>
> I'm getting the same error trying to launch vncserver on a headless machine
> that didn't have any X packages at all until a couple of days ago, and now has
> a few from potato. Frankly, I can't find the file 'fixed' anywhere in the
> current Contents file, so I'm wondering if something has, indeed, gotten well
> and truly hosed in one of the X fonts packages?
I just ran into this yesterday as well -- apparently the fonts index in
fonts/misc isn't being updated ... or rather, I installed every font
package I could find, and that didn't fix the problem. Then, I went
back and ran mkfontdir by hand in the fonts/misc directory (after noting
the aliases there) and all was well. I think it may work for people
upgrading from hamm, and thus it may not have been seen much before.
But there is something amiss with xfonts-base, at least when installing
from scratch. (I'm going to wait a bit before filing this bug, if it
isn't already filed. If someone wants to investigate further and
confirm my hunch -- that mkfontdir isn't run properly or not at all --
then go ahead and file the bug.)
--
Anderson MacKay <mackay@rice.edu>
Reply to: