Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Le 30/08/13 11:47, Heinrich Stoellinger a écrit :

Hi Heinrich,

Having just installed the released LO 4.1.1 version, I still keep getting
the same error as under 4.1.1-RC2 when trying to run a report based on a
MySQL-Database view (I tend to assume that they are actually the same
This prevents me from going to 4.1.1 (which I would LOVE to do!).
In addition to the error mentioned in my last post, I also get the message
"caught a java.lang.IncompatibleClassChangeError".

The reportbuilder has quite a few bugs registered against it, you might
want to look in bugzilla to see whether the one you are experiencing is
also registered. The user list isn't really the place for anyone to deal
with this, other than possibly confirm/deny the existence of the bug in
their particular setup.

The reportbuilder relies on, among others :
- the JVM version installed on your system and declared in LO ;
- certain LO specific configuration parameters which are sometimes
stored in the user profile, and sometimes in the application
configuration files themselves ;
- functionality that may or may not have been affected by other changes
during a particular release version of LO.

That should give you an idea of how complicated it can be to track down
a bug in this area.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.