Issue 86306

Summary:	office crashes at startup on Solaris Intel
Product:	gsl	Reporter:	joachim.lingner
Component:	code	Assignee:	stefan.baltzer
Status:	CLOSED NOT_AN_OOO_ISSUE	QA Contact:	issues@gsl <issues>
Severity:	Trivial
Priority:	P3	CC:	issues, philipp.lohmann
Version:	OOH680m7
Target Milestone:	OOo 2.4
Hardware:	All
OS:	Solaris
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description joachim.lingner 2008-02-21 13:11:07 UTC

I got this stack when runngin soffice.bin:

t@1 (l@1) signal SEGV (access to address exceeded protections) in FcCharSetCopy
at 0xfcaa3028
0xfcaa3028: FcCharSetCopy+0x0028:       movl     %eax,(%edx)
(dbx 2) where
current thread: t@1
=>[1] FcCharSetCopy(0x0), at 0xfcaa3028
  [2] FcValueSave(0x80401dc, 0x6, 0x0), at 0xfcab2de5
  [3] FcPatternAddWithBinding(0x82cc750, 0xfcac3b88, 0x6, 0x0, 0xab1687, 0x1,
0x1), at 0xfcab481c
  [4] FcPatternAdd(0x82cc750, 0xfcac3b88, 0x6, 0x0, 0xab1687, 0x1), at 0xfcab4a3b
  [5] FcNameParse(0x8042c85), at 0xfcab2125
  [6] FcCacheFontSetAdd(0x82cc0d0, 0x82c08b8, 0x82c7b18, 0x29, 0x8044340,
0x804233c), at 0xfca9b229
  [7] FcDirCacheReadDir(0x82cc0d0, 0x82c08b8, 0x82c81e8), at 0xfca9d3ff
  [8] FcDirScan(0x82cc0d0, 0x82c08b8, 0x82c9558, 0x82ce2f0, 0x82c81e8, 0x0), at
0xfcaa7105
  [9] FcConfigBuildFonts(0x82c3050), at 0xfca9e5e6
  [10] FcInitLoadConfigAndFonts(0x817b588, 0x82c0858, 0xfcad4000, 0xfcaaa617,
0x1, 0x82c2fd0), at 0xfcaaa5bd
  [11] FcInit(0x817b588, 0x82c0858, 0xfcad4000, 0xfca9e777, 0xfcad4000,
0x8046480), at 0xfcaaa655
  [12] FcConfigGetCurrent(0x817b588, 0x82c0858, 0xfcad4000, 0xfcaa1117, 0x1,
0x817b588), at 0xfca9e7a7
  [13] FcConfigSubstituteWithPat(0x0, 0x82c0858, 0x0, 0x0), at 0xfcaa1142
  [14] FcConfigSubstitute(0x0, 0x82c0858, 0x0), at 0xfcaa1962

Comment 1 joachim.lingner 2008-02-21 13:12:59 UTC

cc ing pl

Comment 2 philipp.lohmann 2008-02-22 16:22:18 UTC

starting

Comment 3 philipp.lohmann 2008-02-23 10:20:52 UTC

There are some really broken fontconfig installations out there. Checked in a
workaround that catches the SIGSEGV and it that occurs hencforthe ignores
fontconfig in psprint.

fixed in CWS vclshowstop14

Comment 4 philipp.lohmann 2008-02-25 12:16:44 UTC

please verify in CWS vclshowstop14

Comment 5 stefan.baltzer 2008-02-25 17:12:49 UTC

SBA: Further investigation by PL showed that NO Gnome application starts on that
very system. That machine has a broken fontconfig.

I can see no reason why any application shaould be "smarter" than the system
(and its Gnome applications). So this issue is INVALID.

I will set it as such and remove the link to issue 84957.

Comment 6 stefan.baltzer 2008-02-25 17:15:35 UTC

Set to Invalid.

Comment 7 stefan.baltzer 2008-02-25 17:16:17 UTC

Closed.