On Sat, Oct 20, 2001 at 10:42:10AM -0700, Adam Rotaru wrote: > > On Fri, Oct 19, 2001 at 11:17:31PM -0700, Adam > Rotaru > wrote: > > > Today I upgraded my unstable install, and X > stopped > > > working. It includes X packages 4.1.0-8 (was -7) > > > Woohoo!!! So it's not just me. Alright, we gotta > make some comparisons > > here. 1) Did you reboot your computer at all after > the upgrade? 2) Are > > you running a font server? 3) Are you using an ext3 > filesystem? > > 1) Yes, the problem occured after a reboot. > 2) Yes, I run xfs. I tried it with and without, even > with xfs-ttf, no difference > 3) No, I'm using ext2. > > I do use xfonts-base, xfonts-75dpi, xfonts-100dpi, > xfonts-75dpi-transcoded, xfonts-100dpi-transcoded, > xfonts-biznet. > > I tries so many thing, reinstalled X packages and font > packages from testing (4.1.0-7), but still the same. > I strace-d xfs, but no clue. It reads the fonts.dir > and fonts.alias files, and then decided that the > directory is unreadable. > > Finally I managed the solve it this way: I noticed > Type1 and Speedo fond dirs are OK, copied all font > files from misc to Type1, run update-fonts-dir and > -alias a couple of time, (also copied > /etx/X11/fonts/misc/xfonts-base... to ../Type1). > First the effect was that Type1 got unreadable too, > but after several tries it worked, and got the 'fixed' > font from my hacked Type1 directory. I can't explain > what is going on. > It still can't read my misc, 75dpi, 100dpi > directories. > > BTW, both xfs and xfs-ttf give errors in syslog when I > start them, of the form: > > localhost xfs: ignoring font path element > /usr/lib/X11/fonts/misc/ (unreadable) > > --Adam
I am getting a similar problem. I am getting the message: Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Fatal server error: could not open default font 'fixed' any ideas on this one?? -- Stuart
