To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=58215 Issue #:|58215 Summary:|Input/Output error on opening or saving documents Component:|Word processor Version:|OOo 2.0 Platform:|All URL:| OS/Version:|All Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P2 Subcomponent:|code Assigned to:|mru Reported by:|tuharsky
------- Additional comments from [EMAIL PROTECTED] Sun Nov 20 23:19:00 -0800 2005 ------- This problem has many faces and may be connected with issue 54136. Linux is meant to be Debian 3.1 Sarge (stable) and OOo20 sk build. 1. document (dosen't matter the type) on Samba 3.14 share is opened correctly from Linux OOo. When it comes to auto-save or user save, sometimes he gets "Input/output" error and document is not saved. In contrast to issue 54136, it is NOT dependent on opening the same document simultaneously from Windows machine. Occurs rather frequently (we have about 30 Linux machines here) but we cannot tell, what is the factor here -sometimes no error occurs and the document can be saved nicely. When error occurs, the document is probably not possible to save even under different name, because even if the new document is created, sometimes it is empty. Thus there is DATA LOSS. 2. We've gotten the same error on WindowsXP machine opening a file from Thunderbird e-mail message. The file for sure was not ever opened by other user. Again, we're not able to reproduce. It occurs quite randomly from our point of view. 3. Linux NFS v3 share. Document cannot be even OPENED from such share. This can be reproduced everytime -no chance to open document from NFS share. OOO 1.1.4 and 1.1.5 never displayed such behaviour. We strongly consider reverting back to OOo 1.1.4, there is amount of files created under 2.0 however that could produce problems (OOo 1.1.5 cannot save to OpenDocument, so users could be annoyed by using again other format for save, and we have instructed them already to use OpenDocuments). Moreover, we created system MIME assignments for all files to OOo2 and would take lot of futureless backwards steps to revert to OOo1.1.4. Without trying to be offensive, we'd be thankful to have an errata 2.0.1 release ASAP, since this bug is killer for us (and must be for everyone who organises his documents on network). Fortunately, not many users use OOo20 intensively, but such of them who do, they are far from success with using OOo2.0. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
