Created attachment 98420 [details] The File that seems corrupted but you can open it Problem description: Yesterday I saved the file and today I opened it an it was absolutly different from yesterday... It was full of ##### and &&& and another kind of symbols. All what I writed isn't there. hope you can help me... Thank you, Edward Operating System: Mac OS X Version: 4.2.1.1 release
file looks corrupted in Win7x64 as well using 4.2.3.3 however without the original uncorrupted file and exact steps to reproduce the corruption it will very hard to fix.
Hey! Oh… don’t worry…. Thanks for the attention, Edward On 07 May 2014, at 06:38, bugzilla-daemon@freedesktop.org wrote: > tommy27 changed bug 78260 > What Removed Added > Status UNCONFIRMED NEW > CC barta@quipo.it > Ever confirmed 1 > > Comment # 1 on bug 78260 from tommy27 > file looks corrupted in Win7x64 as well using 4.2.3.3 > > however without the original uncorrupted file and exact steps to reproduce the > corruption it will very hard to fix. > > You are receiving this mail because: > You reported the bug.
Hi edumax9, Were you by any chance saving your file to an external USB storage, or did you save to your internal hard disk ?
It looks like that file is corrupt. If Writer can't work out any other format for the file, it interprets as plain text. The garbage seen is the raw data from the file, with hashes (#) for non-printable characters. In this file, it looks like there is some other garbage (possibly a fragment of a different file) at the beginning, and data is missing from the end. Looks a crash (or disk disconnect or failure) in the middle of writing the file has messed up the file system entries. (Was this on a removable disk? Did you remove the disk immediately after saving the file?) I don't know what Mac OSX's disk error checking / recovery utility is (equivalent of scandisk on Windows or chkfs on Linux). It might be able to find the error and orphaned parts of the file, or a previous version of it, although that's unlikely if the disk has still been used for the last couple of months.
Closing as won'tfix. Currently, this is just a corrupted file which devs can do nothing about. edumax9: If you happen to be able to reproduce the corruption process with the current fresh version of LO (4.4) please re-open this bug and attach both a working file and then the same file after corruption.