Created attachment 113412 [details] calculated value at cursor should be zero I'm having a big table with payments and a formula adding VAT percentage values. Prior to 4.4.0.3 this worked flawlessly, but now something strange happens. As you can see in the screenshot at the cursor position it yields a value of 2000 although it should simply be zero, because the cell to left ist empty. In the second screenshot you see the formula. When I enter a 0 into the empty cell, the calculation is correct. Deleting the 0 gives again the wrong value.
Created attachment 113413 [details] the formula with reference to the empty cell
Hi @Gunther, thanks for reporting. Have you tried with a hard recalc?. [Shift+Ctrl+F9] If it doesn't work, please can you attach a minimal sample file where to verify the issue. Please reset the bug to unconfirmed after answer.
Yes, it survives [Shift+Ctrl+F9]. I've added a a file that exhibits the behaviour.
Created attachment 113450 [details] Screenshot of testfile
Created attachment 113451 [details] testfile
I can confirm with LO 4.4.0.3 and Version: 4.5.0.0.alpha0+ Build ID: 7f126fc8570da5c7275a4d4efe019b9ea3b5b073 TinderBox: Win-x86@42, Branch:master, Time: 2015-02-14_23:15:54 also on linux After hard recalc (ctrl+shift+F9)is calculation correct.
I confirm the bug with LO 4.4.2.2 (x86-64 Win7) and also confirm that Gunther's testfile returns to normal after _two_ times pressing [Shift+Ctrl+F9]. I found the bug also on my own spreadsheet and it survives hard recalc. However there's a clue in my file about the bug: when you empty any green cell above or below the cells displaying incorrect calculations (red) and do a hard recalc after that, the calculation is correct in that column. However emptying any cell doesn't fix it, as marked with yellow color. Testfile2 attached, colours added for emphasis. Hope this helps.
Created attachment 114613 [details] Testfile2 for nonzer-cell bug
Doing only ONE hard recalc both files works fine for me with Version: 4.4.2.2 Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6. And saving and reopening after hard recalc keep the right values. There was several bug report for 4.4.0, fixed now. IMO this must be resolved as 'worksforme'.
** 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.0.5 or 5.1.2 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.3 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Works for me after hard recalc. Version: 5.3.3.2 (x64) Build ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448 CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Layout Engine: new; Locale: es-ES (es_ES); Calc: group
After loading loo-empty-cell-bug.ods contains the worng values. Neither F9 nor Ctrl-F9 work for me. :( Tried it on Version: 5.2.6.2 Build-ID: a3100ed2409ebf1c212f5048fbe377c281438fdc CPU-Threads: 4; BS-Version: Windows 6.2; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group and also on Version: 5.3.3.2 Build-ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448 CPU-Threads: 4; BS-Version: Windows 6.2; UI-Render: Standard; Layout-Engine: neu; Gebietsschema: de-DE (de_DE); Calc: group ---- But this works: As soon as I enter a Value in ONE of the cells in column B ALL cells in column E are updated correctly.
Ctrl-Shift F9 works in both LO versions! :)
Testfile survives F9, but after hard recalc (shift+ctrl+F9) worksforme. Testfile2 works after F9. Version: 5.3.3.2 (x64), Win7 x64