Description: Im a teacher and I use serial letters (form letter) to print the achieved points per excercise for each student. Each serial letter (written with LO-Writer) has a similar structure. In the process of creating a new serial letter, I always copy an old serial letter. This process is important to save time, but in my opinion this is also the cause of the crash. Afterwards I click (in german) "Einfügen --> Feldbefehl --> weitere Feldbefehle" and then "Datenbank --> Seriendruck-Feld" to connect the odt-file with the database of the ods-file. Usually LO-Writer shows me in the list of databases the ods-file, but does not offer me to unfold the database, so that I can select a table/column of the ods-file. Continueing in LO-Writer leads to a crash. After some time I found a solution. First you have to delete ALL OLD REFERENCES in the serial-letter. After doing so, the connection to the new ods-file succeeds and there are no more crashes. This is not intuitive and should not be the way how the user should act. Steps to Reproduce: 1. Copy on old ODT-file (and rename it) which was a serial letter with references to an old ODS-file. 2. Leave old column-references in the ODT-file 3. Connect the (new) ODT-file to another ODS-file. 4. Now the imported database does not offer you unfolding und double clicking it or importing again and again often leads to a crash. Actual Results: The program crashes. I thing because there is a mixture of references. The programm is connected to a nrw ods file, but in the odt-file there are references to columns of an old ods-file. Expected Results: When the user connects to a new ods-file (databse), it should delete all old references to the old ods-file. It should also open a prompt and tell the user, that that will happen. Reproducible: Always User Profile Reset: Yes Additional Info: This bug is very old. I hoped since many years this will be solved but today a installed the newest version and it did still exist so I decided to report the bug.
Thanks for the report. I tried reproducing the crash with my own sample files but could not. Can you please provide a zip of sample files, with precise steps that reproduce the crash with those files? And how exactly do you to the new ODS? Using "Exchange database"? Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
(and if you see the Crash Report dialog, please do sent a crash report and share the link to it here. Thank you!)
Dear Benjamin B., 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 Benjamin B., 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