An error occurs when using formulas in a table. Depends on the initial data in the yellow cells. See attachments.
Steps to Reproduce:
User Profile Reset: Yes
The problem is manifested in versions 6.2 and higher.
Created attachment 158404 [details]
File with errors.
In cell D17, the value should be 19:00.
Created attachment 158405 [details]
Error locations are shown.
Thank you for reporting the bug. I can confirm the bug present in
Version: 188.8.131.52.alpha1+ (x86)
Build ID: ec7374ff84c71edfbb30d6e4dc5b486b6df7107f
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win;
TinderBox: Win-x86@42, Branch:master, Time: 2019-11-10_21:37:30
Locale: en-US (en_US); UI-Language: en-US
i think this issue is related to:
Bug 127334 (BrokenDateTimeSpec) - Regression: Incompatible changes in date/time arithmetic introduced between Version: 184.108.40.206 (x64) and version 220.127.116.11
... and also to
Bug 127170 - Clarify clock time (HH:MM, MM:SS, ...) and duration time ([HH]:MM, [MM]:SS, ...) formatting in help; (ignore the MM month vs minute discussion)
Bug 132083 - FORMATTING - Wrong date substraction in cell's operation
I think this bug cannot be solved without having clarified the issues discussed in bug 127170. That's why I moved the bug from "See also" to "Depends on".
The bug is also not in
Version: 18.104.22.168 (x64)
CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard;
Gebietsschema: de-DE (de_DE); Calc: group
This seems to support Oliver Brinzings assumption that this bug is related to bug 127334. It is interesting in the context of the wall clock vs. duration format discussion. The error appears in column D. In this column you correctly use wall clock format HH:MM for a wall clock time.
Note that the value in line 8 column D should be exactly the same a the one in line 7 column E as it is just a copy of this value and the same format is used. Nevertheless the displayed values differ (16:49 vs. 16:50).
I fear that this problem is related to a correct implementation of the specification of date and time arithmetic which makes it susceptible to tiny round off errors.
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 with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
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) from https://downloadarchive.documentfoundation.org/libreoffice/old/
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: https://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!