Created attachment 112348 [details]
Error bar in spreasheet
My file works on LibreOffice Calc 3.6 or less, but didn't work on LibreOffice Calc 4.xx.
The error bar didn't appear.
My english isn't good to explain better.
I confirm issue under Win8.1 x64 using LibO 4.0.4, 4.2.5, 4.3.5 and recent 4.5.0 daily build.
works fine in 3.6.7 and 4.2.4 so it's a regression in the middle of the 4.2.x development (probably a good candidate for the MAB list)
the list of bugfixes of 4.2.5 is here:
probably one of those fix caused this regression as a side effect.
adding Calc developer to CC list.
until we try to fix the bug you can at least upgrade to LibO 18.104.22.168
Created attachment 112378 [details]
screenshot of the error bar as shown correctly in 3.6.7
that pink error bar in the 40%-50% column is not shown in LibO 4.2.5 and following relases. looks fine in 4.2.4 and older versions
My testing indicates that this spreadsheet is slow in scrolling, seems like LO needs some optimizations. I was able to get a clean bibisect and it clearly stops displaying the error bar.
1de992ed60dad1fd65ff0383a8610b0468d9d772 is the first bad commit
Author: Bjoern Michaelsen <email@example.com>
Date: Tue May 20 12:30:20 2014 +0000
Author: Chris Sherlock <firstname.lastname@example.org>
AuthorDate: Thu May 1 23:42:49 2014 +1000
Commit: Chris Sherlock <email@example.com>
CommitDate: Fri May 2 00:18:10 2014 +1000
coverity#1209779 & coverity#1209780 Resource leak
Have the testBasics() function clean up after itself - delete p2 and
p4 at the end of the function.
:100644 100644 5a882bfa118f7e6bdce2a5352a84980e3317b63c 1315213d62e9db779916ce48371a89fa31867b0b M ccache.log
:100644 100644 f8bdc1225a7c2dc7a94ed9a6367b7298f4ee0a37 9c728d68efbe36be265f19b9a78f9d6280176e98 M commitmsg
:100644 100644 3cd5d50875f1e67f2f758bdfd10744eb6d47d13b 58e54f9015582d37978cd75e1ebdaed7ba12ea8f M make.log
:040000 040000 65e23a71dc754b4a799d96c3e25d191237cfddb1 8236eb41fc03f7f798cda8f31383bf2087db52e9 M opt
# good: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb
git bisect good e02439a3d6297a1f5334fa558ddec5ef4212c574
# good: [4850941efe43ae800be5c76e1102ab80ac2c085d] source-hash-980a6e552502f02f12c15bfb1c9f8e6269499f4b
git bisect good 4850941efe43ae800be5c76e1102ab80ac2c085d
# skip: [a900e72b6357882284c5955bdf939bf14269f5fb] source-hash-dd1050b182260a26a1d0ba6d0ef3a6fecc3f4e07
git bisect skip a900e72b6357882284c5955bdf939bf14269f5fb
# skip: [3dda83fc3a43afc6af7f5c0ffd029e610ec1b9a3] source-hash-c59b3d6c5c8096486730007d9b9b053793b90b1e
git bisect skip 3dda83fc3a43afc6af7f5c0ffd029e610ec1b9a3
# good: [4f705a8cfb1998b09f2062510b207d35a33647d8] source-hash-1eeb20f3958666ec6ba6e0fcf52e92e5eb447a14
git bisect good 4f705a8cfb1998b09f2062510b207d35a33647d8
# good: [465e2be02951f9645beb3024506a5212907caf5f] source-hash-674801eb4af21c9ae83c122499f15fa4f4785b0f
git bisect good 465e2be02951f9645beb3024506a5212907caf5f
# bad: [1de992ed60dad1fd65ff0383a8610b0468d9d772] source-hash-8bf0b9536cb33dfcce8a811b70c2ead285300f3f
git bisect bad 1de992ed60dad1fd65ff0383a8610b0468d9d772
# good: [ce3d21bc00b0756f1e7dbb4974db30e6d51b913b] source-hash-8485a276022e05bd34afb2321e72ecfad4589f7e
git bisect good ce3d21bc00b0756f1e7dbb4974db30e6d51b913b
# good: [89894d82385af13d5393f07abeb76a2c309b1828] source-hash-062e69f40b749aa8a6058c3e6ca328af86aeb45b
git bisect good 89894d82385af13d5393f07abeb76a2c309b1828
# good: [038ec16923792263990256ed738920cd761e4f70] source-hash-11b81c1026c17548bfdbb861ac696f9c6acc628e
git bisect good 038ec16923792263990256ed738920cd761e4f70
# good: [741197a13a361480f59eeb3bd1401f984f49f1c0] source-hash-9a61470eb1fa161cba70f2e9c4ea8817dc7f617e
git bisect good 741197a13a361480f59eeb3bd1401f984f49f1c0
The behaviour changed as of the below commit.
Adding Cc: to firstname.lastname@example.org; Could you possibly take a look at this? Thanks
Author: Markus Mohrhard <email@example.com>
Date: Wed Apr 30 01:20:36 2014 +0200
set graphic properties for error bars during import, fdo#78041
Migrating Whiteboard tags to Keywords: (bibisected)
Adding Cc: to Markus Mohrhard
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice
(5.4.1 or 5.3.6 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Actually this looks like it is correct how it is implemented by now. The file is storing a draw:stroke="none" which tells LibreOffice to draw an error bar without a line.
I don't consider this a bug or a regression. It looks like we fixed a previous bug and unfortunately one needs to change the line format from none to continuous once. I checked that the format is correctly exported in master.