[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#516863: openoffice.org-calc: Export... to XHTML throws up error message "JRE is defective" instead of working.



tag 516863 + moreinfo
tags

Willy Gommel wrote:
> In OpenOffice.org's File menu, there is an Export... command. I have a problem with it, because every time I use it to export a small spreadsheet file to XHTML, the following error messages pop up:
> 
> JRE is Defective
> OpenOffice.org requires a Java runtime environment (JRE) to perform this task. The selected JRE is defective. Please select another version or install a new JRE and select it under Tools - Options - OpenOffice.org - Java.
> Please install the openoffice.org-java-common package for this functionality.

Do you have this package install? Which JRE do you try to use?
(look in the mentioned Tools - Options - OpenOffice.org - Java)

> I believe the above error messages are spurious, mainly because the requested package has been installed from the very latest version.
> 
> As to whether JRE is indeed defective, I am hardly in a position to judge that, what with many hundreds of java packages to choose from on my machine. The same factor prevents my "choosing a different version". I know only this: until the last update of 

That doesn not make sense, sorry. a) it is clear whichJVMs OOo supports, it is written
in OOos dependencies b) it's also clear from OOos dependencies which packages you
need in addition.

What you could try is to check whether your OOo Java settings are broken, just delete
javasettings_*_.xml fom your user config and set it again in the Options.

> OpenOffice.org came through a week or two ago, the above error messages were unheard of on my machine.

It was longer than a week. 2.5 or so? Of course testing now got other updates...

> BTW, for the last month or two, I have been getting reports of "Invalid Color depth" error messages from users of machines trying to access .PDFs I have been creating with OpenOffice.org as well. I suspect that there is something fishy in that routine 
> as well.

And there's someting fishy that you put two unrelated things in one bugreport.
See also below and try with OOo3 if possible and if you're sure it's a bug in OOo file *another*
bugreport.

> -- System Information:
> Debian Release: 5.0
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'oldstable')
> Architecture: amd64 (x86_64)

Why are you mixing testing and etch? Bogus combination.

BTW: You are using a completely unsupported version, given how much packages
already droppped in from unstable to testing and that unstable is
adapted to OOo3 already, the OOo 2.4.1 in testing is not really supported by me
anymore, it won't get any fixes anymore (maybe only emergency stuff and security
if OOo3  isn't in testing by then, but nothing else)

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  rene@debian.org | GnuPG-Key ID: 248AEB73
   `-   Fingerprint: 41FA F208 28D4 7CA5 19BB  7AD9 F859 90B0 248A EB73




Reply to: