Description: When trying to show y error bar that spans to below zero on the y axis in the log scale, the graph disappears except a diagonal line. Steps to Reproduce: 1. Input below values in the range A1:E3 Y1 Y2 X Average Stdev 1 2 1 =average(B2:C2) =stdev(B2:C2) 1 6 -1 =average(B3:C3) =stdev(B3:C3) 2. Select the range of C1:D3. 3. Click the chart icon on the toolbar. 4. Click XY(Scatter), click the second to the left graph (with lines inbetween dots) in the Points and Lines area, and click the finish button. 5. Move the chart to the F column so that the values on the E column can be shown. 6. Move the mouse pointer above the line inbetween the two dots on the graph until the tooltip shows "Data Series(Average)". 7. Right click on it and select "Insert Y error bars". 8. Select Cell Range. In the blank of parameters Positive (+), input $Sheet1.$E$2:$E$3. (Alternatively you can select the same range by clicking "Select data range" icon) 9. Check "Same value for both". Click OK. 9. Double click the y axis to modify the scale. Check the Logarithmic scale. Click OK. Actual Results: The graph disappears except a diagnal line across the area where the graph is supposed to be shown. The graph is no more editable to remove the y error bar or to remove the logarithmic scale to solve the problem. Expected Results: The y error bar can span to the bottom end on the graph (because the y axis is in logarithic scale and the error bar spans to negative value that cannot be shown in the graph) and show a pop-up error message that the error bar spans to negative value that cannot be displayed on the logscale axis. Reproducible: Always User Profile Reset: Yes Additional Info: The graph should be at least remain editable to remove the problem. When double clicking the graph, it enters the editing mode, though, but it is not possible to change the y-error-bar range or to remove the logarithmic scale any more.
Created attachment 168509 [details] An example spreadsheet to reproduce the reported problem
*** This bug has been marked as a duplicate of bug 56580 ***