https://bz.apache.org/ooo/show_bug.cgi?id=126846
--- Comment #2 from orcmid <[email protected]> --- Here's a proposal to stay focused and narrow on these and their immediate kin, because there will be much analysis required on just this class of problem. We want to focus on the most constant and costly few reflected that the four cases reflect. 1. Saved documents are opened later and found to be corrupted completely with their content unrecoverable altogether. 2. There are crashes and freezes and stuck messages that require AOO to be shut down, losing whatever work that had been done. Some features always fail hard because a prerequisite, such as Java, is not properly installed. 3. There are situations where a document is reported as damaged, repair is offered, but the report won't go away and AOO can't be used, whether repair is accepted or declined. 4. There are a few situations where suddenly writing aids or other features stop working or appear to be reset, spell-checker marking shows up on all text, etc. These tend to be related to corruption of the User Profile but only complicated manual workarounds are effective. It is easy to expand the scope. We want to narrow it rather than expand it so we can focus on what is likely to be a single defect case. We may find that there are multiple defects with similar symptoms and have to then sort those out. Also, we may have very simple mitigations and remedies that can be introduced in stages toward more complete solutions. That is to avoid destabilizing the software with changes we introduce. Changes must be reversible until we have confidence in them. -- You are receiving this mail because: You are the assignee for the issue.
