Created attachment 121905 [details] Example spreadsheet NB: Originally reported to Ubuntu bug tracker but was asked to post it upstream. https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1412448 When editing an XLS in Libreoffice Calc, the wrap text automatically setting in the cell formatting is not persisted across saves. Attached is a test spreadsheet with a long string of text in cell A1. Steps to reproduce: 1) Right click cell and go to Format Cells 2) Select Alignment tab 3) Unselect Wrap Text Automatically 4) Press OK 5) Save spreadsheet selecting to keep the XLS format if asked 6) Close spreadsheet 7) Reopen spreadsheet Expected Result: When the spreadsheet is reopened cell A1 has remembered that the text is NOT to be wrapped. Actual Result: Cell A1 is once again wrapped
Thanks for filing, mez.pahlan. I confirm the problem. But it's not wrapping per see that is forgotten, I think. It looks related to the issues bug 34717, and bug 32950 Especially the latter looks suspicious. Could it be the same? Ciao - Cor
Hi Cor No problem. Bug 32950 certainly looks very related. I'm afraid I don't know enough about that bug or the code to say for sure. But on first glance it does.
** 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
Still present Ubuntu 17.04 Version: 5.3.3.2 Build ID: 1:5.3.3~rc2-0ubuntu0.17.04.1~lo0 CPU Threads: 4; OS Version: Linux 4.10; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: en-GB (en_GB.UTF-8); Calc: group
** 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 a problem in 6.3.6.
Dear mez.pahlan, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Reproduced in OOo 3.3 -> inherited. And in recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6d71c21890c908225945f0fc3566255ed150f660 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
*** Bug 124117 has been marked as a duplicate of this bug. ***
*** Bug 159615 has been marked as a duplicate of this bug. ***
For the record, this problem doesn't seem to happen with newly created XLS and XLSX files. I created an Excel XLSX file (using MS Excel). In cell A1 I entered a long line of text and wrapped it. Then I saved the file and reopened in LO Calc. The wrapping was there, as expected. So I opened the Format Cells dialog and unchecked "Wrap text automatically". The text unwrapped as expected. Then I saved the file and reopened it in LO Calc and the cell was not wrapped (as expected). Then I did the same to enable wrapping again, saved and closed the file. The wrapping was remembered. Doing the exact same steps with XLS file also worked fine. However, the issue persists with attachment 121905 [details] provided by the OP. Wrapping settings are not remembered. How can this bug be specific to this file?
(In reply to Rafael Lima from comment #11) > However, the issue persists with attachment 121905 [details] provided by the > OP. Wrapping settings are not remembered. How can this bug be specific to > this file? FWIW, with a recent LO 24.8 alpha, after I open and save attachment 121905 [details], when I want to close the file there is a question whether I want to save the changes. There is something (at least) strange with this file, as there should not be any additional question after I just saved and want to close it. With the same attachment 121905 [details], if I remove Wrap Text and save, the cell is automatically set (back) as Wrap Text as soon as I save. So, this reflects the STR from comment 0. Now I edit the content of cell A1, to remove the line breaks in the text. At this point I can save the file as expected. CONCLUSION based on attachment 121905 [details]: The cell attribute "Wrap Text" seems to be automatically set when there are manual line breaks within the text of the cell, and the attribute cannot be set OFF, unless removing the manual line breaks. > BUG! Having said that, the Wrap Text problem is not just with this file. Another example for the Wrap Text issue: from dupe tdf#159615 comment 8, attachment 192461 [details] can also repro the problem (but there is no question to re-save). Open with LO, set wrap text to cell C2 (which contains a formula resulting in long text), save as xlsx and reload > the cell is not wrapped. But, on the same attachment 192461 [details], taking an inactive cell and adding simple (long) text (not a formula) with wrap, it is correctly saved and re-opened for that cell (but not for cell C2). CONCLUSION based on attachment 192461 [details]: Problem on cells with formulas, but not with simple text. > BUG! Whether tdf#159615 and other current dupes should be de-duped, IDK.