Bug 87367 - FILESAVE: corruption afters saving. text replaced by #####
Summary: FILESAVE: corruption afters saving. text replaced by #####
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other Linux (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-16 16:37 UTC by Alain Versa
Modified: 2015-09-04 03:01 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
that is the file I have problems with (1.00 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2014-12-16 16:37 UTC, Alain Versa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alain Versa 2014-12-16 16:37:02 UTC
Created attachment 110910 [details]
that is the file I have problems with

I was working on a file, I saved it and then, when I tried to open it, it is broken, all the text is gone, the only thing I can read is ####. It was a big work I was doing, how can I recover it?
Comment 1 Julien Nabet 2014-12-16 18:15:44 UTC
You're file seems corrupted, it's only 1kb size.
A docx is in fact a zip file with a specific structure.
Comment 2 Christopher Chavez 2014-12-17 00:53:57 UTC
The file is entirely zeroed (0x00, 1024 of them, which LibreOffice shows as 1024 '#'), and there is no information that can be recovered. I have not found any reports of people's documents getting turned into 1kb zeroed files, but I do find reports of (sometimes very angry) users having their documents turned into empty (0 byte) files.
Short of using something like photorec, this may help recover the file: http://ask.libreoffice.org/en/question/6652/how-to-recover-former-version-of-document/

If possible, let us know which version of LibreOffice and Linux distribution was used, and more about what was in the document/why it was large (e.g. did you use images, charts, etc.).
Comment 3 tommy27 2014-12-17 06:33:17 UTC
added a better summary and set status to NEEDINFO
Comment 4 Christopher Chavez 2014-12-18 00:31:08 UTC
The file in question was .docx, so I assume this is for Writer, not Spreadsheet--a '#' for each byte is the result displayed in Writer; doing

dd bs=1K count=4 < /dev/zero > test.docx
libreoffice test.docx

will cause the following appears in the command line:

:1: parser error : Document is empty

^

and Writer displays an unformatted document with 4096 of '#'.
Comment 5 QA Administrators 2015-07-18 17:36:12 UTC
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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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

This NEEDINFO message was generated on: 2015-07-18
Comment 6 QA Administrators 2015-09-04 03:01:30 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO
Message generated on: 2015-09-03