msttcorefonts install breaks FC6 printing, help!
Craig White
craig at tobyhouse.com
Thu Jan 25 18:24:24 UTC 2007
On Thu, 2007-01-25 at 11:00 -0500, Gene Heskett wrote:
> On Thursday 25 January 2007 07:13, Craig White wrote:
> >On Thu, 2007-01-25 at 03:01 -0500, Gene Heskett wrote:
> >> Greetings;
> >>
> >> I installed the msttcorefonts-2.0.1-noarch.rpm 2 nights ago, and now
> >> see that amanda is unable to print her backup reports. From the looks
> >> of the error, nothing will print, and I now have 2 amanda printouts
> >> sitting in the print queue, all failing with an Invalid fonts in
> >> findfonts error.
> >>
> >> When the rpm ran its postinstall thing, it only does two things,
> >> wrapped in bash conditionals:
> >>
> >> /usr/sbin/chkfontpath --add /usr/share/fonts/msttcorefonts
> >>
> >> which apparently runs ok, no errors are reported.
> >> But then it runs
> >> /usr/bin/fc-cache which spits out this:
> >>
> >> /usr/share/fonts: failed to write cache
> >> /usr/share/fonts/bitmap-fonts: failed to write cache
> >> /usr/share/fonts/bitstream-vera: failed to write cache
> >> /usr/share/fonts/default: failed to write cache
> >> /usr/share/fonts/default/Type1: failed to write cache
> >> /usr/share/fonts/default/ghostscript: failed to write cache
> >> /usr/share/fonts/dejavu-lgc: failed to write cache
> >> /usr/share/fonts/japanese: failed to write cache
> >> /usr/share/fonts/japanese/TrueType: failed to write cache
> >> /usr/share/fonts/japanese/misc: failed to write cache
> >> /usr/share/fonts/msttcorefonts: failed to write cache
> >> /usr/share/fonts/perl: failed to write cache
> >> /root/.fonts: failed to write cache
> >> /root/.fonts/kde-override: failed to write cache
> >> /usr/local/share/fonts: failed to write cache
> >>
> >> straceing fc-cache shows that the files its looking for do not exist
> >> on this system, here is the stanza for /root/.fonts/kde-override:
> >> open("/root/.fonts/kde-override/._fonts.dir", O_RDONLY) = -1 ENOENT
> >> (No such file or directory)
> >> open("/root/.fonts/kde-override/%fonts.dir", O_RDONLY) = -1 ENOENT (No
> >> such file or directory)
> >> open("/root/.fonts/kde-override/.AppleDouble/fonts.dir", O_RDONLY) =
> >> -1 ENOENT (No such file or directory)
> >> open("/root/.fonts/kde-override/fonts.dir/rsrc", O_RDONLY) = -1
> >> ENOTDIR (Not a directory)
> >> open("/root/.fonts/kde-override/resource.frk/fonts.dir", O_RDONLY) =
> >> -1 ENOENT (No such file or directory)
> >> open("/root/.fonts/kde-override/.resource/fonts.dir", O_RDONLY) = -1
> >> ENOENT (No such file or directory)
> >>
> >> And I assume its the same for the others listed above since those
> >> files/dirs do not exist:
> >>
> >> [root at coyote ~]# ls -la /root/.fonts/kde-override
> >> total 36
> >> drwxr-xr-x 2 root root 4096 Sep 29 2004 .
> >> drwxr-xr-x 3 root root 4096 Dec 24 2004 ..
> >> -rw-r--r-- 1 root root 3784 Jun 30 2002 cursor.pcf.gz
> >> -rw-r--r-- 1 root root 0 Jan 5 2005 fonts.cache-1
> >> -rw-r--r-- 1 root root 23 Jan 21 17:15 fonts.dir
> >>
> >> You'll recall I ran the selinux utility 'fixfiles' several days ago
> >> also. But this apparently started with the failed installation
> >> postinstall of msttcorefonts.
> >>
> >> So whats the rescue procedure here folks?, I have jobs piling up in
> >> the print queue from the findfont error.
> >>
> >> ISTR we used to have a fixfonts utility, but that puppy seems to be on
> >> the missing list here. Was it deprecated?
> >>
> >> Thanks for any clues/cluebats.
> >
> >----
> >the errors you list include paths that would have only come from a
> >Macintosh (rsrc / resource.frk / .AppleDouble) and that Macintosh cruft
> >doesn't seem to be very agreeable to findfont. Did you copy some fonts
> >from a Macintosh before you installed the msttcorefonts?
> >
> >Craig
>
> No, not to my knowledge Craig. For this install, and this has been true
> since the install plus a day or so, the only extra stuff was to copy a
> bunch of fonts from my old FC2 drive that I had downloaded from
> goldenweb.it (a great font source BTW) over the last 3 or so years. They
> all showed up for use in OOo-2.0.x as soon as copied. All the other
> fonts on this system were installed by yumex from fedora repos with the
> possible addition of a livna or atrpms package but I sure don't remember
> clicking on any fonts from either in recent (last month or so) history.
>
> Can I nuke those? Duh, silly Q, they don't exist in the first place.
> I suppose I can rerun the strace and back up to the top, looking for hints
> of where it may be picking up these erronious paths, but that's a 10
> megabyte strace! Hints gleefully checked out as that would be a rather
> painfull search.
>
> Did that, (had to increase the history to 1,000,000 lines) traced down to
> the first failure, after it had successfully opened every font in
> the /usr/share/fonts/bitmap-fonts directory, and the failure appears to
> be:
>
> stat64("/usr/share/fonts/bitmap-fonts", {st_mode=S_IFDIR|0766,
> st_size=4096, ...}) = 0
> write(2, "/usr/share/fonts/bitmap-fonts: f"...,
> 53/usr/share/fonts/bitmap-fonts: failed to write cache
> ) = 53
>
> The drive has 80GB free, and the ls -la of that dir is:
> [root at coyote src]# ls -la /usr/share/fonts/bitmap-fonts
> total 7216
> drwxrw-rw- 2 root root 4096 Nov 9 08:35 .
> drwxrw-rw- 9 root root 4096 Jan 25 02:12 ..
> -rwxrw-rw- 1 root root 654344 Jul 12 2006 10x20.pcf
> -rwxrw-rw- 1 root root 182064 Jul 12 2006 4x6.pcf
> -rwxrw-rw- 1 root root 239812 Jul 12 2006 5x7.pcf
> -rwxrw-rw- 1 root root 220944 Jul 12 2006 5x8.pcf
> -rwxrw-rw- 1 root root 244424 Jul 12 2006 6x10.pcf
> -rwxrw-rw- 1 root root 270480 Jul 12 2006 6x12.pcf
> -rwxrw-rw- 1 root root 237596 Jul 12 2006 6x13B.pcf
> -rwxrw-rw- 1 root root 495964 Jul 12 2006 6x13.pcf
> -rwxrw-rw- 1 root root 218096 Jul 12 2006 6x9.pcf
> -rwxrw-rw- 1 root root 219064 Jul 12 2006 7x14B.pcf
> -rwxrw-rw- 1 root root 353836 Jul 12 2006 7x14.pcf
> -rwxrw-rw- 1 root root 284372 Jul 12 2006 9x15B.pcf
> -rwxrw-rw- 1 root root 565716 Jul 12 2006 9x15.pcf
> -rwxrw-rw- 1 root root 209924 Jul 12 2006 9x18B.pcf
> -rwxrw-rw- 1 root root 618112 Jul 12 2006 9x18.pcf
> -rwxrw-rw- 1 root root 193804 Jul 12 2006 console8x16.pcf
> -rwxrw-rw- 1 root root 149408 Jul 12 2006 console8x8.pcf
> -rwxrw-rw- 1 root root 522564 Jul 12 2006 console9x15.pcf
> -rwxrw-rw- 1 root root 65488 Jul 12 2006 lutBS08.pcf
> -rwxrw-rw- 1 root root 72040 Jul 12 2006 lutBS10.pcf
> -rwxrw-rw- 1 root root 77124 Jul 12 2006 lutBS12.pcf
> -rwxrw-rw- 1 root root 80584 Jul 12 2006 lutBS14.pcf
> -rwxrw-rw- 1 root root 90248 Jul 12 2006 lutBS18.pcf
> -rwxrw-rw- 1 root root 94608 Jul 12 2006 lutBS19.pcf
> -rwxrw-rw- 1 root root 104852 Jul 12 2006 lutBS24.pcf
> -rwxrw-rw- 1 root root 65440 Jul 12 2006 lutRS08.pcf
> -rwxrw-rw- 1 root root 71740 Jul 12 2006 lutRS10.pcf
> -rwxrw-rw- 1 root root 76904 Jul 12 2006 lutRS12.pcf
> -rwxrw-rw- 1 root root 80556 Jul 12 2006 lutRS14.pcf
> -rwxrw-rw- 1 root root 89500 Jul 12 2006 lutRS18.pcf
> -rwxrw-rw- 1 root root 92320 Jul 12 2006 lutRS19.pcf
> -rwxrw-rw- 1 root root 103776 Jul 12 2006 lutRS24.pcf
>
> And that all looks world writable to me.
>
> If this isn't enough data, just ask.
>
> Here is an interesting item, the DESCRIPTION in that rpm:
> ==============
> The TrueType core fonts for the web that was once available from
> http://www.microsoft.com/typography/fontpack/. The src rpm is cleverly
> constructed so that the actual fonts are downloaded from Sourceforge's
> site
> at build time. Therefore this package technically does not 'redistribute'
> the fonts, it just makes it easy to install them on a linux system.
> ==============
> I didn't notice any lags, and the fonts are in the rpm, and they are
> installed. But something sure is giving fc-cache a belly ache. And I'd
> darned sure call that rpm a re-distribution since the fonts are in fact
> in it.
----
[root at localhost ~]# rpm -q msttcorefonts
msttcorefonts-1.3-4
[root at localhost ~]# /usr/sbin/chkfontpath \
--add /usr/share/fonts/msttcorefonts
chkfontpath: /usr/share/fonts/msttcorefonts already in list
[root at localhost ~]#
I have had the msttcorefonts installed on this machine since day 1
(FC-6, install via kickstart and using local repo's)
No such problems on my end - must be something with your setup.
Craig
More information about the fedora-list
mailing list