Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Empty OOo saved as UOF file comes up read only | ||
---|---|---|---|
Product: | General | Reporter: | wolframgarten |
Component: | code | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P4 | CC: | issues, Mathias_Bauer |
Version: | DEV300m74 | Keywords: | regression |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Windows, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
wolframgarten
2010-03-11 14:48:17 UTC
OS set. Broken, worked in 3.1.1. Keyword set. OOo 3.3 is nearly final. I change the target of this issue to OOo 3.x. Please find a solution and set a correct target, if you know when a fix can be integrated. Adapting Summary and Component as this issue also comes up for a writer document. cl->mba: I heard you know about this filter? Please delegate Mikhail, please have a look. Maybe our locking procedures don't work well for xslt based filters?! I see currently no way to have a difference in OOo locking behavior for this filter. What could be possible, is that the filter holds the stream open, and thus let system filelocking prevent further document editing. As far as I know xslt based filters are java filters, and we had already similar problems with them. The rather rare circumstances and the easy workaround (restart) justify a P4 Since this is a regression I do not agree to re-priorizing this. Prio 4 is as good as "close it, wont fix". Reset assigne to the default "issues@openoffice.apache.org". |