Breakdown of libreoffice using Save as and save copy
I think I have stated that the error belongs to base, but I do not know if it is correct. I find it when I save a form so maybe I should say Writer
Please write down a little bit for description. What are you doing to get the crash?
Could you also give a try at https://wiki.documentfoundation.org/QA/FirstSteps? If you talk about Base, I suppose it's a form in an odb file. If yes, do you reproduce this with a brand new form in this odb file or a brand new form in a brand new odb file? What's the database used? embedded hsqldb, embedded Firebird, other?
Answers to questions: If you're talking about Base, I'm assuming it's a form in an .odb file. No, there is no error in the .odb file, it runs well and almost helps to remove the traces from the error, but it gets lost a bit in the dark. The files in question are .odt files with some forms did not give any errors, but some more complicated give errors. I simplified one of these to almost nothing, But the error did not disappear. ??? The database is used with embedded hsqldb. Note: I use a different file in this review than I used for the crash report the bug was reported on. At the bottom I change the error description. Error message: Due to errors, Libreoffice shut down. All files you were working on will be saved now. The next time libre office is started, your files will be restored automatically. The following file will be restored: Test view.odt. "Test visning.odt". The error occurs when the file is closed or saved. the file: Purchasebase.odb.lck contains (recovery file) HSQLLOCK v «Æà Upon reopening the file, Libreoffice goes into a perpetual LOOP. I stop by forcing libreoffice to close with a windows program. By re-opening the file, libre office displays an error report that it requests to be submitted. I have sent quite a few of these reports. HSQLLOCK v ¶w ---- HSQLLOCK v € Üë I have tried to identify the error on a smaller database and it was almost successful, but it seems as if the error changes character or is different than first assumed. After removing the file in remote, the file still fails when shutting down. the recovery file contains HSQLLOCK v € Üë Upon reopening, libreoffice goes into perpetual loop. I stop the loop as previously described. Indkøbsbase.odb.lck contains after repeated attempts HSQLLOCK v € å Ë I delete the content. I delete remaining threads from libreoffice with my windows program. I open the .odb file and neglect error messages. and close the .ODB file again. I open the test file again. I am uploading the following bug report: The crash report was uploaded successfully. You can soon find the report at: crashreport.libreoffice.org/stats/crash_details/43e09c20-fb73-4756-96b1-3125b2e467b1 This error appears as a message when I close the file and I get the option to upload it when I reopen the file. I have not used my windows program to stop this run. New error description: The program fails when I close the file with the forms (Test view.odt). (crash) When I reopen the file, libreoffice goes into a perpetual loop.
Crashreport is almost empty. You're talking about perpetual loop, about errors but it doesn't provide much info to investigate. Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps? (as indicated in my previous comment) If you still reproduce this, could you attach minimum step by step process to reproduce this?
Created attachment 168532 [details] self-extracting file. with database with form page that crashes when saved. I am attaching a self-extracting zip file with the minimized program that still has the error. The error is supposed to be associated with the list field, but has effect only when the file is saved. The file “Test view.odt” cannot be saved normally without the program crashing. In edit mode, the file can be saved and closed without errors. When stored in normal use mode, the program crashes and will send an error report. If you select "Do not save" when closing the file, the program will not crash.
Could you attach zip file? Indeed self-extracting zip is an exe, so relevant for Windows users, not for Linux or Mac users.
Created attachment 168537 [details] .zip with the reported error
Thank you for the feedback. I gave a try with the file but didn't reproduce the crash with LO Debian package 7.0.4 or with master sources updated today. (I changed a value and tried to save). It's perhaps a Windows only bug. It would be useful you retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace). For the moment, let's put this back to UNCONFIRMED.
Upon re-examination of the error, it turns out that it is not there in libreoffice 6.4.7.2, but in libreoffice 7.0 and 7.1 it is present
Hello Eigil, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Eigil Wiwe, 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 Eigil Wiwe, 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