Description: I have a spreadsheet in which Sheet1 is mostly about calculating random numbers for x-y coordinates and Sheet2 analyses them and plot then on a graph. This is attached. when I press F9 in sheet2 it looks like all the numbers in the sheet are updated. They all change. I assume this is because Sheet1 changed. 1) I though F9 should not change Sheet1 when I am looking at Sheet 2. At least that is what is indicated by https://help.libreoffice.org/Calc/Shortcut_Keys_for_Spreadsheets 2) Far worse. The data is changed but incorrectly. Normally I would be hard pressed to spot this but the graph I am drawing is clearly wrong after pressing F9 but correct after pressing shift-ctrl-F9. I know it is wrong because light coloured dots should not fall next to dark dots. Dark dots should not appear at the edge of the graph. Sadly this is a complex sheet for debugging purposes. I tried a simple sheet dosing some trivial calc with random numbers but could reproduce the effect. Steps to Reproduce: 1. open attached sheet 2. switch to sheet2 (plot) 3. press shift-ctrl-F9 to see a correct plot 4. press F9 (best done 4 or 5 times) to see an incorrect plot 5. compare with pressing shift-ctrl-F9 5 times to see a correct plot each time Actual Results: light coloured dots and dark dots spread out over graph light and dark dots next to each other Expected Results: light coloured dots at edge of graph - dark dots clustered around (-1,1) (1,1) (-1,-1) (1,-1). No light dots near dark dots. Reproducible: Always User Profile Reset: No Additional Info: Sheet was designed to trial a simple algorithm for colour coding dots depending on how closely clustered they are. Operating system is Opensuse Leap 42.3
Sorry forgot attachment - will have to add later
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the document is provided.
Created attachment 143746 [details] spreadsheet displaying problem
I have manged to check all the values in the cells and I think they all update correctly. I did this by duplicating the file. Then once the problem is manifest in file1 I copy all the values from file1:sheet1 to file2:sheet1 and paste by value. file2:sheet2 updates and displays the same numbers as file1:sheet2. The problem is the chart. It is not displaying the data correctly. Once incorrect you can click on the graph and highlight an individual point. I chose to do this for a dark point near the edge of the graph since dark points should not appear there. Once highlighted the cell is also highlighted so you can check the data. The x,y coordinates for the point are not those where the point is drawn on the chart.
As an aside I find it extremely difficult to click on points. For some reason no matter where I click on graph the series in column G always becomes selected even though I click nowhere near and series G points
Another odd thing. If I set the background color of a cell everything updates as if I pressed shift-ctrl-F9. think there could be several spin off bugs here
I have spent some time cutting down the complex file to create another with this problem. I now have it down to the attached file badredraw.ods. This has only one sheet. IT has 100 rows of data from row 5 to row 104. The idea is to plot x against itself. As the chart shows this should produce a straight line not random scatter. When you first load the sheet you see a blue and red points on a straight line. Now press F9 a few times , usually 2 or 3 needed. You get a random scatter. If you remove row 104 data save, reload you get straight lines even after many presses of F9. If you add row 104 back, save, reload you get the problem back. This may be related to other bugs. Libre Office has a problem working with more than 100 lines of data. I have seen this before https://bugs.documentfoundation.org/show_bug.cgi?id=112434
Created attachment 143758 [details] simpler version of chart redraw bug
I can not confirm with Version: 6.2.0.0.alpha0+ Build ID: 53eda574a61396b6765cd1cb0ac9804c754ac4c1 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; Could you test with dev version? http://dev-builds.libreoffice.org/daily/master/ If you still observe the bug in dev version, please attach printscreen. Thank you.
Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear MD, 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 MD, 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