[upstream] [3.1] DATA LOSS: openoffice oobase reports SIGSEGV in openjdk-6 when saving a report

[Matteo Settenvini]

See attached logfile.

Using oobase with openjdk-6 is a pain. First, CPU is almost always at 100% when editing reports. Second, opening a report in editing mode, dragging around a few fields, adding a couple of lines, saving the report, and trying to close the report editingwindow, results in a crash.

Should be considered severe, since ooo isn't always able to restore the .odb file, or restores it correctly (and then the tables have no records!!!). I would have lost almost 1100 company contacts this way, if I had not kept a Microsoft Excel (yuck!) spreadsheet with the data.

[Matteo Settenvini (tchernobog)]

I almost forgot:

openoffice.org is at 3.0.1~rc1-2ubuntu3
openjdk-6-jre is at 6b14-0ubuntu8

[Chris Cheney (ccheney)]

Does this happen every time you attempt to make a report, or just the one time?

For future reference using an early alpha version of Ubuntu for important work isn't a very good idea. :-)

Thanks,

Chris Cheney

[Matteo Settenvini (tchernobog)]

This happens every time I try to make a report, on closing the editor window. Sometimes crashes also when trying to run a report from the editor window, but I'm not sure it's exactly the same bug.

Overall, the report component of oobase is very prone to crashing the whole app.

@Chris: I know, that's why I take backups :-). Having people using early alpha of Ubuntu makes possible to fix bugs *before* they slip in LTS versions of Ubuntu ;-).

[Chris Cheney (ccheney)]

Do you still have this problem with OOo 1:3.0.1-1ubuntu1?

[Matteo Settenvini (tchernobog)]

Yes, this problem is still there.

[Chris Cheney (ccheney)]

Do you have this same problem with the official version of OpenOffice.org from http://openoffice.org/ when using openjdk-6 ?

[Troy James Sobotka (troy-sobotka)]

Definitely a show stopper bug.

https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/347069
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/347068

[Matteo Settenvini (tchernobog)]

@Cheney: using the debs from vanilla OOo (OOO300m15, build 9379) and openjdk-6-jre 6b12-0ubuntu6.1, the problem seems fixed (there have been major changes in the UI, too, so I get OOO guys worked on this recently).

[Troy James Sobotka (troy-sobotka)]

Sun's Java 1.6.0_12 selected under Options->Java fails as well.

Testing with lower versions.

@Matteo:
Is there a clean way to test the debs from oo.org as opposed to a manual installation of all 16 or so of them? Thanks for your help.

[Troy James Sobotka (troy-sobotka)]

Upon further testing:

Sun's 1.6.0_12: Failure as above.
Sun's 1.5.0_17: Epic failure. Won't even get to tables.
Sun's 1.6.0_0 Cacao: Failure as above.
Sun's 1.6.0_0 OpenJDK: Failure as given in the original report.

[Chris Cheney (ccheney)]

confirmed with sun-java6-jre and openjdk-6-jre on jaunty amd64.

[Troy James Sobotka (troy-sobotka)]

Confirmed that 3.0.1 downloaded DEBS (sudo dpkg -i o*.deb) and manually installing the sun-report-builder 1.0.6 (sudo /opt/openoffice.org3/program/unopkg add --shared /path/to/sun-report-builder.oxt) works.

At least we can work on Jaunty, which is a positive.

Using the Sun JRE 1.6.0_12 as installed from the repository.

[Troy James Sobotka (troy-sobotka)]

Drat.

Forgot to mention that this applies to amd64 testing environment. Apologies for the bugspam.