[Issue 126990] File saved normally then opened and filled with #

2021-03-06 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #16 from John --- See "Text in document transformed to #" at https://forum.openoffice.org/en/forum/viewtopic.php?f=7=104676#p507553 where a user describes exactly what happened to cause a .odt file to become full of #. > The

[Issue 126990] File saved normally then opened and filled with #

2021-03-05 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #15 from John --- See Comment 46 in Issue 126869 - Analysis Task: Lost/Corrupted Documents after Save/Shutdown where I shut down the PC (Start > Power > Shutdown) a few seconds after the green bar had finished crossing the screen. The

[Issue 126990] File saved normally then opened and filled with #

2020-12-09 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #14 from John --- Also, for someone with programming skills, a simple test would probably be 1. Add an infinite loop a few lines after line 52 so that AOO loops during the file write 2. Wait until AOO is looping during the file

[Issue 126990] File saved normally then opened and filled with #

2020-12-09 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #13 from John --- Also, for someone with programming skills, a simple test would probably be 1. Add an infinite loop a few lines after line 52 so that AOO loops during the file write 2. Issue a shutdown by closing the laptop lid.

[Issue 126990] File saved normally then opened and filled with #

2020-12-09 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #12 from John --- Unfortunately I don't have sufficient programming skills :-( I recently assisted a user with a corrupted .ods file which I think resulted from the same "shut down before writing is completed" cause. In his case

[Issue 126990] File saved normally then opened and filled with #

2020-12-09 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #11 from oooforum (fr) --- (In reply to John from comment #9) > where I suggest the NULLs are written in > Line 52 of DEFLATOR. If you have programming skill, you can submit a PR on Github with this fix:

[Issue 126990] File saved normally then opened and filled with #

2020-12-09 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 Peter changed: What|Removed |Added Severity|Normal |Critical CC|

[Issue 126990] File saved normally then opened and filled with #

2020-12-08 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #9 from John --- As a) this bug is confirmed, b) there are hundreds of reports of it in the forum, c) it causes complete data loss and nothing can be recovered from the file (the # are displayed because the file is full of NULL

[Issue 126990] File saved normally then opened and filled with #

2019-06-30 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #8 from John --- Yes. There are hundreds and hundreds of cases on the forum. I strongly suspect that the problem arises when AOO mishandles a hibernate or sleep interrupt when it is in the process of saving a file. I further suspect

[Issue 126990] File saved normally then opened and filled with #

2019-06-07 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 oooforum (fr) changed: What|Removed |Added CC||ooofo...@free.fr --- Comment #7 from

[Issue 126990] File saved normally then opened and filled with #

2017-03-06 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #6 from John --- I am sorry but there is nothing which can be done because the file is full of zeros - there is (literally) nothing in it. For some reason the file was not saved. Search the forum with and

[Issue 126990] File saved normally then opened and filled with #

2017-03-05 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 orcmid changed: What|Removed |Added CC|orc...@apache.org | -- You are receiving this

[Issue 126990] File saved normally then opened and filled with #

2017-03-05 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #5 from Tania Valladares --- I am trying to recover a document in which the text has been replaced with #. It is extremely important. Can you try to see the document as I understand there's nothing I can do

[Issue 126990] File saved normally then opened and filled with #

2017-03-05 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 Tania Valladares changed: What|Removed |Added CC|

[Issue 126990] File saved normally then opened and filled with #

2016-05-31 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #4 from John --- Created attachment 85564 --> https://bz.apache.org/ooo/attachment.cgi?id=85564=edit Some examples of damaged files - all zeros, garbage and a mixture See the forum post 22 page term paper

[Issue 126990] File saved normally then opened and filled with #

2016-05-30 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 --- Comment #3 from orcmid --- (In reply to John from comment #2) > Created attachment 85563 [details] > An example .odt file which opens as "full of ##" > > This file is taken from >

[Issue 126990] File saved normally then opened and filled with #

2016-05-29 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 John changed: What|Removed |Added CC||john.h...@yahoo.co.uk ---

[Issue 126990] File saved normally then opened and filled with #

2016-05-29 Thread bugzilla
https://bz.apache.org/ooo/show_bug.cgi?id=126990 orcmid changed: What|Removed |Added Component|help|save-export