Red Hat Bugzilla – Bug 170391
OpenOffice.org spell check broken in Update 2.
Last modified: 2013-10-20 18:46:15 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.0.7-1.4.1 Firefox/1.0.7
Description of problem:
During the upgrade from RHEL4 U1 to RHEL4 U2, Open Office was updated to version 1.1.2-28.6.0.
Since this update the spell check does not work. When you run the check on a document (F7), it offers you the correct spellings for words as expeted, but when you select the "replace" option, it just skips on to the next spelling mistake without correcting the document.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open a new document
2. Write some words including some spelling mistakes
3. Hit F7 to spell check the document
4. When correct spelling is suggested, click 'replace'
Actual Results: It does not replace the incorrect spelling with the correct as suggested in the spell check window, and skips on to next mistake in document (if any).
Expected Results: It should replace the incorrect spelling before moving on to the next mistake.
i can reproduce this.
*** Bug 170516 has been marked as a duplicate of this bug. ***
(In reply to comment #3)
> writer only
I can reproduce as well. Is there a temp workaround, or do we have to go back
to version like 1.1.2-24.6?
This is pretty bad, all RHEL4 U2 installations are broken in this way. Can we
have someone look at this quickly?
The bug is fixed and the package is built. What remains is to grind through the
Note that this bug applies on RHEL3 U6 as well. I looked for a bug against
RHEL3 and didn't see one...
$ rpm -q openoffice.org
RHEL3 -> 171134
How many more months should we wait for a fix? How can RedHat Linux be ready
for the desktop prime time when the most basic function (spell check in word
processor) has been broken for 5 months?
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.