Apache OpenOffice (AOO) Bugzilla – Issue 17223
OOo crash creating report
Last modified: 2006-05-31 14:29:06 UTC
When I create report OOo crashes or fills the document without several information. Situation: - MySQL 4.0.11a - ODBC MyODBC 3.51.06 - Java 1.4.1_02 (same problem with other jre) I'll attach some error report and files Davide
Created attachment 7913 [details] crash report
Created attachment 7914 [details] A report when OOo didn't crash
Created attachment 7915 [details] Another crash error report
I see from the crash logs that you're using glibc-2.3.1. That version has known problems. Can you update to glibc-2.3.2? Which distro are you using?
The distribution I'm using is Mandrake 9.1. I'll try if I can find the update. If it's not possible I'll try to recompile it. Davide
Replacing glibc is not for the faint at heart. It's possible Mandrake has fixed the glibc-2.3.1 bugs in their local copy, too. It was only Debian and Gentoo that have known problems with glibc-2.3.1. Say, was this rc1 or rc2? If it was the older candidate, you might try OpenOffice 1.1rc2, it has a number of bugfixes. I have to say I don't have any idea where to go with this one. Maybe try different ODBC drivers; there's a tiny chance that will affect this. We already know that UnixODBC had a crash bug, which they recently fixed. BTW, which JREs did you try with? But I did see something that worried me a bit: crash_report.bin itself crashed, saying /usr/local/OOo-1.1/program/crash_report.bin: error while loading shared libraries: libpng.so.2: cannot open shared object file: No such file or directory Could you do 'locate libpng.so' and tell me what it says?
I've updated the glibc to 2.3.2 and the problem remains. The OOo version is the italian localized RC1. I'll download the english version and I retry. I'll also will try with the newest version of unixODBC. I've tried different JREs: 1.4.1_02 and 1.4.2 without success. I'm not optimistic because the behavior changes a lot between ODBC and JDBC so I think the db support is still unstable. I don't have the locate command but ldconfig -v reports that libpng.so.2 does not exist. It exists libpng.so.3. Davide
Ok. With unixODBC 2.2.6 the system does not crash. It remains a problem: when I create a report the text fields, instead of real values, report "Ut wisi enim ad minim". In any field and just at the first record. the other records the text field is void. The other fields numeric and date seem OK. Davide
Nothing to do. Also with RC2 the "Ut wisi enim ad minim" problem remains. Davide
"Ut wisi enim ad minim" is a placeholder text which is used during creating the report, but should not persist when it's finished. If it, for you, *does* persist, please submit another issue for this and assign it to bc@openoffice.org. Thanks
OK, it was an UnixODBC bug, then! Great! BTW, ldconfig won't tell you about compatibility symlinks. You'd need to do ls -l /usr/lib/libpng*.so* maybe to see whether the compatibility symlink for the older libpng was missing. And it looks like libpng.so.2 and libpng.so.3 are in different packages, at least on Red Hat 8: $ rpm -q -f /usr/lib/libpng.so.2 libpng10-1.0.13-5 $ rpm -q -f /usr/lib/libpng.so.3 libpng-1.2.2-6 so it looks like the gui crash reporter is going to fail on distros that don't include libpng10! Time for a bug report against Mandrake (for not including libpng10) and against OpenOffice (which can't rely on the system providing libpng10). I'll file the latter one. Thanks!
closing INVALID
change subcomponent to 'none'