Bug 129540 - Wrong y-error bars for range cells in calc
Summary: Wrong y-error bars for range cells in calc
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.2.8.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-21 16:11 UTC by heiko
Modified: 2020-05-21 13:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Calc file with data sets (17.22 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-12-21 16:12 UTC, heiko
Details
Picture from data set (47.14 KB, image/png)
2019-12-21 16:13 UTC, heiko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description heiko 2019-12-21 16:11:36 UTC
Description:
When selecting the y-error bars as range, only the first column is displayed for all.

Steps to Reproduce:
Opening the test file shows the error (see also the picture).

1. Fill cells with values
2. Create xy diagram
3. Apply y error bars

Actual Results:
Wrong y error bars

Expected Results:
Specific y error bars for all data points


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 heiko 2019-12-21 16:12:23 UTC
Created attachment 156720 [details]
Calc file with data sets
Comment 2 heiko 2019-12-21 16:13:02 UTC
Created attachment 156721 [details]
Picture from data set
Comment 3 Buovjaga 2020-04-30 18:10:33 UTC
(In reply to heiko from comment #1)
> Created attachment 156720 [details]
> Calc file with data sets

Can you give steps on what we need to do, if we want to create the chart from scratch based on the data in this file?
Comment 4 heiko 2020-05-01 17:39:11 UTC
I think the main problem is that I inserted the y-error-bar via Insert>Y-error-bar.
When assigning the y-error-bars individually it works. 

I just tried it because I had many graphs with different error-bars. On the other hand, the guiding of preconditions also hangs here (within the error category).
Comment 5 Buovjaga 2020-05-01 18:02:19 UTC
(In reply to heiko from comment #4)
> I think the main problem is that I inserted the y-error-bar via
> Insert>Y-error-bar.
> When assigning the y-error-bars individually it works. 
> 
> I just tried it because I had many graphs with different error-bars. On the
> other hand, the guiding of preconditions also hangs here (within the error
> category).

Do you mean we could close this report? If not, please give steps like I asked.
Comment 6 heiko 2020-05-01 18:27:38 UTC
Unfortunately I'm doing home-office (the version is the same, but different host) and I can't get to the point, it breaks off with the error:

$ oocalc
kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen."
kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen."
get value on unknown control 107


Fatal exception: Signal 11
Stack:
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3aa10)[0x7f31484e2a10]
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3abd8)[0x7f31484e2bd8]
/usr/lib64/libc.so.6(+0x3caf0)[0x7f31481f4af0]
[0x9c7ccc0]
Comment 7 Buovjaga 2020-05-01 18:47:20 UTC
(In reply to heiko from comment #6)
> Unfortunately I'm doing home-office (the version is the same, but different
> host) and I can't get to the point, it breaks off with the error:
> 
> $ oocalc
> kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen."
> kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen."
> get value on unknown control 107
> 
> 
> Fatal exception: Signal 11
> Stack:
> /usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3aa10)[0x7f31484e2a10]
> /usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3abd8)[0x7f31484e2bd8]
> /usr/lib64/libc.so.6(+0x3caf0)[0x7f31481f4af0]
> [0x9c7ccc0]

Maybe it is related to KDE (kf5). Try launching from the command line with

SAL_USE_VCLPLUGIN=gtk3 libreoffice

or

SAL_USE_VCLPLUGIN=gen libreoffice
Comment 8 heiko 2020-05-02 17:58:15 UTC
It still won't work with this command. I cannot select the fields for the y error bar. When closing the dialog, however, it also crashes.

$ SAL_USE_VCLPLUGIN=gtk3 libreoffice

Fatal exception: Signal 11
Stack:
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3aa10)[0x7f1dce95aa10]
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3abd8)[0x7f1dce95abd8]
/usr/lib64/libc.so.6(+0x3caf0)[0x7f1dce66caf0]
[0x358aec0]
Comment 9 Buovjaga 2020-05-02 20:03:46 UTC
Does it also crash, if you launch LibreOffice in Safe Mode: Help - Restart in safe mode and then Continue in safe mode?
Comment 10 heiko 2020-05-03 16:30:14 UTC
It's also crashing.

oocalc --safe-mode
kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen."
get value on unknown control 107


Fatal exception: Signal 11
Stack:
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3aa10)[0x7f9e4d32aa10]
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3abd8)[0x7f9e4d32abd8]
/usr/lib64/libc.so.6(+0x3caf0)[0x7f9e4d03caf0]
[0x513b140]
Comment 11 Stéphane Guillou (stragu) 2020-05-21 12:42:46 UTC
I guess what the reporter tried was to select the whole chart, and add a y error bar. By default, Calc will apply the same error bars to all data series (which is stated in the title of the dialogue: "Y error bars for all data series").
One can see this by:

* Going into the chart
* Insert > Y error bars...
* Select "Cell range", tick "same value for both", and use the range $F$2:$G$11

Calc will only use the first column's values to draw the error bars for both series.

In order to have the right error bars, one needs to first select one data series, and then add the y error bars using the corresponding column. Then, repeat with the second one.

(Pretty much what is said in comment 4)

So I guess this can be closed as not a bug?

Tested with:

Version: 6.4.3.2 (x64)
Build ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: en-AU (en_AU); UI-Language: en-US
Calc: threaded
Comment 12 Buovjaga 2020-05-21 13:02:44 UTC
Yeah, let's close.

Heiko: for the crash, please open a new report with steps. In the new report you can just refer to attachment 156720 [details] and it will get linked.