Created attachment 78015 [details] Files demonstrating the problem Hi, Write does not evaluate formulas in odt files while converting to pdf or printing from command line. Formulas are evaluated correctly when converting from docx and rtf files Formulas are evaluated correctly when converting from odf by Apache OO 3.4 To reproduce: Convert file tabulky2.LO40.odt to pdf by libreoffice4.0 --headless --convert-to pdf tabulky2-LO40.odt or print it by libreoffice4.0 --headless --print-to-file xx.odt tabulky2-LO40.odt Instead of the result an error message appears: "** Expression is faulty **" (in the yellow field) Try the same with the rtf and docx files - the result is correct -- Milos
Created attachment 82514 [details] PDF of original ODT with expanded rows to better show the error message. This is just a confirmation of the problem with clarification. The problem only occurs for the ODT and not the DOCX or RTF (as the ODT contains formulas and the DOCX/RTF do not - they contain literal values). I can't confirm if AOO v3.4 converts the formulas in the ODT correctly, but if it does, then this may be a regression. In the ODT the initial 4-row Writer table includes these formulas in the last (red) row: = sum<B2:B3> # which displays "70" = sum(<B4>)<C2:C3> # which displays "105" The yellow table then references these two cells using the formulas: = <Tabulka.B4> # i.e., the "70" value above = <Tabulka.C4> # i.e., the "105" value above I edited the original ODT by expanding the rows receiving the error in order to more clearly show the result. The attached PDF, generated from this edited ODT, clearly shows that the two cells in the red row result in "** Expression is faulty **", as do the two cells in the yellow row (which reference the two red cells). I have re-confirmed this by creating a new ODT containing only two simple tables: the first sums a cell containing "30" and a cell containing "40"; the second references the result of this sum formula. Resulting notation in ODT and output in the PDF are identical to the original files, thus I did not bother attaching them. Tests conducted under GNU/Linux Crunchbang 11 running TDF/LO v4.0.4.2 (Build ID: 9e9821abd0ffdbc09cd8c52eaa574fa09eb08f2).
Hi, I'd like to push this bug report. I ran into the same problem under windows and ubuntu. Sum calculations endet up in "Faulty expression"-error. If I calculate like "= <A1>+<A2><A3>" the result ist correct. I also found out, that sum works if the table ist the very first element in the odt File. Maybe, there is already a solution for this problem? -- Chris
The problem of the formulas in the red row not totalling correctly (and not being referenced correctly in the yellow row) seems to be fixed in all these versions under GNU/Linux: - v4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a - v4.2.5.2 Build ID: 61cb170a04bb1f12e77c884eab9192be736ec5f5 - v4.3.0.3 Build ID: 08ebe52789a201dd7d38ef653ef7a48925e7f9f7 - v4.4.0.0.alpha0+ Build ID: 4aa9b041de3129f19b48e66d349f48657b73f33e (2014-07-19) Milos if you can confirm this, we may be able to finally mark this bug as RESOLVED and WORKSFORME (unless an identifiable fix can be located, in which case it can be marked FIXED).
(In reply to comment #3) > The problem of the formulas in the red row not totalling correctly (and not > being referenced correctly in the yellow row) seems to be fixed in all these > versions under GNU/Linux: > > - v4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a > - v4.2.5.2 Build ID: 61cb170a04bb1f12e77c884eab9192be736ec5f5 > - v4.3.0.3 Build ID: 08ebe52789a201dd7d38ef653ef7a48925e7f9f7 > - v4.4.0.0.alpha0+ Build ID: 4aa9b041de3129f19b48e66d349f48657b73f33e > (2014-07-19) > > Milos if you can confirm this, we may be able to finally mark this bug as > RESOLVED and WORKSFORME (unless an identifiable fix can be located, in which > case it can be marked FIXED). Hi, it still does not work for me. I've tested Verzia: 4.2.6.1 5fdddf655fba363e34f755715238d0943a44857e Verzia: 4.3.0.3 08ebe52789a201dd7d38ef653ef7a48925e7f9f7 Did you run the conversion from command line? This way? /opt/libreoffice4.2/program/soffice --headless --convert-to pdf t.odt -- m
(In reply to comment #4) > Did you run the conversion from command line? Oh, sorry. Please disregard comment 3. Still produces the indicated error here also.
Hi, I've tested with 4.2.5.2 (WIN) 4.2.4.2(Ubuntu 14.04) PHP $msg = @shell_exec($cmd_prefix.escapeshellarg($libreoffice_path).' --headless --nodefault --nofirststartwizard --nolockcheck --nologo --norestore --invisible --convert-to pdf '.escapeshellarg($path).' --outdir '.escapeshellarg($temp_file_dir)); Command Line soffice.exe --headless --nodefault --nofirststartwizard --nolockcheck --nologo --norestore --invisible --convert-to pdf test.pdf --outdir test; /usr/bin/libreoffice --headless --nodefault --nofirststartwizard --nolockcheck --nologo --norestore --invisible --convert-to pdf /home/xxx/test.pdf --outdir /home/xxx/temp -- Chris
** 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.0.5 or later) 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: 2015-09-03
Still repro. Ubuntu 15.10 64-bit Version: 5.1.0.0.alpha1+ Build ID: 7272e8df62a12d6172b297d7a82a0265cd1bc44a TinderBox: Linux-rpm_deb-x86_64@70-TDF-dbg, Branch:master, Time: 2015-11-15_00:23:07 Locale: en-US (en_US.UTF-8)
same error here, trying to convert 10+ odt writer documents incl. a table and some formulars. Everytime I convert the files to PDF using the commandline, the formulars are not evaluated before converting and in the output file you see "expression is faulty" instead of the value.
I can confirm this bug using also .fods format and converting to pdf
** 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
*** Bug 92181 has been marked as a duplicate of this bug. ***
*** Bug 98183 has been marked as a duplicate of this bug. ***
setting various fields conform duplicate bug 98183
maybe check a build with the fix of bug 121962 looks rather similar :)
I just checked and the document no longer displays "Expression invalid", but it has 0 sum instead of the correct sum. So there is still some bug here.
This is fixed now with the commits pushed for bug 121962. *** This bug has been marked as a duplicate of bug 121962 ***