Activity log for bug #60981

Date Who What changed Old value New value Message
2006-09-17 22:57:35 Danny Staple bug added bug
2006-09-17 22:58:57 Danny Staple description 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 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. 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.
2006-09-19 04:26:50 John Vivirito openoffice.org: status Unconfirmed Needs Info
2006-09-19 04:26:50 John Vivirito openoffice.org: statusexplanation 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.
2006-10-06 20:15:12 Danny Staple openoffice.org: status Needs Info Fix Released
2006-10-06 20:15:12 Danny Staple openoffice.org: statusexplanation 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. Tried this in 2.0.4~rc3 on Edgy, and it no longer occurs. Marking as fixed.
2006-10-06 20:36:20 John Vivirito openoffice.org: status Fix Released Confirmed
2006-10-06 20:36:20 John Vivirito openoffice.org: statusexplanation Tried this in 2.0.4~rc3 on Edgy, and it no longer occurs. Marking as fixed. 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.
2006-10-06 20:56:31 Matthias Klose openoffice.org: status Confirmed Fix Released
2006-10-06 20:56:31 Matthias Klose openoffice.org: statusexplanation 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. > 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.
2006-10-06 20:58:55 Timo Aaltonen openoffice.org: status Unconfirmed Rejected
2006-10-06 20:58:55 Timo Aaltonen openoffice.org: statusexplanation yes, this was discussed on #ubuntu-bugs so rejecting this