If you accidentally add § into a formula will cause the rest of the formula to be erased. This is specially annoying in keyboard layouts where § is next to 1 so it is easy to hit by accident. How to reproduce/example: In all you should enter a calculation formula in a cell and see that it produces the expected value and that when you click on it the edit bar shows the right formula. I will use =2*2*2 as example in the following. First example: Change the middle 2 to a § producing =2*§*2 and press enter. You get the expected Err:501 as cell value, but going back to edit you see =2* in the edit box, so everything starting from § was truncated. Expected behavior: Have =2*§*2 in the edit box so could change the § into the meant 1 Second example: Undo or type in =2*2*2 again to reset for next: Change the first 2 to a § producing =§*2*2 and press enter. You get the expected Err:501 as cell value, but going back to edit you see Err:501 in the edit box, so everything including the = was truncated. Expected behavior: Have =§*2*2 in the edit box so could change the § into the meant 1 Third example: Type in directly a new formula =§*2*2 and press enter. You get the expected Err:501 as cell value, but going back to edit you see Err:501 in the edit box, so everything including the = was truncated. Expected behavior: Have =§*2*2 in the edit box so could change the § into the meant 1 Libreoffice version: Version: 5.0.1.2 (x64) Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: en-GB (en_GB) System: Windows 8.1 Pro 64 bit.
Reproducible with LO 5.0.3.0+ built at home under Ubuntu 15.04 x86-64 with gcc 5.1. We encounter the same behaviour with any invalid character (in the meaning of LO Calc), for example ± or ¨ Set status to NEW. Best regards. JBF
Seems it begins with ascii 128
** 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.1.5 or 5.2.1 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-20160920
Still reproducible in LO 5.2.3.0+ and current master, both built at home under Ubuntu 16.04 x86-64. Best regards. JBF
** 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) 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-20170929
Still reproducible in LO 5.4.4.0.0+ and current master, both built at home under Ubuntu 16.04 x86-64. Best regards. JBF
** 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
Still reproducible with LO 6.2.0.1.0+ Best regards. JBF
https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/compiler.cxx?r=60a66bd5#2648 https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/compiler.cxx?r=60a66bd5#2653 https://opengrok.libreoffice.org/xref/core/include/formula/errorcodes.hxx?r=da9a6f42#33 may be BY DESIGN, but can be confusing to end users. i18n related, sc formula related matter. CCing Eike.
Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/7d6f30d04c51088b26815c241a7473c48822c6c3%5E%21 Resolves: tdf#93951 set remainder as bad string if not parsed as valid It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Pending review https://gerrit.libreoffice.org/67115 for 6-2
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/99b0a3702d9c04c68d33adb9fbf1fd289618cc89%5E%21 Resolves: tdf#93951 set remainder as bad string if not parsed as valid It will be available in 6.2.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Verified fixed in Version: 6.2.2.0.0+ Build ID: ffd826d0e421a7634ac742439ecd0e7563b3eb4d Threads CPU : 4; OS : Linux 4.15; UI Render : par défaut; VCL: gtk3; Ubuntu_18.04_x86-64 Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded Best regards. JBF
Also verified in Version: 6.3.0.0.alpha0+ (x64) Build ID: 99e12aed50765d0c2ac7be29c44469641f2567b5 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-02-16_23:24:24 Locale: es-ES (es_ES); UI-Language: en-US Calc: CL
Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/26623cc6c144c451323a08be7bd021ae354b1a95 tdf#93951: sc_ucalc: Add unittest It will be available in 7.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.