Description: When you try to use a database that works well in LibreOffice 6.2, in LibreOffice 6.3 Base on different machines in different places when loading and forming forms, it crashes and falls into a cyclic loading-an error and does not load. Crashreport on W7x32: http://crashreport.libreoffice.org/stats/crash_details/936fd856-98b2-488c-ab42-71f103594c92 On W10x64: crashreport.libreoffice.org/stats/crash_details/fb066ce2-fd66-41c6-bbd1-0accf2bed0f3 Steps to Reproduce: 1.LibreOffice 6.3 + external DB Firebird + network multi-user mode. 2.Opening forms with iframes Calc attachments-documents that are formatted during the download process, listeners and control buttons are installed (inside Calc). 3.The formation of these OLE objects fails. Actual Results: 6.3 LibreOffice Base fails, the attempt at recovery and attempt to reboot. Always unsuccessful. Expected Results: In LO6.2, the form is loaded, formatted, control buttons are created in IFrame-calc. Then the work and changes in the IFrame-calc document take place. Reproducible: Always User Profile Reset: Yes Additional Info: Here's the message: The failure report was successfully sent. It will soon be available at: crashreport.libreoffice.org/stats/crash_details/936fd856-98b2-488c-ab42-71f103594c92 Check the report if there are no related error reports yet, please create one on bugs.documentfoundation.org ahhh! Add details on how to reproduce the failure and the above ID in the crash report field. Thank you for Your help in improving LibreOffice.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Created attachment 153427 [details] Database-LibreOffice + database-Firebird + Macro-Library Added to the archive. It database + Firebird + 2 macro libraries. Macros should be transferred to the libraries of the LO. Macros from the Library1 library should be moved to the Standard folder. Access login - SYSDBA, password - Kadet1802.
In order to create a crash program you need to run the form "Заявка" or "Заказ"
So, failures LO 6.3 have themselves I won. The reasons for them were two problems: 1. The SupportsService method stopped working. Bypassed by the method Identifier. 2. As far as I understood, there was an error exceeding the amount of information about the formatting of the document line Calc. The line was as follows: Dim TableBorder As New com.sun.star.table.TableBorder oDoc = ThisComponent oSheet = oDoc.sheets(0) oRange = oSheet.Rows().getByIndex(101) aBorder = oRange.TableBorder The crash was on the last line. Reduced oRange and everything went: oRange = oSheet.getCellRangeByPosition(0,102,20,102) However, I will not switch to LO 6.3 yet. It's too slow in my database. In the Iframe-calc attachment of my forms macros create a lot of any buttons. They are attached to the cells and, apparently, because of this, they begin to tremble and jump. Like constantly redrawn with changes. In General, in LO with these bindings a long-standing problem. I couldn't even level them properly. But in previous versions, though they stood still and worked, and then dance and do not always work. Drawing is very slow.
[Automated Action] NeedInfo-To-Unconfirmed
@Kadet : please try with LO6312 just released to see if your problem has gone away and report back here. There was an issue with crashing reported in bug 126588 (Firebird view crashes) that has since been fixed and this might have an impact on your bug report.
Where to put DBLibrary and Library1 precisely? I mean, I got AppData\Roaming\LibreOffice\4\user\basic and this directory contains Standard
Loading files with 6.3.0.0 beta1 or with 6.3.3 mixed soup ! I have on screen files opened with one version and other files with hhe other version. If I open a new file; I don't know the next version is used. LOL.
(In reply to Gérard DUBOIS from comment #8) > Loading files with 6.3.0.0 beta1 or with 6.3.3 mixed soup ! > I have on screen files opened with one version and other files with hhe > other version. If I open a new file; I don't know the next version is used. > LOL. It's better to have only 1 version of Libreoffice on a computer if not you must follow https://wiki.documentfoundation.org/Installing_in_parallel. Anyway, your comment isn't related to the bugtracker.
Dear Kadet, 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 Kadet, 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