openoffice.org: Crashes on start

Bug #14709 reported by Debian Bug Importer
8
Affects Status Importance Assigned to Milestone
openoffice.org (Debian)
Fix Released
Unknown
openoffice.org (Ubuntu)
Invalid
High
Matthias Klose

Bug Description

Automatically imported from Debian bug report #302160 http://bugs.debian.org/302160

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #302160 http://bugs.debian.org/302160

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (4.6 KiB)

Message-id: <email address hidden>
Date: Wed, 30 Mar 2005 14:31:37 +0300
From: Harri Kiiskinen <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: openoffice.org: Crashes on start

Package: openoffice.org
Version: 1.1.3-7
Severity: grave
Justification: renders package unusable

All the openoffice programs (no matter how started: Menu, command-line:
ooffice, oowriter, oocalc etc.) crash on startup. Disabling CUPS does
not help, neither enabling
 export SAL_DISABLE_CUPS=1
in /etc/openoffice/openoffice.conf. The replacement of
/usr/lib/openoffice/program/libpsp645li.so with
 http://people.debian.org/~halls/openoffice/test/libpsp645li.so.bz2
does not help either. The problem persists, and has been there through
many versions of openoffice, the last working one must have been before
1.1.0 or something, way back in time.

Greetings,

 Harri Kiiskinen

The output of ooffice on terminal:

OpenOffice.org lockfile found (/home/harri/.openoffice/1.1.3/.lock)
Using existing OpenOffice.org
sh: line 1: crash_report: command not found

Fatal exception: Signal 11
Stack:
/usr/lib/openoffice/program/libsal.so.3[0x411ab3ec]
/usr/lib/openoffice/program/libsal.so.3[0x411ab579]
/usr/lib/openoffice/program/libsal.so.3[0x411ab644]
[0xffffe420]
/usr/lib/openoffice/program/libpsp645li.so(_ZN3psp16PrintFontManager9PrintFont14readAfmMetricsERKN3rtl7OStringEPN3utl17MultiAtomProviderEb+0x1ed1)[0x40b74fad]
/usr/lib/openoffice/program/libpsp645li.so(_ZNK3psp16PrintFontManager15analyzeFontFileEiRKN3rtl7OStringEbRKN4_STL4listIS2_NS5_9allocatorIS2_EEEERNS6_IPNS0_9PrintFontENS7_ISD_EEEE+0x4cd)[0x40b79e51]
/usr/lib/openoffice/program/libpsp645li.so(_ZN3psp16PrintFontManager14initFontconfigEv+0x529)[0x40b99535]
/usr/lib/openoffice/program/libpsp645li.so(_ZN3psp16PrintFontManager10initializeEPv+0x17c)[0x40b7e210]
/usr/lib/openoffice/program/libpsp645li.so(_ZN3psp16PrintFontManager3getEv+0x69)[0x40b75195]
/usr/lib/openoffice/program/libvclplug_gen645li.so(_ZN14X11SalGraphics14GetDevFontListEP15ImplDevFontList+0x63)[0x40a977dd]
/usr/lib/openoffice/program/libvcl645li.so(_ZNK12OutputDevice16ImplInitFontListEv+0x4d)[0x426b52ad]
/usr/lib/openoffice/program/libvcl645li.so(_ZN6Window24ImplUpdateGlobalSettingsER11AllSettingsh+0x64)[0x42767d9e]
/usr/lib/openoffice/program/libvcl645li.so(_ZN6Window8ImplInitEPS_xP16SystemParentData+0x6f9)[0x4276949b]
/usr/lib/openoffice/program/libvcl645li.so(_ZN16ImplBorderWindow8ImplInitEP6WindowxtP16SystemParentData+0x112)[0x42722df6]
/usr/lib/openoffice/program/libvcl645li.so(_ZN16ImplBorderWindowC1EP6WindowP16SystemParentDataxt+0x70)[0x42722f9c]
/usr/lib/openoffice/program/libvcl645li.so(_ZN10WorkWindow8ImplInitEP6WindowxP16SystemParentData+0x7d)[0x42784c57]
/usr/lib/openoffice/program/libvcl645li.so(_ZN11IntroWindowC2Ev+0x68)[0x427859ea]
/usr/lib/openoffice/program/libspl645li.so[0x4524f48d]
/usr/lib/openoffice/program/libspl645li.so[0x452505ff]
/usr/lib/openoffice/program/libcppuhelpergcc3.so.3[0x414f7169]
/usr/lib/openoffice/program/libcppuhelpergcc3.so.3[0x414f731a]
/usr/lib/openoffice/program/libcppuhelpergcc3.so.3[0x414f7eba]
/usr/lib/openoffice/program/libcppuhelpergcc3.so.3[0x414f7384]
/...

Read more...

Revision history for this message
In , Leandro Guimarães Faria Corcete DUTRA (leandro) wrote :

 Here this has happened with the 1.1.4 packages.

--
Leandro Guimarães Faria Corcete Dutra <email address hidden>
Maringá, PR, BRASIL +55 (44) 3025 6253
http://br.geocities.com./lgcdutra/ +55 (44) 8803 1729
Soli Deo Gloria! +55 (11) 9406 7191

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <1112197488.24656.7.camel@debian>
Date: Wed, 30 Mar 2005 12:44:48 -0300
From: Leandro =?ISO-8859-1?Q?Guimar=E3es?= Faria Corcete Dutra <email address hidden>
To: <email address hidden>
Subject: openoffice.org: Crashes on start

 Here this has happened with the 1.1.4 packages.

--=20
Leandro Guimar=C3=A3es Faria Corcete Dutra <email address hidden>
Maring=C3=A1, PR, BRASIL +55 (44) 3025 6253
http://br.geocities.com./lgcdutra/ +55 (44) 8803 1729
Soli Deo Gloria! +55 (11) 9406 7191

Revision history for this message
In , Harri Kiiskinen (harkiisk) wrote : Reason for crash solved

Hello,

I finally found the reason for the mysterious crash: it resulted from a
corrupted afm-file in /usr/X11R6/lib/X11/fonts/Type1/. So the bug
actually should read something like:

"OpenOffice.Org crashes when it tries to read a non-ascii character in
an afm file." Of course, there shouldn't ever be any non-ascii
characters in afm files, but other programs may have bugs in them,
too...

A suggested solution: instead of crashing, ignore the font, perhaps with
a notice, that the font OpenOffice.org was trying to read is corrupted.

--
Harri Kiiskinen

Revision history for this message
In , Justin Pryzby (justinpryzby-users) wrote : retitle 302160 to openoffice.org: crashes when trying to read a non-ascii character from afm file

# Automatically generated email from bts, devscripts version 2.8.10
retitle 302160 openoffice.org: crashes when trying to read a non-ascii character from afm file

Revision history for this message
Matthias Klose (doko) wrote :

from the debian report: "it resulted from a corrupted afm-file in
/usr/X11R6/lib/X11/fonts/Type1/",
checked that these are correct in the xfonts-scalable package.

Revision history for this message
In , A. Maitland Bottoms (bottoms) wrote : openoffice.org: crashes when trying to read a non-ascii character from afm file

Version: 1.1.3-7
Sarge system

Yes, I encountered this on a system that still had some fonts in a
/usr/X11R6/lib/X11/fonts/WordPerfect/
directory. (Not Debian's fault...)

Got rid of those and OpenOffice.org is happy to run again.

-Maitland

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-id: <email address hidden>
Date: Fri, 01 Apr 2005 13:07:37 +0300 (EEST)
From: Harri Kiiskinen <email address hidden>
To: <email address hidden>
Subject: Reason for crash solved

Hello,

I finally found the reason for the mysterious crash: it resulted from a
corrupted afm-file in /usr/X11R6/lib/X11/fonts/Type1/. So the bug
actually should read something like:

"OpenOffice.Org crashes when it tries to read a non-ascii character in
an afm file." Of course, there shouldn't ever be any non-ascii
characters in afm files, but other programs may have bugs in them,
too...

A suggested solution: instead of crashing, ignore the font, perhaps with
a notice, that the font OpenOffice.org was trying to read is corrupted.

--
Harri Kiiskinen

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <E1DHKLs-0006XC-00@localhost>
Date: Fri, 1 Apr 2005 06:30:10 -0500
From: Justin Pryzby <email address hidden>
To: <email address hidden>
Subject: retitle 302160 to openoffice.org: crashes when trying to read a non-ascii character from
 afm file

# Automatically generated email from bts, devscripts version 2.8.10
retitle 302160 openoffice.org: crashes when trying to read a non-ascii character from afm file

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 3 Apr 2005 19:46:38 -0400
From: "A. Maitland Bottoms" <email address hidden>
To: <email address hidden>
Subject: openoffice.org: crashes when trying to read a non-ascii character from afm file

Version: 1.1.3-7
Sarge system

Yes, I encountered this on a system that still had some fonts in a
/usr/X11R6/lib/X11/fonts/WordPerfect/
directory. (Not Debian's fault...)

Got rid of those and OpenOffice.org is happy to run again.

-Maitland

Revision history for this message
In , Rene Engelhard (rene-engelhard) wrote : severity of 302160 is important

severity 302160 important

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <20050406100644.D41926A1E9@localhost>
Date: Wed, 6 Apr 2005 12:06:44 +0200 (CEST)
From: <email address hidden> (Rene Engelhard)
To: <email address hidden>
Subject: severity of 302160 is important

severity 302160 important

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <20050406100852.6A66B6A1E9@localhost>
Date: Wed, 6 Apr 2005 12:08:52 +0200 (CEST)
From: <email address hidden> (Rene Engelhard)
To: <email address hidden>
Subject: severity of 302160 is important

severity 302160 important

Revision history for this message
In , Browaeys-alban (browaeys-alban) wrote : Re: openoffice.org: crashes when trying to read a non-ascii character from afm file

Does openoffice really manage the rendering of font itself ?

If it rely on libxft2 or freetype2 the bug could be reassigned
there. Also there was an upload yesterday fixing a segfault
with some broken bdf fonts, it could be valuable to check if the
problem still exist before reassigning.

Could you provide the broken font ?

Regards
Alban

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 6 Apr 2005 19:07:21 +0200
From: <email address hidden>
To: <email address hidden>
Subject: Re: openoffice.org: crashes when trying to read a non-ascii character from afm file

Does openoffice really manage the rendering of font itself ?

If it rely on libxft2 or freetype2 the bug could be reassigned
there. Also there was an upload yesterday fixing a segfault
with some broken bdf fonts, it could be valuable to check if the
problem still exist before reassigning.

Could you provide the broken font ?

Regards
Alban

Revision history for this message
In , Browaeys-alban (browaeys-alban) wrote :

Thank for you tracking the issue about the openoffice crash in:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302160

Other users have encountered the same crash and broken or corrupted fonts
are not so rare.

Could you give more information about the font so that the font
librairy maintainer can check why it is not ignored (and send to
the application leading to a crash).

Was it a font corrupted in some random way by a disk problem ?

My apalogies if you answered to the previous request.Please send
a copy of the answer to <email address hidden> , though it should
be done automatically by your mail agent.

Regards
Alban

Revision history for this message
In , Harri Kiiskinen (harkiisk) wrote : Re: Bug#302160: openoffice.org: crashes when trying to read a non-ascii character from afm file

Hello,

and sorry for not answering the last mail; I simply forgot it.

On Sat, 23 Apr 2005 <email address hidden> wrote:

> Thank for you tracking the issue about the openoffice crash in:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302160
>
> Other users have encountered the same crash and broken or corrupted fonts
> are not so rare.
>
> Could you give more information about the font so that the font
> librairy maintainer can check why it is not ignored (and send to
> the application leading to a crash).
>
> Was it a font corrupted in some random way by a disk problem ?

I cannot provide you with the details about the font nor the afm-file
any more, because when I fixed the corrupted afm-file, the problem went
away, and at the time of the last mail, I didn't remember any more which
font it actually was.

However, the details are almost clear in my mind: there were two 8-bit
characters in the corrupted afm-file: in the first case, a character
with the decimal code >230 had replaced (in emacs it looked like \238)
the return-char at the end of the line; in the second case, a character
in the name of a glyph in kerning tables had been replaced by a
charcter with the decimal code >230.

The cause was most probably a disk corruption, probably as a result of
running out of batteries on my laptop.

Greetings,

Harri Kiiskinen

Revision history for this message
In , Browaeys-alban (browaeys-alban) wrote : corrupted fot should be ignored

reassign 302160 libfreetype6
quit

I wonder if it is fontconfig job ... though can fontconfig
detecty if a font has some weird characters inside (8 bit in an
afm file there).

Regards
Alban

Revision history for this message
In , Will Newton (will-misconception) wrote :

severity 302160 normal

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 23 Apr 2005 08:32:24 +0200
From: <email address hidden>
To: <email address hidden>
Subject: Re: openoffice.org: crashes when trying to read a non-ascii character from afm file

Thank for you tracking the issue about the openoffice crash in:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302160

Other users have encountered the same crash and broken or corrupted fonts
are not so rare.

Could you give more information about the font so that the font
librairy maintainer can check why it is not ignored (and send to
the application leading to a crash).

Was it a font corrupted in some random way by a disk problem ?

My apalogies if you answered to the previous request.Please send
a copy of the answer to <email address hidden> , though it should
be done automatically by your mail agent.

Regards
Alban

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-id: <email address hidden>
Date: Mon, 25 Apr 2005 10:43:42 +0300 (EEST)
From: Harri Kiiskinen <email address hidden>
To: <email address hidden>, <email address hidden>
Cc: <email address hidden>, Debian BTS <email address hidden>,
 Harri Kiiskinen <email address hidden>
Subject: Re: Bug#302160: openoffice.org: crashes when trying to read a
 non-ascii character from afm file

Hello,

and sorry for not answering the last mail; I simply forgot it.

On Sat, 23 Apr 2005 <email address hidden> wrote:

> Thank for you tracking the issue about the openoffice crash in:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302160
>
> Other users have encountered the same crash and broken or corrupted fonts
> are not so rare.
>
> Could you give more information about the font so that the font
> librairy maintainer can check why it is not ignored (and send to
> the application leading to a crash).
>
> Was it a font corrupted in some random way by a disk problem ?

I cannot provide you with the details about the font nor the afm-file
any more, because when I fixed the corrupted afm-file, the problem went
away, and at the time of the last mail, I didn't remember any more which
font it actually was.

However, the details are almost clear in my mind: there were two 8-bit
characters in the corrupted afm-file: in the first case, a character
with the decimal code >230 had replaced (in emacs it looked like \238)
the return-char at the end of the line; in the second case, a character
in the name of a glyph in kerning tables had been replaced by a
charcter with the decimal code >230.

The cause was most probably a disk corruption, probably as a result of
running out of batteries on my laptop.

Greetings,

Harri Kiiskinen

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 23 Jun 2005 14:04:47 +0200
From: <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: corrupted fot should be ignored

reassign 302160 libfreetype6
quit

I wonder if it is fontconfig job ... though can fontconfig
detecty if a font has some weird characters inside (8 bit in an
afm file there).

Regards
Alban

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Thu, 23 Jun 2005 19:48:47 +0100
From: Will Newton <email address hidden>
To: <email address hidden>

severity 302160 normal

Changed in openoffice.org (Debian):
status: New → Incomplete
Changed in openoffice.org (Debian):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.