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


Hi Harvey,

I have been connecting sucessfully for several years to a MariaDB10
database in my local network domain using LibreOffice Base as client .
However, the current openSUSE release of LibreOffice blocks access to
it as it wants the database to support TLS/SSL. I am using the so-
called MySQL/MariaDB Connector.

OpenSUSE 15.6 here. Connected to a MariaDB with LibreOffice-packages from OpenSUSE mithout any problem. There is no ask for TLS/SSL at all. MariaDB is running on the same machine.>
Version: 25.2.4.3 (X86_64) / LibreOffice Community
Build ID: 33e196637044ead23f5c3226cde09b47731f7e27
CPU threads: 2; OS: Linux 6.15; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

This isn't the version of OpenSUSE - see Build_ID. It is directly from libreoffice.org. But this version also runs here without any problem.

This is a Build_ID of LO in OpenSUSE:
Build ID: 480(Build:2)

Regards

Robert
--
Homepage: https://www.familiegrosskopf.de/robert

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

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.