Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | TrueType Font "Times New Roman" crashes Build 632 on XFree86 4.1.0 | ||
---|---|---|---|
Product: | gsl | Reporter: | issues@www <issues> |
Component: | code | Assignee: | hdu <hdu> |
Status: | CLOSED FIXED | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P1 (highest) | CC: | issues |
Version: | 632 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
issues@www
2001-06-25 22:10:54 UTC
TH->HDU: FreeType/GlyphCache? Does it still crash when you uncomment the line #setenv SAL_ANTIALIAS_DISABLE true; export SAL_ANTIALIAS_DISABLE in the program/soffice file? You can uncomment this line by removing the # in front of it. OO does start after uncommenting the line setenv SAL_ANTIALIAS_DISABLE true; export SAL_ANTIALIAS_DISABLE The not antialiased TT Fonts can be used. But OO still crashes when I try to use "Monotype Sorts" - it's a MS font that I copied from my W2k fonts-directory. > The not antialiased TT Fonts can be used.
Very interesting. I think this means that the RENDER extension
for the Voodoo3 AGP driver seems to have a problem. Or maybe
the libXrender library on your system is corrupted.
Is there any other program that uses antialiased fonts
(e.g. KDE with qt>=2.3) on this machine?
"Monotype Sorts" works ok here. I read on the mailing list
that you recompiled VCL and there were compile problems with
the freetype library?
I activated anti-aliased TT Fonts for QT 2.3.0 on my machine. The desktop of KDE 2.1 shows only TrueType Fonts now. The anti-aliased TT fonts work fine with KWord. I checked that with xmag. But OO still doesn't start. I had to disable anti-aliased fonts for OO again. BTW: Monotype Sorts seems not to be a real TT font as KDE didn't recognized it after I had activated anti-aliasing. I'm still using the Build 632 binaries for testing purposes. That's because I have problems with compiling the source-code. The path for the freetype library headers seems to be incorrect. Are the binaries of Build 632 for Linux o.k.? I recognized that the MD5 Sum of the binaries is not that reported on the WebPage. So libXrender seems too work...
> I recognized that the MD5 Sum of the binaries is not
> that reported on the WebPage.
This is the onyl idea I have left. Though I'm wondering how
a corrupted *.tgz could be successfully uncompressed and
running in the non-antialiased case. Strange indeed.
I'm also wondering if during the setup the fonts where antialiased? I have now installed Build 638 and OOo does work with TrueType fonts. They are antialiased and I had no crashes so far. Btw the setup uses antialiased fonts, too. I did the test with a SuSE 7.2, a patched Kernel 2.4.4, XFree86 4.1.0 and KDE 2.2. Though the problem you had with 632 could not be recreated here and is not yet understood, do you agree that the issue has been resolved in the 632->638 evolution? It could be closed then. Yes, I think it has been resolved in 638. Closing then. closing. |