https://bugs.documentfoundation.org/show_bug.cgi?id=167313
--- Comment #37 from b. <[email protected]> --- As I _assume_ it will take some time until a dev has time to analyse the already bibisected issue ... and as I step by step become a pro in workarounds ... If you stumble into this issue, 1. Keep the file open and save it with a new name, DO NOT close it before you are fully finished with repair, save again with another new name to work with, if it is encrypted make the copy without password. Ver. BAD in the following. 2. Check through the undo steps, saving the file to a third temporary name, with luck you find a step / version which saves quick, heals the issue. 3. If not successful check for available older copies or backups, remember to also check for *.bak versions, also in your user directory / profile. Before accessing any of them make a new separate backup copy and only work with these copies. Check if any of them is ok, saves fast, then save unencrypted. 4. If no success in 2. or 3. make a new file. The file from step 2., 3. or 4. is named as GOOD below. 5. Now you have two unencrypted files, one BAD and one GOOD. 6. From inside GOOD select Edit - Track Changes - Compare Document... , select the newer one - BAD - with issue as compare target, 7. you get a list of differences, evtl. you need to open Edit - Track Changes - Manage, 8. the differences are in the logic as if the GOOD file had the content of the BAD file and what needs to be changed to go back to it's old content. By !rejecting! the proposed changes the newer content is pulled into the old file. 9. When finished try how well the new version works. If not retry with other versions / variations. 10. In the logic of the patchworked LO design ... evtl. a dev. would like to implement a CPU-load-checker, and ring an alarm whenever writer has high CPU load for some time? And: 11. Like to implement something near the recipe above as "repair-attempt" option? 12. Evtl. with an option to check for differences and mail them to LO for analysis? It shouldn't stay like it is ... -- You are receiving this mail because: You are the assignee for the bug.
