Re: X.org: Fatal server error [Solved]
On Fri, Feb 15, 2008 at 01:44:13PM +0100, Harald Weis wrote: Fatal server error: could not open default font 'fixed' I've learned two lessons. 1. As a constant user of portupgrade since ages, this time, before and after the xorg-upgrade procedure, I have carelessly omitted the `-R' option. No wonder that required packages were missing. 2. The `pkg_info -L' check does not certify that the file is actually in its place: between two checks I have removed all the empty fontfiles in misc/, thereby getting rid again of fonts.alias as well :-( and forgot about it. Now I know that the server is indeed looking first for the `fixed' line in fonts.alias. If he does not find it, he complains no matter how many fixed fonts are stored in misc/. The fact that misc/ and three other directories in that machine were only populated with a large number of empty fontfiles remains weird though. Thanks again for every reply, on-list and off-list. HW -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error [Solved]
in message [EMAIL PROTECTED], wrote Harald Weis
thusly...
2. The `pkg_info -L' check does not certify that the file is
actually in its place
To actually verify the existence of the files, stat(2) them somehow
(will work at least in bourne like shells) ...
pkg_info -L port-name \
| awk '!/^(Info|Files:|$)/ { print $0 }' \
| xargs ls -l /dev/null
... above will only show the error messages for missing files of a
port|package.
- Parv
--
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
On Mon, Feb 11, 2008 at 12:29:13PM -0800, Joseph Olatt wrote: On Mon, Feb 11, 2008 at 10:37:02AM +0100, Harald Weis wrote: On Sun, Feb 10, 2008 at 06:13:33PM -0800, Joseph Olatt wrote: On Thu, Feb 07, 2008 at 01:44:03PM +0100, Harald Weis wrote: I would check and see if you have the following packages installed: 1. font-misc-misc 2. font-cursor-misc They are installed alright, like all other packages containing the pattern ``font'' in their name. If font-misc-misc and font-cursor-misc are installed, I would do the following: 1. Check /usr/local/lib/X11/fonts/misc directory to see if there are font files there. In my case, that is where the fonts from package font-misc-misc and font-cursor-misc got installed. (pkg_info -L font-misc-misc-1.0.0 would tell you where the fonts got installed.) 2. Check the xorg.conf (/etc/X11/xorg.conf for me) to see if you have a section similar to the following: Section Files RgbPath /usr/local/share/X11/rgb ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection If the line 'FontPath /usr/local/lib/X11/fonts/misc/' does not exist, you could get the fixed font error. Finally, I've found the real reason for the empty fonts.dir file in misc/ (and 100dpi/, 75dpi, cyrillic): a lot of .pcf.gz files were indeed present, but I've not spotted that they were empty ! Shame on me. They must have been created (time stamp: Feb 3) during the xorg-upgrade procedure (described in the /usr/ports/UPDATING), but all empty, God knows why. misc/ is now populated with all the fonts created by the following packages: font-arabic-misc-1.0.0 font-cursor-misc-1.0.0 font-daewoo-misc-1.0.0 font-dec-misc-1.0.0 font-isas-misc-1.0.0 font-jis-misc-1.0.0 font-micro-misc-1.0.0 font-misc-cyrillic-1.0.0 font-misc-ethiopic-1.0.0 font-misc-meltho-1.0.0_1 font-misc-misc-1.0.0 font-mutt-misc-1.0.0 font-schumacher-misc-1.0.0 font-sony-misc-1.0.0 font-sun-misc-1.0.0 xorg-fonts-miscbitmaps-7.3 (meta package: no output from `pkg_info -L') The fonts.dir file contains now exactly 340 `fixed' fonts. There is no owner or permission problem whatsoever. And still, whether I follow strictly the method described in the Handbook or whether I use my own method with xinit and $HOME/.xinitrc the X server makes always the same complaint: Fatal server error: could not open default font 'fixed' The output of 'truss -fae startx' does not show why on earth the server cannot open the default font. It seems hopeless. I've never encountered such a bug. Is there really no other solution than the Windows-approach: Reinstall xorg from scratch ? Thanks in advance for every other idea. Harald -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
On Mon, Feb 11, 2008 at 12:29:13PM -0800, Joseph Olatt wrote: On Mon, Feb 11, 2008 at 10:37:02AM +0100, Harald Weis wrote: On Sun, Feb 10, 2008 at 06:13:33PM -0800, Joseph Olatt wrote: On Thu, Feb 07, 2008 at 01:44:03PM +0100, Harald Weis wrote: A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. 1. Check /usr/local/lib/X11/fonts/misc directory to see if there are font files there. In my case, that is where the fonts from package font-misc-misc and font-cursor-misc got installed. (pkg_info -L font-misc-misc-1.0.0 would tell you where the fonts got installed.) 2. Check the xorg.conf (/etc/X11/xorg.conf for me) to see if you have a section similar to the following: Section Files RgbPath /usr/local/share/X11/rgb ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection If the line 'FontPath /usr/local/lib/X11/fonts/misc/' does not exist, you could get the fixed font error. I've done all these checks at the very beginning. The only remaining problem was the empty fonts.dir file which fully explains to my mind the fatal server error. I then ran mkfontdir and saw that this command does indeed generate an empty fonts.dir file on the bad machine where everything else seems so utterly correct. What I haven't done yet on the bad box (because it's not on my desk and its external, stupid, ISP router does not let me in via SSH) is to copy my fonts.dir file to it. Just for fun to see what happens. I'll do that tomorrow... In the last resort, I shall portupgrade -fP -o x11/xorg xorg But I hate the idea, it's so Unix-unlike, isn't it ? Harald -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. I would check and see if you have the following packages installed: 1. font-misc-misc 2. font-cursor-misc They are installed alright, like all other packages containing the pattern ``font'' in their name. In the meantime, following an off-list advice, I've used truss(1). I've got now nice truss.out files for two machines (same release): mine which is good and the other machine (in fact a desktop as well) which has the bug. The trouble is that I'm unable to interpret the difference. For example: Every line in the bad truss.out file is prefixed with ``2682: ''. Perhaps a line number? But of which file ? Couldn't find anything within the sources of truss or mkfontscale. No reply yet from the maintainer for mkfontscale [EMAIL PROTECTED] First, I'm replying for convenience to two off-list remarks: I've created 4 truss.out files, 2 on the bad box, 2 on the good one, using the following 2 commands (under root in /usr/local/lib/X11/fonts): truss -o truss.out mkfontdir misc/ truss -fae -o truss-fae.out mkfontdir misc/ After renaming I've got: truss.bad, truss.good, truss-fae.bad, truss-fae.good truss-fae.bad is the _only_ file all lines of which are prefixed with ``2682: ''. All lines of all other files don't have such a prefix. I cannot check for the time being whether this corresponds to a pid. The bad box is at the other end of the town. Second, is there nobody (more competent than me) out there who would accept receiving and looking into e.g. truss-fae.bad.bz2 (12kB) and truss-fae.good.bz2 (18kB) ? You know I'm just asking for the very very obvious thing which should take not more than 5 minutes for an experienced person. Thank you in advance. Harald -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
On Mon, Feb 11, 2008 at 10:37:02AM +0100, Harald Weis wrote: On Sun, Feb 10, 2008 at 06:13:33PM -0800, Joseph Olatt wrote: On Thu, Feb 07, 2008 at 01:44:03PM +0100, Harald Weis wrote: This is the message (without the stars) I get on a laptop after a fresh install of FreeBSD 6.2-RELEASE i386 (previously 6.0). Searching the archives, I found two reasons which do not apply for me: 1. xorg-fonts-miscbitmaps-7.2 is properly installed 2. the same is true for font-alias-1.0.1 A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. I would check and see if you have the following packages installed: 1. font-misc-misc 2. font-cursor-misc They are installed alright, like all other packages containing the pattern ``font'' in their name. If font-misc-misc and font-cursor-misc are installed, I would do the following: 1. Check /usr/local/lib/X11/fonts/misc directory to see if there are font files there. In my case, that is where the fonts from package font-misc-misc and font-cursor-misc got installed. (pkg_info -L font-misc-misc-1.0.0 would tell you where the fonts got installed.) 2. Check the xorg.conf (/etc/X11/xorg.conf for me) to see if you have a section similar to the following: Section Files RgbPath /usr/local/share/X11/rgb ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection If the line 'FontPath /usr/local/lib/X11/fonts/misc/' does not exist, you could get the fixed font error. snip ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
On Sun, Feb 10, 2008 at 06:13:33PM -0800, Joseph Olatt wrote: On Thu, Feb 07, 2008 at 01:44:03PM +0100, Harald Weis wrote: This is the message (without the stars) I get on a laptop after a fresh install of FreeBSD 6.2-RELEASE i386 (previously 6.0). Searching the archives, I found two reasons which do not apply for me: 1. xorg-fonts-miscbitmaps-7.2 is properly installed 2. the same is true for font-alias-1.0.1 A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. I would check and see if you have the following packages installed: 1. font-misc-misc 2. font-cursor-misc They are installed alright, like all other packages containing the pattern ``font'' in their name. In the meantime, following an off-list advice, I've used truss(1). I've got now nice truss.out files for two machines (same release): mine which is good and the other machine (in fact a desktop as well) which has the bug. The trouble is that I'm unable to interpret the difference. For example: Every line in the bad truss.out file is prefixed with ``2682: ''. Perhaps a line number? But of which file ? Couldn't find anything within the sources of truss or mkfontscale. No reply yet from the maintainer for mkfontscale [EMAIL PROTECTED] Thanks for any help, Harald -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
On Thu, Feb 07, 2008 at 01:44:03PM +0100, Harald Weis wrote: Hello All, *** Fatal server error: *** could not open default font 'fixed' This is the message (without the stars) I get on a laptop after a fresh install of FreeBSD 6.2-RELEASE i386 (previously 6.0). Searching the archives, I found two reasons which do not apply for me: 1. xorg-fonts-miscbitmaps-7.2 is properly installed 2. the same is true for font-alias-1.0.1 A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. xorg-7.2, xorg-fonts-7.2 and all the rest are properly installed. The instructions of the 20070519-section in UPDATING have successfully been executed. Fortunately, lynx and elinks work alright. Needless to say that I've portupgrade'd both mkfontdir and mkfontscale with the '-f' option, and that my ports tree is portsnap'ed up-to-date. What else could I do to find the bug ? Thanks in advance, Harald I would check and see if you have the following packages installed: 1. font-misc-misc 2. font-cursor-misc They are in: /usr/ports/x11-fonts regards, joseph ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
X.org: Fatal server error
Hello All, *** Fatal server error: *** could not open default font 'fixed' This is the message (without the stars) I get on a laptop after a fresh install of FreeBSD 6.2-RELEASE i386 (previously 6.0). Searching the archives, I found two reasons which do not apply for me: 1. xorg-fonts-miscbitmaps-7.2 is properly installed 2. the same is true for font-alias-1.0.1 A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. xorg-7.2, xorg-fonts-7.2 and all the rest are properly installed. The instructions of the 20070519-section in UPDATING have successfully been executed. Fortunately, lynx and elinks work alright. Needless to say that I've portupgrade'd both mkfontdir and mkfontscale with the '-f' option, and that my ports tree is portsnap'ed up-to-date. What else could I do to find the bug ? Thanks in advance, Harald ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
