Created attachment 117165 [details] demonstration database: enable macros and open Form1, follow instructions there When the database browser is hidden via macro using the method.SetVisible(False), if a Base Report is opened and then the report window is closed, the Form used to open the report via macro is unexpectedly is closed as well, along with the whole database. The report window should be treated like a Form window and should be closeable without closing everything regardless of whether the database browser is .SetVisible(False). Alternatively, when you close the report's Writer window, it should not close a hidden database that has an open Form. If is not possible to artfully macro around this, as the report window does not seem to have any macro events. This is presumably one of several non-integration bugs from the implementation of jFreeReport. Using Windows 7 LO 5.0.0.2
Version: 5.1.0.0.alpha1+ Build ID: 9136f2344af88d524b6c10b6b2dfd6017bba60ec Locale: fr-FR (fr.UTF-8) Confirming
Reproduced on OSX
I have tested this: Set the database unvisible (first button). Opened the report (second button). Closed the report (only the report) by choosing "Close Document" (not close the window of the windowmaker) or "File" → "Close" Both ways the database isn't closed because the entry-menue is opened instead of the report. The form is also open. If I close the report-document by coosing taking the 'X' from the windowmaker it will close the whole LibreOffice - also the opened form. This is different if I open the report directly from base without hiding the window. "File" → "Exit LibreOffice" will close all opened windows - if visible or hidden it makes no difference. So I could confirm the database is unexpectly closed when choosing the close-button of the windowmaker. This behavior is the same in all LO-Versions I have installed - also 3.*-Versions. My system: OpenSUSE 13.2 64bit rpm Linux
I would tick the importance of the bug down a notch because there is a partial workaround by watching the state of the Writer window via macro and hiding the Base application window again when the Writer window is closed. Base macros seem to be multi-threaded, allowing the applications to continue normally while the Base macro loops looking for the size.width of the writer window to go to 0 or the .isVisible to go to false, at which time it hides the application window. The need for the first `Wait 50` below illustrates another oddity of LO Basic, which is that sometimes instituting a `Wait` is necessary to allow the application to finish reaching the desired state before continuing. appWindow.setVisible(True) appWindow.isMinimized = True Wait 50 writerRept = reportContainer.open writerCntrllr = writerRept.CurrentController writerFrame = writerCntrllr.Frame writerWindow = writerFrame.getComponentWindow i = 0 sz = writerWindow.getSize.Width vis = writerWindow.isVisible Do While sz > 0 And vis = True And i < 100000 sz = writerWindow.getSize.width vis = writerWindow.isVisible i = i + 1 Wait 10 Loop appWindow.setVisible(False)
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Created attachment 136996 [details] the odb that crashes I can provide a mysql dump if needed but I think it will not be necessary.
Comment on attachment 136996 [details] the odb that crashes odb crashes after closing the main BASE window if opened with macros enabled.
Created attachment 136999 [details] bt with debug symbols from ODatabaseDocument::connectController message On pc Debian x86-64 with master sources updated yesterday + enable-dbgutil, I don't reproduce the crash but I got a hang when trying to open the file. I noticed too this message: warn:legacy.osl:12259:12274:dbaccess/source/core/dataaccess/databasedocument.cxx:808: ODatabaseDocument::connectController: this controller is already connected!
** 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
Bug still exists with version: 6.1.3.1 on OpenSUSE 15, 64bit rpm Linux.
Dear Doug, 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
*** Bug 143010 has been marked as a duplicate of this bug. ***
Still present, judging by duplicate bug 143010
Dear Doug, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug