Description of problem: Version-Release number of selected component (if applicable): openoffice.org-*-2.3.0-6.5.1.el5_2 How reproducible: always Steps to Reproduce: 1. save an Impress file with password 2. create a new Impress file 3. Insert -> File -> open the file in step 1 -> press several ok button Actual results: ooimpress got crashed Expected results: Additional info: pls refer to <http://nfs.nay.redhat.com/xwang/logs/crash-insertfile>
Does this work with 2.3.0-6.5 the previous release ? I get this with the very latest release as well, so can you confirm that it is not a regression ? It's a most excellent qa discovered bug, but I suspect that its not a new one in this release.
Reproduced, and analysed, and I've logged the fix upstream as http://www.openoffice.org/issues/show_bug.cgi?id=90612 This isn't a regression from the previous RHEL-5.2 release and has existed in OOo for some time. So it shouldn't block the current security errata. So we should treat it as a normal bug and fix it in a normal bug-fixing errata if given the appropriate acks
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
checked in, will be in >= 2.3.0-6.7
This issue is also present in openoffice.org-2.3.0-6.5.4.el5_2
Yes, that's to be expected. This is a 5.3.0 bug, fixed in >= 2.3.0-6.7 (latest RHEL-5.3.0 build is 2.3.0-6.10) while openoffice.org-2.3.0-6.5.4.el5_2 is a 5.2.z security release. So the bug shouldn't be seen in 5.3.0 stream, but should remain in 5.2.z streams
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 therefore 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. http://rhn.redhat.com/errata/RHBA-2009-0121.html