Description: LibreOffice 6.3.3.2 MSI install inserted a bar graph into an open LO Write document, then suggested saving it. When I started to install LO 6.3.3.2, I didn't notice that I had a Write document open (from LO 6.2.something, I think 6.2.3.2). When I did notice, I switched to it, and saw my document as I'd left it. I wasn't sure if I'd saved it since making edits. As I was about to save it, suddenly a generic-looking bar graph with orange and blue bars appeared, while the MSI install was churning away doing "validation" or probably something after that. I tried to undo several times, but I seemed to have reached a limit on undo's. The bar graph wouldn't disappear, despite all the undo's. So I did a SaveAs. I'll have to compare the 2 documents. The install completed fully, but it's a pain and very unexpected, unwanted behavior. Steps to Reproduce: Unsure if all steps below are needed, but: 1) On an AMD64 machine with Windows 10 and LibreOffice 6.2.3.2, and IO Bit Software Updater 2.2 and Google Chrome as the default browser, open a Write document. 2) Make edits to it, without saving. Or, possibly, make edits and save.) 3) Open several other apps, including different browsers with many tabs, so that leaving the Write doc in the background, and CPU/RAM are stretched thin. 4) In Software Updater 2.2, initiate the download (in Google Chrome) of LO 6.3.3.2 as LibreOffice_6.3.3_Win_x64.msi. 5) From Chrome, run LibreOffice_6.3.3_Win_x64.msi (6.3.3.2). 6) During "validation" process of LO install, switch to LO Write doc. Attempt to close. It must not close at this point, which is the point of having Chrome & Edge or Firefox open. 7) Switch back and forth between install MSI and LO Write. Observe if anything is inserted into LO Write doc. 8) If bar graph is inserted, attempt to undo to make it go away. 9) Do a SaveAs, naming it something else. 10) Window pops up in install, suggesting hard-close of Write. 11) Choose hard-close. Actual Results: A generic bar graph was inserted into the middle of my Write Doc. Undo would not make it go away. After several undo's, the undo option "greyed-out". Option to hard-close suggested by install. Expected Results: No changes to open LO files performed by new LO install. Ability to close/save open LO files. Reproducible: Didn't try User Profile Reset: No Additional Info: I will try to attach bar graph. For some reason, Google Chrome would not allow me to submit bug report, claiming (falsely) that I'd failed to choose a version. I tried several times, and verified that I had chosen 6.3.3.2 release. I had to copy this from Chrome to Edge.
Created attachment 156410 [details] Write document I had open, with (unwanted, not-undo-able) bar graph inserted
I can delete the bar graph in your attachment Version: 6.3.3.2 Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded
Wow, that is a weird one. The values in the added chart object (which with selection can simply be deleted) are present in our Standard templates for the 'Classy_Red' Object 1 [1] and for qa testing during build [2] And the ODF Text document (.odt) attached is annotated as a 6.3.3.2 prepared document--so the update from 6.2.x was probably completed. Although your edits after the update probably would have obscured if changes had been made while update was ongoing. But, other than identifying where the errant chart originated, very unlikely this is a common/reproducable incident. We'd like to know why, but reality is we probably will never know. Are you aware, or can you find out, does the 'IObit Software Updater v2' log its installation/package actions? If it does and there is a detailed log of the MS Installer package's actions--we might get lucky and see what went wrong. Absent that, and with a caution to get in the habit of shutting down your programs before attempting to upgrade/update, this really is going to be unactionable. And some would argue it is NOT OUR BUG. But, please check IObit utility for its log situation--we might get lucky. =-ref-= [1] https://opengrok.libreoffice.org/xref/core/extras/source/templates/presnt/Classy_Red/Object1/content.xml?r=659acfbb#56 [2] https://opengrok.libreoffice.org/xref/core/chart2/qa/data.chd?r=668c6b02
Dear Stephen Walker, 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 Stephen Walker, 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