This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Could not open default font 'fixed'


Igor Pechtchanski wrote:

On Wed, 10 Mar 2004, Harold L Hunt II wrote:


Igor Pechtchanski wrote:


On Tue, 9 Mar 2004, Harold L Hunt II wrote:


Jeff,

Jeff Wolkove wrote:


I had the above error when I attempted to run startxwin.bat. The FAQ says
I should nudge the mailing list so here I am nudging. Does anyone know
of a fix for this error? Let me know if you need any further details.

Yes, we all know the answer, but it looks like it took me quite a long time to get around to updating the FAQ :)

There is now a detailed answer were there was previously a request to
nudge the mailing list by 2003-01-31... I hope I mistyped that as 2003
when it really should have been 2004.  It would be a little silly if it
really took longer than a year to revisit this issue.

http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof

Harold

Harold,


FWIW, you should be able to simply re-run any one of the
/etc/postinstall/XFree86-f*.sh.done scripts... :-)
     Igor

I don't understand, please explain. Harold


Harold,

First, all the postinstall scripts for XFree86-fnts, XFree86-f100,
XFree86-fscl, XFree86-fcyr, and XFree86-fenc are the same -- that's the
"any one of..." part.

Right.


Secondly, umount is already part of these scripts, and there should be no
need to reinstall the package just to re-run the postinstall script, hence
my suggestion (to just re-run the script from the command line).  Of
course, if any of the font files are corrupt then reinstallation *is*
needed.

Sure, umount is part of those scripts, but I want my instructions to work in all possible cases. I could think of some weird instances where someone had removed the postinstall scripts. In any case, I don't want to depend on those scripts being there.


The second part of your answer indicates that you don't fully understand the problem. See, it goes like this:

1) You have an invalid mount point in the registry that points to nowhere for /usr/X11R6/lib/X11/fonts.

2) You have setup.exe install the fonts packages.

3) setup.exe extracts the fonts packages according to the mount points, thus extracting the fonts packages to *nowhere*.

4) You do not actually have the files from the fonts packages on your system.

5) You have to kill the invalid mount point, then resinstall the fonts packages in order to actually get the files.

Weird, eh?

Harold


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]