[Bug 921706] ghostscript: /invalidfont in /findfont, --nostringval-- Helvetica
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=921706
--- Comment #55 from Jaroslav Škarvada <jskarvad(a)redhat.com> ---
(In reply to Jerry James from comment #53)
> But if the guesses in comment 40 through comment 46 are correct, that only
> worked because the -v slowed fc-cache down enough to let something else
> happen first. If we can figure out what that mysterious something else is,
> we'll finally have a clue how to solve this bug for good.
No, I ran it in the buildroot which is "in the wrong state" after failed:
$ mock -r fedora-rawhide-x86_64 ./sendmail-8.14.9-2.fc21.src.rpm
I am not changing the urw-fonts scriptlets.
If fc-cache is ran in such buildroot (by entering it by e.g. mock -r
fedora-rawhide-x86_64 --shell), it seems there is no difference if using '-v'
or not. The following command fixes the cache:
# fc-cache /usr/share/fonts/default
and then the ps2pdf works, but the:
# fc-cache /usr/share/fonts/default/Type1
doesn't fix the cache (this is the same path as used in the urw-fonts
scriptlets) which seems suspicious to me.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=PVAJ6a2OA3&a=cc_unsubscribe
9 years, 11 months
[Bug 921706] ghostscript: /invalidfont in /findfont, --nostringval-- Helvetica
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=921706
--- Comment #54 from Jerry James <loganjerry(a)gmail.com> ---
Running fc-cache -v inside the urw-fonts %post script yields this output on a
failing zenon build:
/usr/share/fonts/default/Type1: caching, new cache contents: 35 fonts, 0 dirs
/var/cache/fontconfig: cleaning cache directory
/builddir/.cache/fontconfig: not cleaning non-existent cache directory
/builddir/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded
as opposed to this output on a successful build:
/usr/share/fonts/default/Type1: skipping, existing cache is valid: 35 fonts, 0
dirs
/var/cache/fontconfig: cleaning cache directory
/builddir/.cache/fontconfig: not cleaning non-existent cache directory
/builddir/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded
Does that give a clue as to what is going wrong?
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=H7nuw1OLVY&a=cc_unsubscribe
9 years, 11 months
[Bug 921706] ghostscript: /invalidfont in /findfont, --nostringval-- Helvetica
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=921706
--- Comment #53 from Jerry James <loganjerry(a)gmail.com> ---
(In reply to Jaroslav Škarvada from comment #51)
> # fc-cache -v /usr/share/fonts/default
> /usr/share/fonts/default: skipping, existing cache is valid: 0 fonts, 1 dirs
> /usr/share/fonts/default/ghostscript: skipping, existing cache is valid: 4
> fonts, 0 dirs
> Re-scanning /usr/share/fonts/default: caching, new cache contents: 0 fonts,
> 2 dirs
> /var/cache/fontconfig: cleaning cache directory
> /builddir/.cache/fontconfig: not cleaning non-existent cache directory
> /builddir/.fontconfig: not cleaning non-existent cache directory
> fc-cache: succeeded
>
> And then everything work as expected.
But if the guesses in comment 40 through comment 46 are correct, that only
worked because the -v slowed fc-cache down enough to let something else happen
first. If we can figure out what that mysterious something else is, we'll
finally have a clue how to solve this bug for good.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=J3RmlbU98T&a=cc_unsubscribe
9 years, 11 months
[Bug 921706] ghostscript: /invalidfont in /findfont, --nostringval-- Helvetica
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=921706
--- Comment #52 from Jerry James <loganjerry(a)gmail.com> ---
(In reply to Akira TAGOH from comment #48)
> That sounds like another issue. does changing the order of <cachedir> in
> /etc/fonts.conf help? i.e. changing
>
> <cachedir>/var/cache/fontconfig</cachedir>
> <cachedir prefix="xdg">fontconfig</cachedir>
>
> to:
>
> <cachedir prefix="xdg">fontconfig</cachedir>
> <cachedir>/var/cache/fontconfig</cachedir>
Sorry to be slow replying. That does not help. I just did a mock build with
the lines switch as indicated (in a custom fontconfig package build; that was
the only change). The zenon build still failed with the ghostscript complaint
recorded above. Now I see this inside the mock root:
# ls /var/cache/fontconfig
# ls /builddir/.cache/fontconfig
0251a5afa6ac727a1e32b7d4d4aa7cf0-le64.cache-4
3830d5c3ddfd5cd38a049b759396e72e-le64.cache-4
87f5e051180a7a75f16eb6fe7dbd3749-le64.cache-4
b79f3aaa7d385a141ab53ec885cc22a8-le64.cache-4
CACHEDIR.TAG
cfde08ab28ad1d91784abb10973575e3-le64.cache-4
# strings
/builddir/.cache/fontconfig/0251a5afa6ac727a1e32b7d4d4aa7cf0-le64.cache-4
/usr/share/fonts/default
/usr/share/fonts/default/ghostscript
# strings
/builddir/.cache/fontconfig/b79f3aaa7d385a141ab53ec885cc22a8-le64.cache-4
/usr/share/fonts/default/Type1
URW Gothic L
Book
/usr/share/fonts/default/Type1/a010013l.pfb
Type 1
sha256:ef6cd71620433f650ab4b8022318b261858f4a82ddf87059ad515d355ff2f1cf
URWGothicL-Book
URW Gothic L
Demi
/usr/share/fonts/default/Type1/a010015l.pfb
Type 1
...
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6RibcU59bG&a=cc_unsubscribe
9 years, 11 months
[Bug 921706] ghostscript: /invalidfont in /findfont, --nostringval-- Helvetica
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=921706
--- Comment #51 from Jaroslav Škarvada <jskarvad(a)redhat.com> ---
It's quite good reproducible with sendmail (I would say 90% reproducibility) in
both koji and mock, e.g. I used the following:
$ mock -r fedora-rawhide-x86_64 ./sendmail-8.14.9-2.fc21.src.rpm
When the problem happen, it is not possible to rebuild the cache by hand as it
seems already up-to-date:
# fc-cache -v /usr/share/fonts/default/Type1
/usr/share/fonts/default/Type1: skipping, existing cache is valid: 35 fonts, 0
dirs
/var/cache/fontconfig: cleaning cache directory
/builddir/.cache/fontconfig: not cleaning non-existent cache directory
/builddir/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded
This is the same command (without -v) that is issued in the spec file. But the
following command rebuilds the cache successfully:
# fc-cache -v /usr/share/fonts/default
/usr/share/fonts/default: skipping, existing cache is valid: 0 fonts, 1 dirs
/usr/share/fonts/default/ghostscript: skipping, existing cache is valid: 4
fonts, 0 dirs
Re-scanning /usr/share/fonts/default: caching, new cache contents: 0 fonts, 2
dirs
/var/cache/fontconfig: cleaning cache directory
/builddir/.cache/fontconfig: not cleaning non-existent cache directory
/builddir/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded
And then everything work as expected.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6AEIaIueO2&a=cc_unsubscribe
9 years, 11 months