Apache OpenOffice (AOO) Bugzilla – Issue 120035
AOO 3.4 fails to install with JRE Platform SE 7U5 under WinXP x32
Last modified: 2012-08-28 07:30:20 UTC
Created attachment 78393 [details] Error message AOo Having upgraded JRE on PC, existing installed OOo 3.3 as well as upgraded installed AOo 3.4, both gave consequent "JRE is defective" multiple errors during start up. A0o 3.4 does not recognize, or is incompatible with, Java Platform SE 7 update 5 (1.7.0_05). My only solution was to also install the latest previous JRE version (1.6.0_33), and set AOo and OOo to use only this Java version. However, this is not optimal, and a security risk.
Duplicated *** This issue has been marked as a duplicate of issue 119993 ***
Hi Solver / Editor of this Bugzilla Reported this bug 12005. received 3 mails in reply thus far, with following status for AOO and Java JRE 5u7 problem report on this apache.org issue website:- 1. My bug 12005 now marked as duplicate of bug 11993. 2. Bug 11993 marked as duplicate of bug 119525. 3. Bug 120046 marked as duplicate of bug 119525. Thus as far as I can make out, only valid bug number, at present, is bug 119525, which must give a SOLUTION for the bug problem reports (12005, 11993, 120046). Forgive the basics, but this is my first report of anything in bugzilla ! 1. When can a SOLUTION be expected? 2. How do access this SOLUTION (in Bugzilla, or will personal email arrive as am part of cc)? Thanks for clarity.
(In reply to comment #2) > Forgive the basics, but this is my first report of anything in bugzilla ! > 1. When can a SOLUTION be expected? Developers can only fix bugs they can reproduce on the computer they work. This is something logical, as developer cannot travel to go home and do their work there. So far, no developer was able to reproduce this bug, so we can't start working on fixing it. > 2. How do access this SOLUTION (in Bugzilla, or will personal email arrive > as am part of cc)? All activity related to a bug is tracked on the bug itself, so that adding yourself to the CC List is enough to get notifications about status updates. This bug is resolved as duplicated, you should add yourself to the CC List in Bug 119525
After several hours back and fourth I finally found that was the installed extensions the culprits. To solve java related issues remove extensions one by one until you find the culprit one or ones. Maybe it is easier to say than to implement it, but extensions should not crash the main program, no matter how bad they behave: they should crash by themselves and let users know what is going on. NB
close as dup