Issue 1459 - Failing Installation on Linux
Summary: Failing Installation on Linux
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: 633
Hardware: PC Linux, all
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: philipp.lohmann
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-13 09:43 UTC by hdu@apache.org
Modified: 2004-10-11 15:00 UTC (History)
1 user (show)

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

Attachments
strace before failure, looks like psprint's fontmanager (13.55 KB, text/plain)
2001-08-13 09:46 UTC, hdu@apache.org 		no flags Details
strace before failure, looks like psprint's fontmanager (13.55 KB, text/plain)
2001-08-13 09:51 UTC, hdu@apache.org 		no flags Details
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 hdu@apache.org 2001-08-13 09:43:16 UTC 
Reported by Alistair Robinson <blackfive@fakenhamweb.co.uk> in oo.discuss, for
some reason he wasn't able to file an issuezilla bug, so I'm doing it for him:

I've done some experimentation, and found that the installer always fails on 
my machine if any of the following standard WIndoze TrueType fonts are in the 
X Server's font path:

marlett.ttf
symbol.ttf
webdings.ttf
wingding.ttf

(IIRC correctly, these are all symbol or dingbat fonts, so maybe the 
non-standard encoding is screwing things up?)

This is with XFree86 4.1.0 BTW
Comment 1 hdu@apache.org 2001-08-13 09:46:36 UTC 
Created attachment 445 [details]
strace before failure, looks like psprint's fontmanager
Comment 2 hdu@apache.org 2001-08-13 09:51:04 UTC 
As soon as psprint's fontmanager has seen the first of the
symbol fonts mentioned above it crashes with a SIGSEGV.
On my (hdu) system this worked ok in 633 and 638.
Comment 3 hdu@apache.org 2001-08-13 09:51:14 UTC 
Created attachment 446 [details]
strace before failure, looks like psprint's fontmanager
Comment 4 philipp.lohmann 2001-08-27 12:22:09 UTC 
I finally could reproduce the problem. This was due to freeing an 
uninitalized pointer in the fontsubset code. It was fixed already in 
src633, but the Ooo binary install set does not contain that fix.
Comment 5 thorsten.ziehm 2004-10-11 15:00:23 UTC 
This prio1-Task can be closed. It isn't interessting anymore!