Created attachment 117821 [details] Sequence of creating and connection to a MariaDB database on localhost. When I try to connect to a MariaDB database in Libreoffice 5.0.0.5 (x64 using jdk8 and jdk 7, both x64) on Windows 7 and 8.1 Base crashes. Driver is included in both JDK installations and is loaded. Connection in wizard can be established but program crashes as soon as database file is loaded. I can't find a useful log file. If somebody tells me where to find one I can attach it here.
@Andreas : don't know about a Windows specific log, but there might be a hs_error_pid file lying around somewhere that the JVM creates.
Found a command line parameter to pass to JVM to force it to create this log file but it did not create it. The only thing i found in the temporary folder was a file which had the process id as name but it did not contain any useful information.
We need someone running Windows 64bit with LO 64bit to confirm.
I can confirm with Version: 5.1.0.0.alpha1+ (x64) Build ID: e0b0501452e6a72ba800ae9f536d766f8111ed78 TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-08-19_01:09:37 Win10
This link may help: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace
I see same crash issue in Base Database with: * Windows 7 Ultimate 64-bit on an i7 920 * LibreOffice 5.0.2.2 (x64) * Java SE Developer Kit 7 Update 85 (64-bit) * PostgreSQL 9.3 JDBC4 driver in DbVisualizer Free 9.2.10 (64-bit) * PostgreSQL 9.4.4 server in FreeBSD 9.3 jail on FreeNAS 9.3. I see no crashes with the PortableApps LibreOffice 5.0.2.2 (32-bit), so something must be messed up in the 64-bit version. DbVisualizer 9.2.10 (64-bit) connects OK too. Sorry, but I won't be installing any Microsoft debugging bloat because it can take up a loads of space and can be a pain to cleanly get rid of later; anyhow LibreOffice should provide it's own debug logging/capture for this, not the useless error message I saw.
*** Bug 95227 has been marked as a duplicate of this bug. ***
Also occurs with mySQL connector 5.1.37.
*** Bug 93396 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
On Win10 + master sources updated today, both 64 bits + mariadb-java-client-1.7.1.jar + pure JDBC (not Mysql then JDBC), I don't reproduce the crash. (I used "org.mariadb.jdbc.Driver" for classname) Idem with LO 6.1.5. Could someone give it a new try with a recent LO version?
Dear Andreas Gottardi, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Andreas Gottardi, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp