Created attachment 127384 [details] Corrupt document: text is hidden from view and falls off page. After editing, saving and reopening a document, text disappears from the document. It falls off the page and does not show on the next page like it did while editing before. Instead, though it is selectable with Command+A, it disappears from the pages in my document. The same thing happens to us repeatedly in different documents, containing a similar layout with tables. A document is attached as an example.
Not reproducible for me under Ubuntu 16.04 x86-64 with Version: 5.2.3.0.0+ Build ID: 8c20df32c8278bc4a076cef285db7788627f4c07 Threads CPU : 4; Version de l'OS :Linux 4.4; UI Render : par défaut; Ubuntu_16.04_x86-64 Locale : fr-FR (fr_FR.UTF-8); Calc: single Please, could you add some information: - your OS - does the text disappears definitely (data loss) or does it reappear when you close and reopen the document ? Set status to NEEDINFO, please set it back to UNCONFIRMED once you have provided these informations. Best regards. JBF
I couldn't reproduce it with v5.2.1.2 / Windows 7. Added a space, saved and reopened it, and it looks the same.
Hi guys, thanks! Are you saying that when you open the attached document, all text is visible and you see it normally paginated to about 10 pages? With me, it doesn't. I had the same problem on both Linux and MacOS, in both cases the corrupted document looks the same and text is not visible. Right now I am using: OS X El Capitan Version 10.11.5 (15F34) MacBook Pro (Retina, 15-inch, Mid2015) The text is still there but it is not visible (falls off the page). If I close and reopen the document, it doesn't get better.
Hm, no, I only see two pages, and a 3rd, empty one (except header). And indeed, word count says the document contains 15819 characters, which contradicts what can be seen. What I'm a bit confused by, from the description I thought it was supposed to look fine at first, and I had to edit/save/reopen it to make the text disappear.
Hi Wim, I confirm that I see some content being hidden, sometimes .. didn't study it too long. Seems an old document with quite a long history? Of course you want to behave that perfect too, but.. ;\ Ever attempted to create a new clean one?
looks as if it behaves the same in version 3.3.0.4 (Initially looked in master Version: 5.3.0.0.alpha0+ Build ID: 1ef48f3bebe80a386490e2a0f8fd0ae40de07ada CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-09-18_23:46:24 Locale: nl-NL (nl_NL.UTF-8); Calc: group )
Wondering if this might be related to an issue of corrupted LibreOffice writer files that we are experiencing on MacOS X 10.11.6 with LO 5.1.5.2. After an OS update from MacOS X 10.9.5 to 10.11.6 we are experiencing corrupted LibreOffice writer documents. The issue appears to pertain to writer documents counting tables. When opened in LO 5.1.5.2 on Macos X 10.11.6 the document renders as gibberish. The documents were normal on MacOS X 10.9.5 with LO 5.1.5.2 -TL
This shouldn't have been confirmed so fast. Reporter says "After editing, saving and reopening a document.." so Needinfo is still proper to know: - do you have the original document, with all the text, can you attach that one? - what is the original document before saving, odt or sth. else? - how was the document created, from scratch or by coping from somewhere or by saving from some other format? The document is from 2010, with 712 registered revisions. Reporter says "The same thing happens to us repeatedly in different documents" so I ask: - how many people? - what are you using now, LO 5.2.1.2? - Windows, I guess, is it 32-bit or 64-bit platform?
(In reply to Timur from comment #8) > This shouldn't have been confirmed so fast. Basically you are right, and your questions are just. It's just (another just) that I saw the effect he describes. And even then, it might turn out that for whatever reason the file has gone mad - see my questions... @Wim: lots of stuff for you to asnwer :)
People thanks for your reactions and looking into this! Cor, I tried creating a new document and experienced the same problems. I will reproduce the same document later and see if it still bugs. My suspicion is that tables within tables cause the problem, where one table cell spans 10 or 20 pages and that cell includes at least two tables which each span more than one page. T.L. I am not sure if we have the same problem? At least with us it didn’t have to do with MacOS X versions and tables do not render gibberish. If you experience gibberish, probably those are not connected. Timur, I can attach the original document we use and sometimes break. Later on, I can test more. The original document is .odt We use our own blank document again and again and as far as I know, it was created in OpenOffice by a colleague of mine. The same error occurred with four people, three of which using Mac and one on Windows. It occurs very often with Eline on an Airbook, and with Merijn on Windows, so often that they didn’t want to use LibreOffice any more. The system I am using was already stated. The document attached broke when saving from a Windows machine. All errors occurred when editing a copy of our master blank document which I will attach. Thanks for looking into this, Wim
Created attachment 127527 [details] Our master blank document which easily breaks when adding table rows to the inner table within the table
(In reply to Wim Feijen from comment #10) > Cor, I tried creating a new document and experienced the same problems. I > will reproduce the same document later and see if it still bugs. My > suspicion is that tables within tables cause the problem, where one table > cell spans 10 or 20 pages and that cell includes at least two tables which > each span more than one page. Thanks for further description and attachments Wim. I can imagine that you, as intermediate solution, could work with a different lay out until this problem is been solved? Since that is not easy to predict. Will try to look further in details one of these days.
It turn out that my issue with gibberish tables was likely due to bit rot related to LibreOffice.
EDIT: It turn out that my issue with gibberish tables was likely due to bit rot *UNrelated* to LibreOffice.
(In reply to T.L. from comment #14) > EDIT: It turn out that my issue with gibberish tables was likely due to bit > rot *UNrelated* to LibreOffice. thanks for reporting back
ping to myself..
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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping-20170502
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170531