You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2014/01/24 14:26:22 UTC
[Bug 124102] New: Unable to validate java installation
https://issues.apache.org/ooo/show_bug.cgi?id=124102
Bug ID: 124102
Issue Type: DEFECT
Summary: Unable to validate java installation
Product: General
Version: 4.0.1
Hardware: All
OS: Windows 7
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: ui
Assignee: issues@openoffice.apache.org
Reporter: bty-adminf1@trebly.net
CC: issues@openoffice.apache.org
Created attachment 82384
--> https://issues.apache.org/ooo/attachment.cgi?id=82384&action=edit
The xml java config file " javasettings_Windows_x86.xml" of openoffive 4.01
At first load of (supposed any openoffice application, checked with Writer) I
get the error "invalid java".
I have to check OK on Six messages.
Then opening options/java I get the good version.
I can close OpenOffice during the user session I will not get back the error.
The reference of java (x86 version recently updated to 1.7.0_51, I have too,
for other applications, the x64 version and old inactivated versions)
The javasettings_Windows_x86.xml file joined seems OK.
So I don't understand what happens.
I don't know what to check else and I have no criteria to filter java registry
keys.
The error is always in the defined conditions.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 124102] Unable to validate permanently java installation, error
no valid java at system restart
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124102
trebly <bt...@trebly.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bty-adminf1@trebly.net
Summary|Unable to validate java |Unable to validate
|installation |permanently java
| |installation, error no
| |valid java at system
| |restart
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 124102] Unable to validate permanently java installation, error
no valid java after system restart
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124102
--- Comment #2 from trebly <bt...@trebly.net> ---
Still unable to validate Java installation and no Java functions
Another way to explain :
I need to use Java x64 for Eclipse and other softs.
As OpenOffice is an x32 application, even running on a x64 system the right
version of Java to use with is the x32.
Both installation are done and on each cpl they are activated (with different
parameters : default for x86 and for x64 large memory options needed by Eclipse
to run fast).
>java -version gives :
C:\Users\BTy-Admin-N2x.BTY-ASUSG73>java -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
When OpenOffice Writer starts I get 9 messages of Java load error.
Then when I run OpenOffice : options/java the x86 installation is found (while
x64 Java directory is said as not containing valid Java).
At OK no error message is displayed, but
no functions depending of java are running (as orthography check)
the help:search generates the error message of no valid installation.
Since years, never I got any problem. This is new. I have not found any special
instruction for running both x32 and x64 and OpenOffice recognition of java
installation.
Why as Java is not running well the option:java panel finds the right directory
and installation but don't send at OK any message to say that "finally" java is
not running for OpenOffice ?
Thank for help or reproduce a bug.
I think that these errors can be an issue of the java launch when both x32 and
x64 are present on the same x64 system.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 124102] Unable to validate permanently java installation, error
no valid java after system restart
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124102
Edwin Sharp <el...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needhelp
CC| |elish@apache.org
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 124102] Unable to validate permanently java installation, error
no valid java after system restart
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124102
trebly <bt...@trebly.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Unable to validate |Unable to validate
|permanently java |permanently java
|installation, error no |installation, error no
|valid java at system |valid java after system
|restart |restart
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 124102] Unable to validate permanently java installation, error
no valid java after system restart
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124102
trebly <bt...@trebly.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needhelp |usability
--- Comment #3 from trebly <bt...@trebly.net> ---
Hi,
Got the explanation, verified.
The extended parameters for java were wrong the value for -xms was defined for
x64 version. Then java launch was crashing at start.
I could not really check why all java launch were crashing while these
parameters were not defined into java.cpl but only into ooe parameters (I had
not checked them, because there was normally no reason to not have default
values)
The problem for which I do think that a little development should be done :
- When OK button for java installation identified version validation is hit, a
launch of java and check should be done.
Actually there is no check, then the user think that java is running : if a
function like "search" into help is immediately performed then an error message
is displayed.
So the user have usability default and non functioning various features without
visible reason, when ooe/writer is launched again later the same check is
performed and issues to error message.
The like validated OK and later the check at starting with error is then
completely confusing user and administrator. They can think that java
installation is not memorized while it has never been valid...
Reports into several forum, time to time of java installation errors are may be
reported for the same reason.
Hope to help.
Best regards
Trebly
note : the orthography failure was another problem reported separately.
Typically note that it occurs several times that "repair" installation misses
to reinstall needed extensions or create directory accidentally deleted (the
reason to reinstall which crashes ooe.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 124102] Unable to validate permanently java installation, error
no valid java after system restart
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124102
trebly <bt...@trebly.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest|--- |4.0.1
Confirmation on| |
--- Comment #1 from trebly <bt...@trebly.net> ---
Hi,
Still without solution.
Even with help which is clear and well known previously, I remain unable to
activate correctly and permanently JAVA (reinstalled 1.7.0_51)
Found by menu option/java with parameters, but not activated nor saved with no
error message.
May be a problem with administrator rights. The user which installs is myself
main-admin, but as this account is used most of time in developments it has to
be re-created. The old account damaged by a trojan has been suppressed and
replaced, it seems that some products memorises the original creator which
don't exists any more but don't checks the current registry and note simply the
owner as unknown...
To search and check of all occurrences of the old main admin name as owner is
awful.
How to check and why The OK on identification of the java installation don't
gives any error message ?
Others products seem to find java.
Please confirm which registry key and or contents of file
javasettings_windows_x86.xml must be checked.
Thank's
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.