This bug could be related to #42518. It is reproduceable since several versions of libre office, don't know if it ever worked. Example: 1) Create a text document with language German 2) Insert a table with three lines 3) Enter the numbers 1,2 in Line one, 1,3 in line two 4) Enter formula =<A1:A2> in line three; Result: 2,5 5) Select all cells, go to "Format number..." (Zahlenformat...) 6) Set "English Great Britain" as language. Result: 0 0 2.5 After pressing <F9>, line three changes to 0, too. On linux version I have also seen, that another number is displayed.
Can you attach a document with this so we can check it out? I just tried with the formula you gave and I get a faulty expression error. Marking as NEEDINFO. Once you attach the document please move back to UNCONFIRMED and I'll take a look at it right away. Thanks for helping us out
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Created attachment 79985 [details] Explain the bug Sorry, I've forgotten to post the example.
The bug is also reproducable with the current stable version 4.0.3.3
Confirm same behavior on LO 4.0.4.1 (Win7 32bit) from language Indonesian to English (UK) Setting back the language doesn't change results.
Reproducible with LO 4.4.1.2, Win 8.1
** 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
This Bug is still valid with version 5.0.4.2 (opensuse leap) sowie mit Version 5.1.2.2
This bug dows no longer exist in 6.0.4.1
The problem is coming from the interpretation of the decimal separator. Your table contains a comma as decimal separator. When you switch to a language which use a point as decimal separator, the contents of your cells are no more recognized as a value and is converted to a text, which sum is 0. The pb is not fixed for me with Version: 6.0.4.1 (x64) Build ID: a63363f6506b8bdc5222481ce79ef33b2d13c741 Threads CPU : 4; OS : Windows 6.1; UI Render : par défaut; Locale : fr-FR (fr_FR); Calc: CL Set it back to NEW as no fix was identified @Johannes Weberhofer: "RESOLVED FIXED" is used only if we know which commit fixed the bug. In your case, you should have selected "RESOLVED WORKSFORME" The result of the sum in A3 is 0 when switching to a language of the number format using point as decimal separator. More precise procedure to reproduce the bug: 1. Tools > Options > Language Settings > Languages: Locale setting: choose a language using comma as decimal separator like French (France) or German (Germany) 2. Open attachment 79985 [details] => Result in 3rd cell is 2,5 (two and half) 3. Select all cells (click in table and hit twice Ctrl+A) 4. Right click in a cell > Number Format 5. Change language to a language using point as decimal separator, such as English (USA). OK Actual result: Display of values in two first cells are the same and sum in 3rd cell is 0 Expected result: Display of values should change decimal separator to a point (1.2 and 1.3), and sum should be 2.5
@Laurent BP thanks for re-checking. You are right, the bug still exists. I have tested it within calc were it works nicely. Have updated the version information as 3.5.3 is no longer maintained.
(In reply to Johannes Weberhofer from comment #11) > Have updated the version information as 3.5.3 is no longer maintained. Version corresponds to the *earliest* version number where the bug appeared. You should not change it. Revert to 3.5.3
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This bug is still valid with version 6.2.2.2; However, upon testing I have noticed that setting a useful number format, accepting and setting the language in a second step leads in a valid result.
Dear Johannes Weberhofer, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This specific behavior can no longer be reproduced.