Description: Hello, I found a bug with LibreOffice (6.1/6.2/6.3). When you try to merge as unique document with lot of entries, it crashes. Here the steps to reproduce it: 1. Download the two attached files (exploitants47.ods and Surfaces_2019_fiche-instruction_AB.odt). 2. Open the file Surfaces_2019_fiche-instruction_AB.odt 3. Update database (Edit->Exchange database) and link with "explotants47.ods". 4. Go to File->Print 5. Say yes to the message 6. on the mailing view, set print in a file and save as unique document -> It will freeze LibreOffice forever If you don't save it as unique document, it takes time but it works. Thanks Actual Results: Freeze Expected Results: Generate the file Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 155566 [details] db
Created attachment 155567 [details] Write file to open
I can not reproduce with Version: 6.3.2.2 Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded in about 2min20sec all the 780 unique documents are created maybe only a windows problem???
LO doesn't freeze, but almost everything in menues and every icon in toolbar is greyed out (never seen that before). A document is created with 0kb (I waited 1minute). Perhaps I should wait longer. Version: 6.3.3.1 (x64) Build-ID: f41f4c7f9507aeca13cb9df51f34d80e8ba30a99 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Hi Jean-Sebastien Bevilacqua, How long did you wait before you killed LibreOffice ?
this could be issue: Bug 117480 - Mailmerge crash when saving merged document (only the first time the connection is done) it happens only if one uses "Edit->Exchange database" instead of registering the database.
I waited for 10 minutes without results. And yes I'm on Windows.
(In reply to Dieter Praas from comment #4) > A document is created with 0kb (I waited 1minute). Perhaps I should wait > longer. After 15 minutes I could use LO, but mail merge only created an empty document. Version: 6.4.0.0.alpha1 (x64) Build ID: cc57df8f942f239d29cb575ea5a7cb01405db787 CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: threaded
Dear Jean-Sebastien Bevilacqua, 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 Jean-Sebastien Bevilacqua, 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