Novadays I've noticed that a diagram's picture different in Calc screen as copy the pasted picture in writer. (not fuzzy or empty, it seems correct diagram but values were invalid on it.) My ods has 20 diagrams. Data of them are calculated by many functions on many sheets. I used to copy diagrams to writer odt document. When I noticed this thing I have made png-s by saving as html and I found 2 pngs from 20 which weere not the same as picure shown in calc for the same type diagram. Those pngs were the correct diagrams of a previous version of the current ods file. (this ods is reused annually with different data set) It means for me that diagrams (can) have saved pictures (image cache?) inside the ods and for some reason in my ods those old images were not replaced when the diagram was redrawn de to source data change. Finally I found CTRL-SHIFT-F9 which recalculates and redraw diagrams and replaces the stored images as well .... If I don't forget it!!!! I guess it would be a very useful and desirable change in LO to delete cached version of digarams as a 1st step when a diagram is redrawn on screen due to data change. It would be much better than pasting an incorrect diagram which sometimes almost invisible until somebody asks sg like this on a meeting: How the hell can be this number 2 today when you've promised it will be 4.5 at least till the end of this year!!! The only thing I remember when I have copied diagrams that I was faster than LO could refresh everything. Maybe I have saved earlier the ods than previous diagram chache refresh process finished on all diagrams (?) After CTRL-SHIFT-F9 all diagrams were correctly copied to writer. But an error message wuld be much better than a different picture in target document.
Hello, Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. Thank you
Dear Bug Submitter, 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-20180302
Dear Bug Submitter, 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-20180404