Issue 1106 - TrueType Font "Times New Roman" crashes Build 632 on XFree86 4.1.0
Summary: TrueType Font "Times New Roman" crashes Build 632 on XFree86 4.1.0
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: 632
Hardware: PC Linux, all
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: hdu@apache.org
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-06-25 22:10 UTC by issues@www
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description issues@www 2001-06-25 22:10:54 UTC
I'm using Build 632 as found on the OO-Download page.

When trying to start OpenOffice it crashes.

After removing all TrueType Fonts I was able to start OO.
BUT: Other applications work with the TrueType Fonts on XFree86 4.1.0 (e.g.
koffice). When I reinstalled "Times New Roman" OO crashed again when I tried to
start it.

And OO crashes when I open the Font drop-down list, even if there are no
TrueType fonts installed 

I'm running on a fresh install of SuSE 7.1 / Kernel 2.4.0.
I've installed SuSE's rpms of XFree86 4.1.0 and KDE 2.1.1 .
The video card is a Voodoo3 AGP. Driver: tdfx.o.
Resolution: 1280x1024 24bpp (DRI inactive)

The fonts are installed on a ReiserFS partition.
"Times New Roman" is the TrueType Font as delivered with W2k.

Detlef
Comment 1 Unknown 2001-06-26 08:44:00 UTC
TH->HDU: FreeType/GlyphCache?
Comment 2 hdu@apache.org 2001-06-26 10:13:44 UTC
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.
Comment 3 issues@www 2001-06-27 21:41:25 UTC
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.
Comment 4 hdu@apache.org 2001-06-28 09:40:59 UTC
> 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?
Comment 5 issues@www 2001-06-29 01:11:13 UTC
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.



Comment 6 hdu@apache.org 2001-06-29 14:34:43 UTC
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.
Comment 7 hdu@apache.org 2001-06-29 14:50:29 UTC
I'm also wondering if during the setup the fonts where antialiased?
Comment 8 detlef 2001-09-11 20:11:41 UTC
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.
Comment 9 hdu@apache.org 2001-09-14 15:29:00 UTC
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.
Comment 10 detlef 2001-09-16 23:20:31 UTC
Yes, I think it has been resolved in 638.
Comment 11 hdu@apache.org 2001-09-26 10:01:57 UTC
Closing then.
Comment 12 hdu@apache.org 2002-05-16 10:19:05 UTC
closing.