Openoffice on x86 crashes when "Finish" clicked in Wizard

[Danny Staple]

In OpenOffice Base, simply clicking on "finish" in the wizard will cause openoffice.org to crash. I found this while trying to reproduce Bug #60679 in Edgy.

This is on Edgy, with openoffice.org 2.0.3-4ubuntu2. It did offer to save my document though. This is aso 100%.

To reproduce (100% here):
* Click on OpenOffice Base, and go through the database wizard.
* Select Create new Database
* Leaving defaults click next, then finish.
* OpenOffice will now give you a "OpenOffice has crashed dialog", and a save file box to try to recover your database. Cancelling/saving and then clicking the ok button in the dialog will restart

If started from the command line - I see the following messages
  javaldx: Could not find a Java Runtime Environment!
  Can find no compliant libebook client libraries

Now the first message, I understand, but if there really was no environment, it would not run, so I am presuming that is merely no Sun recognised one. I can (note this) still use Office Writer documents. This occurs crash, or no crash. I have java-common 0.25ubuntu1, java-gcj-compat 1.0.63-0ubuntu1 and gij-4.1 4.1.1-13ubuntu2j2 installed.

The second message is repeated five times. This is shown as soon as the Database Wizard starts. Checking my box, I definately have "libebook1.2-9" installed.

[John Vivirito (gnomefreak)]

Thanks for your bug report. Could you please try to obtain a
backtrace by following the instructions on
       http://wiki.ubuntu.com/DebuggingProgramCrash.
This will greatly aid us in tracking down your problem.

[Danny Staple (danny-orionrobots)]

Tried this in 2.0.4~rc3 on Edgy, and it no longer occurs. Marking as fixed.

[John Vivirito (gnomefreak)]

Im unmarking it as fixed. dapper is LTS and i think since we wont backport OO.o 2.0.4 this needs to be fixed in dapper. If dapper wasnt LTS i would agree.

[Matthias Klose (doko)]

> Im unmarking it as fixed. dapper is LTS and i think since we wont
> backport OO.o 2.0.4 this needs to be fixed in dapper. If dapper
> wasnt LTS i would agree.

marking as fixed; you didn't even veryify that it's reproducible in dapper, neither with the released version, nor the version in dapper-proposed.

[Timo Aaltonen (tjaalton)]

yes, this was discussed on #ubuntu-bugs so rejecting this

[Danny Staple (danny-orionrobots)]

I had only ever raised this as an Edgy bug. So I agree with Matthias/Timo on this.

[John Vivirito (gnomefreak)]

Yeah i know i got bugs confused me and timo had talked about this on IRC