Issue 10874 - XFree crash when using times.ttf
Summary: XFree crash when using times.ttf
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-01-22 22:24 UTC by vpoythress
Modified: 2003-09-08 16:56 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description vpoythress 2003-01-22 22:24:26 UTC 
I have files with footnotes in .doc and .sxw that, when loaded in
oowriter and scrolled down to where the footnote is, regularly lead to 
dumping me out of XFree and into the command line. It happens either in
KDE or Gnome. It seems to be
partly related to the small size of the fonts in the subscript numbers, but
changing the size (and ttf font of footnote char styles) did not totally cure it.  

The initial pages with no footnotes appear OK.

Also, if I remove the (MS originated) times.ttf, which I have set as my
default font, and let oowriter use the closest equivalent, the problem 
goes away.


I can reproduce the effect in both RedHat 7.3 and Mandrake 9.0,
in both of which I installed OpenOffice1.0.2 in the workstation form.

I can provide the .doc files if you like <vpoythress1@netscape.net>. I can't find
a way to attach them to this message.
Comment 1 dankegel 2003-05-15 16:36:32 UTC 
Vern says it's fixed in both Redhat 9 and Mandrake 9.1 (both with
OpenOffice 1.0.2), so I guess it was an X bug.  He sent me the
files in case anyone's curious.
Comment 2 thorsten.ziehm 2003-05-21 17:06:38 UTC 
This task is 'resolved invalid' and will be closed now.
If you have more details to reproduce the task, please reopen it.
Comment 3 thorsten.ziehm 2003-05-21 17:11:01 UTC 
This task is 'resolved invalid' and will be closed now.
If you can give more details to reproduce the problem, please re-open it.
Comment 4 thorsten.ziehm 2003-05-21 17:12:45 UTC 
... closed