Description: I normally download a .ODS file, fill it in and click on an 'Activate' button to generate another file .ODS file which I upload to file my tax returns. When I disable macros as recommended it works fine upto the point where I have to click on the 'Activate' button, then it generates an error. Steps to Reproduce: 1.Open file 2.Enable Macros 3.Fill in tax details and click Next button 4.End tab has a validate button 5. Click on the validate button to create another .ODS file Actual Results: Error: An Exception occured Type: Com.Sun.uno.Runtime Exception Message:. Highlighted: Function getUniqueName (oContainer,sName$) .... Do While oContainer.hasByName(sNew) oContainer.removeByName(sNew) Expected Results: Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 6.2.8.2 Build ID: 1:6.2.8~rc2-0ubuntu0.16.04.1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Note that the attachment will be public, remove any sensitive information before attaching it. See the QA FAQ Wiki,https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F, for further detail.)
Dear depotke, 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 depotke, 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