RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 674328 - [fix available] freefont-20060126-4.el5 causes icu to crash, making OpenOffice.org crash
Summary: [fix available] freefont-20060126-4.el5 causes icu to crash, making OpenOffic...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: icu
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Caolan McNamara
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-01 13:53 UTC by Jiri Koten
Modified: 2016-05-10 20:18 UTC (History)
1 user (show)

Fixed In Version: icu-4.2.1-13.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 20:18:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
abrt.log (70.63 KB, text/plain)
2011-02-01 13:53 UTC, Jiri Koten
no flags Details
~/.openoffice.org/3/user/registry (101.22 KB, application/x-bzip)
2011-02-01 13:56 UTC, Jiri Koten
no flags Details
output of fc-list -v (1.21 MB, text/plain)
2011-02-01 15:58 UTC, Jiri Koten
no flags Details
fix like so (591 bytes, patch)
2011-02-02 12:40 UTC, Caolan McNamara
no flags Details | Diff
fix some other crashers (2.00 KB, application/octet-stream)
2011-02-03 11:20 UTC, Caolan McNamara
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0781 0 normal SHIPPED_LIVE icu bug fix update 2016-05-10 22:35:52 UTC

Description Jiri Koten 2011-02-01 13:53:53 UTC
Created attachment 476398 [details]
abrt.log

Version-Release number of selected component (if applicable):
openoffice.org-writer-3.2.1-19.6.el6_0.5.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start openoffice.org-writer
2. Go to Tools > Options > Language Settings > Languages
  
Actual results:
Crash

Additional info:
Cannot reproduce on my machine but crash happens on our stable machines.

$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Comment 1 Jiri Koten 2011-02-01 13:56:05 UTC
Created attachment 476400 [details]
~/.openoffice.org/3/user/registry

Comment 2 Caolan McNamara 2011-02-01 15:21:17 UTC
This is a crash in icu and apparently due to some specific font.

Is the en_US locale information output from the affected machines ? We really need to find out what font is triggering this.

Can we get the output of fc-list -v > /tmp/fontlist.txt from an affected box

Comment 3 Jiri Koten 2011-02-01 15:58:22 UTC
Created attachment 476427 [details]
output of fc-list -v

icu-4.2.1-9.el6

Comment 5 Caolan McNamara 2011-02-02 11:57:25 UTC
The trigger is freefont-20060126-4.el5, which isn't part of the default RHEL-6 package set I believe.

Comment 6 Caolan McNamara 2011-02-02 12:40:49 UTC
Created attachment 476553 [details]
fix like so

Comment 7 Caolan McNamara 2011-02-02 12:42:21 UTC
Logged upstream as icu#8320

Comment 8 Caolan McNamara 2011-02-03 11:20:38 UTC
Created attachment 476745 [details]
fix some other crashers

freeserif is apparently a good test for stress testing icu

Comment 9 RHEL Program Management 2011-07-05 23:47:58 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 10 Caolan McNamara 2011-09-07 09:12:46 UTC
reportedly additionally this as well http://bugs.icu-project.org/trac/ticket/8800

Comment 13 Suzanne Logcher 2012-02-14 23:06:29 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 14 Steve White 2012-08-22 17:31:11 UTC
FreeSerif would indeed serve as a good stress-test.  It goes places few other fonts go.  But a recent version of the font would be an even *better* stress test, than the ancient 2006 version you refer to.

The current version of FreeSerif is 20120503
http://ftp.gnu.org/gnu/freefont/

Comment 15 Caolan McNamara 2012-08-22 19:46:07 UTC
Indeed, but this bug is from RHEL-6 and the version in EPEL-6 at the time of reporting was freefont-20060126 

You can/could log a bug against the gnu-free-fonts package to point out that the packaged version is archaic https://admin.fedoraproject.org/pkgdb/acls/bugs/gnu-free-fonts

I see that even the rawhide version is stuck at 20100919

Comment 16 Steve White 2012-08-23 08:18:00 UTC
Hi Caolán,

1) Yes, I think the 2012 version is very worthwhile.
   I can't easily bump them: the fedora site has certificate issues with login--I accepted their unverified certificate, but then Firefox said "unable to negotiate an acceptable set of security parameters".

2) Toward the present bug, I have a thought.  
The 2006 FreeFont (as well as the 2003 against which a similar crash is reported) both had corrupted strings in the "TTF Names" table.

   https://savannah.gnu.org/bugs/?15791

These were meant to be typographic samples in various languages.
In the 2008 release these strings were removed.  (I never saw application software that used them anyway.)

Just what had happened to get the strings in that condition I don't know,
but their encoding was not correct, and garbage appeared in most font software, and some software would come unglued.

Comment 21 errata-xmlrpc 2016-05-10 20:18:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0781.html


Note You need to log in before you can comment on or make changes to this bug.