Created attachment 89957 [details] Document which loses data upon click in table / PDF generation without notice. LibreOffice Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a Problem description: The embedded spreadsheet table in the attached document is corrupted upon click or PDF generation. Steps to reproduce: 1. Load document 2. Hover over cell D2 and it will show a proper formula "= <B2>*<C2>" 3. Generate PDF or click anywhere in the table 4. See the sum in D2 evaporate to 0. Total sum also reduced. 5. Close the file -> No change reported Current behavior: Document which I had created for quotes to my clients loses crucial data. Expected behavior: Loss free treatment of the data. ============================== PS: I had to open https://www.libreoffice.org/get-help/bug/ in Firefox, because the page wouldn't display right in Chrome... :/ Operating System: Mac OS X Version: 4.1.3.2 release
Can't reproduce, export to PDF is correct and shows the same as in Writer using Version: 4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a - Sophie
Created attachment 90002 [details] Short screencast showing how the cell is corrupted by clicking in the table. https://dl.dropboxusercontent.com/u/76285475/Cell%20corrupted.mov
Comment on attachment 90002 [details] Short screencast showing how the cell is corrupted by clicking in the table. What OSX are you on? I'm on 10.7.5 11G63B
Thank you for your bug report, I can reproduce this bug running Version: 4.2.0.0.beta1, Also in 3.6.7.2(Build ID: e183d5b) and 4.0.6.2 Build ID: f4ca7b35f580827ad2c69ea6d29f7c9b48ebbac7 OS: Mac osx 10.9.
** 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 (4.4.1 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-04-18
Reproduced on Version: 4.4.2.2 Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6 Locale: de_ Took me almost an hour to confirm that the bug persists and post here. Please streamline the process, guys...who else would take their precious time to check!?
** 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
Reproduced on OSX 10.11.6 LibreOffice Version: 5.2.1.2 Build ID: 31dd62db80d4e60af04904455ec9c9219178d620 as well as LibreOffice Version: 5.1.4.2 Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a
Changing version back to the earliest affected version.
I had a look at the test case, and cell C2 is text, not a number. C3 and C4 are numbers and hence their formulas are not broken. As such this is not a bug per se. It could be that LO somehow have mangled the data at one point, but as of now this is a format error in the input. Version: 6.0.0.0.alpha1+ Build ID: 7e03c4eed72452fdfb87341214a21956c08ba969 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2017-10-25_23:45:02 Locale: en-US (en_US.UTF-8); Calc: group