Description: Libreoffice crashes when I launch Mail Merge Wizard, with different files connected with a MS Access database. I sent many crash reports when the problem happened. It doesn't happen with 5.4.2. Steps to Reproduce: 1. Open a file with MS Access DB fields 2. Tools-> mail marge wizard 3. The crash appens and the LibreOffice window disappear Actual Results: The crash appens and the LibreOffice window disappear Expected Results: The opening of the wizard Reproducible: Always User Profile Reset: Yes Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
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 139721 [details] One of the files that have the problem
I can't reproduce it in Version: 6.1.0.0.alpha0+ Build ID: 226804c8f7d2306562380283edfd919a88863807 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded nor in Versión: 6.0.1.1 Id. de compilación: 60bfb1526849283ce2491346ed2aa51c465abfe6 Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group
To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Was failing on: Version: 6.0.1.0.0+ Build ID: 9e7344ae5776117e94684713767fae1b0afbb6b9 CPU threads: 40; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-6-0, Time: 2018-01-30_11:33:05 Locale: en-US (en_US.UTF-8); Calc: group So I upgraded to this on the clone and it's doing the same thing: Version: 6.0.2.0.0+ Build ID: d1a4f50d686054b757320c0ef3f3dc4c724c685c CPU threads: 24; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-6-0, Time: 2018-02-22_03:27:32 Locale: en-US (en_US.UTF-8); Calc: group So the regression happened prior to the first daily build.
I already reset the user profile back to defaults, same thing. This is happening to all of us, this is not a user setting issue.
I can't reproduce it in Version: 6.1.0.0.alpha0+ Build ID: ddbb78caa78085673b07dbea6f53288ec6237764 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group
*** Bug 115969 has been marked as a duplicate of this bug. ***
no crash with Version: 6.1.0.0.alpha0+ Build ID: dc8d8cbf30ca3429236eca16b8f447ef5d4e61d3 CPU threads: 1; OS: Windows 10.0; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-02-28_00:00:19 but maybe we need ms access db file for reproduce? Could you paste crash report ID here?
Does it crash with an empty document? OTOH, might it be related to the address list you use ?
Could you please follow the instructions provided at this link < https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg > and submit a backtrace? That way a developer can look into the underlying reason of the crash.
Wait a minute, Dave reproduced this so this should be NEW. Would be cool to get a backtrace from Dave.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The bug is still present. Versione: 6.2.3.2 (x64) Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac Thread CPU: 4; SO: Windows 10.0; Resa interfaccia: predefinito; VCL: win; Versione locale: it-IT (it_IT); Lingua interfaccia: it-IT Calc: threaded Best regards. Andrea
Dave: could you get a backtrace of the crash on Linux?
The crash happens on W10, I don't know if it happens on Linux and I can't verify it, because I dont't have any PC with Linux.
(In reply to fratelliferretti from comment #16) > The crash happens on W10, I don't know if it happens on Linux and I can't > verify it, because I dont't have any PC with Linux. In comment 5 we learned from Dave that it happens on Linux.
This bug wasn't reproducible for all, but also doesn't have sample database. Please retest with current LO you are using and attach minimal sample database without personal data.
We don't know if it's MDB or ACCDB and how it's accessed by LO.
Dear fratelliferretti, 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 fratelliferretti, 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