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


Besides the general problem of LO 3.6 not starting due to duplicate UNO implementations caused by the bundled extension prereg mechanism, there are also reports for a more specific problem of not starting due to duplicate UNO implementations of org.openoffice.comp.connectivity.pq.Driver, <https://bugs.freedesktop.org/show_bug.cgi?id=53246> "Libo36 does not start, InvalidRegistryException from program/services/postgresql-sdbc.rdb." This appears to be caused by an old postgresql-sdbc-*.oxt installed per-user or shared (<http://wiki.documentfoundation.org/PostgreSQL-SDBC>) while the same functionality is included as a non-extension today (<http://cgit.freedesktop.org/libreoffice/core/commit/?id=c97d74b5f0608866bad3f7ae943811bdff4f7986> "fdo#45090: Changed postgresql-sdbc from bundled oxt to proper optional part.").

<http://cgit.freedesktop.org/libreoffice/core/commit/?id=f50a41437ee99aee499dbabd1d36ef8197db5559> "fdo#53246 Fresh postgresql-sdbc implementation names" works around that on master, with a rather trivial patch of choosing new names for the relevant UNO implementations. I verified that it does not break things with the instructions from <http://lists.freedesktop.org/archives/libreoffice/2012-January/024333.html> "[Libreoffice] [PATCH] rpath / ... for extensions (and the case of PostgreSQL-SDBC)."

Please review and consider for backporting to libreoffice-3-6.

Thanks,
Stephan

Context


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.