When opening Writer using a template for letter writing and enabling macros to insert data such as addresses or any other, the application immediately crashes and a crash report is created and sent. This occurred in LO7.1.1.2 and is now happening in LO 7.1.2.1. I do not know if it goes back to an earlier version. If I do not enable macros, the application goes ahead and opens the document, but if I hit the Data Sources icon, the crash occurs again. I am using the latest version of Windows 10 with the latest updates. I have not tested this on my Linux machine at home yet.
Thank you for reporting the bug. Could you please add the link to the crash report and perhaps attach a sample document, as this makes it easier for us to verify the bug. => NEEDINFO
Created attachment 174578 [details] Office Correspondence template I have experienced this bug since the version following 7.0.4.2 [LO last stable version]. I start the application, select a template, select enable macros, and the application crashes. I have also tried a blank writer document under Create and selected the data icon and the application crashes as well. After each installation from LO 7.0.4.2 I have tested the attached template with the new LO version and each time it has crashed. I have LODev 7.3.0.0 on the computer as well, and it does not crash when starting the template, but I notice that the dialogue to enable macros is different on the LODev from the LO versions.
[Automated Action] NeedInfo-To-Unconfirmed
Just checked the latest version of LO 7.2.1.2 after installing this morning. The same action occurs with respect to the collapse of the application when opening a file with a macro being enabled. see previous report dated 2021-03-19. It seems to me that this is more than of medium importance in the proper functioning of the program so I have up-marked it to major. Although I have uploaded my template in the past, you will need to have registered databases attached. The ones attached are addresses and CRF-A which is a database of project information which has proprietary information on it.
No crash with template from attachment 174578 [details] and Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: threaded 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.
Dear Charles R. Francis, 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 Charles R. Francis, 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