LO Write crash when use the EXCHANGE DATABASE button in mail merge: I ha a write file that use a ODS (Calc) file like database. I connect my write file to CALC (ex DOCUMENT1) by "mail merge" funcion. When i exchange my write file to new Calc document (ex DOCUMENT2) the write document crash during the final step.
Please don't autoconfirm your own bug. Also, could you provide a package with minimal test files (odt+ods) + minimal step by step process to reproduce this?
Created attachment 178728 [details] Write document with mailmerge fields
Created attachment 178729 [details] Calc database (actual)
Created attachment 178730 [details] Calc database with new data (i want to change to it)
Note: the CALC spreadsheet is in SHARING mode (Tools -> Share document). --- My file was resident in a network folder. WRITE file (Test_bug_mailmerge.odt) is connect with mailmerge field to the CALC file (prev.ods). I want to change the CALC file with a new CALC file (next.ods) that have the same fields but different data. STEP. 1) open the "Test_bug_mailmerge.odt" 2) menù TOOL -> MAIL MERGE WIZARD 3) select Button "exchange Database". 4) select file "next.odt" and "Foglio1" (or in ENG "Sheet1")-> (a warning was display that is a Share spreadsheet document). [NOTE: the exchange database windows goes behind the windows wizard, maybe this generate the bug]. I press again exchange database button. 5) select DEFINE button -> NEXT button -> NEXT button -> END button. now the exchange database windows is already open. I press DEFINE button and it close the exchange database windows. Now the WRITE is freeze and the mouse pointer is a circle rounding ... i close the Write and the windows 10 messagge display "Libreoffice Write not responding".
(In reply to Julien Nabet from comment #1) > Please don't autoconfirm your own bug. > > Also, could you provide a package with minimal test files (odt+ods) + > minimal step by step process to reproduce this? I've provide a package with minimal test files and step by step process. i've change the status to UNCONFIRMED. Is all rigth?
I've change in NEW because is confirmed in "Crash report or crash signature". Is rigth?
I could not reproduce with: Version: 7.2.7.2 / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Nor with: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Could you please test again in a supported version (7.4 or 7.5), to see if you can still reproduce the crash? Note that you can quickly exchange a database with Edit > Exchange Database. (crash report shared by marco: https://crashreport.libreoffice.org/stats/crash_details/68deff01-9ae9-4832-a62a-0733200a36f1, crash signature doesn't show up for 7.4 or 7.5)
Dear marco.jj, 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 marco.jj, 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