Apache OpenOffice (AOO) Bugzilla – Issue 101899
General input/output error when opening locked files
Last modified: 2010-06-07 11:49:17 UTC
I often lock files that I use as a starting point for other documents. I also lock files once I am done with them to prevent them from accidentally being changed. Since I updated to OpenOffice.org 3.1 I cannot open these files. I now get a message "General input/output error while accessing [file]." Steps to reproduce: 1. Create a text document and save it. 2. Navigate to the document in the Finder. 3. Right-click on the file, and choose get info. 4. In the box that appears check the "locked" checkbox. 5. Try to open the file. Regression: OpenOffice.org 3.0.1 opened these files without any problem. I had to revert back to it because of this bug.
As a clarification, this behavior is not restricted to text documents. All six types of documents have that error when trying to open a locked file. (A text document is just the easiest type to create as an example.)
*** Issue 101899 has been confirmed by votes. ***
MD->MAV: As discussed please have a look. Seems that Office fails to switch into read-only modus automatically. When you select the "Read-only" checkbox in the file open dialog, it seems to work.
Strating from OOo3.1 the system file locking is used again. So it is correct that the locked document can not be edited. But the office should open the document read-only in this case instead of showing the error. Taking over the issue.
The problem is that a wrong error code is provided to the framework. As result the framework does not detect that the opening fails because the file is locked. This is definitely the Mac problem only. Actually this is no real regression. The Mac is officially supported starting from OOo3.0, and at this time there was already no system file locking usage. When the system file locking was turned on, the implementation was used as it is, without adjusting for Mac. There is an easy fix, I will integrate it for Mac platform only to avoid unnecessary risk.
The fix is commited to gciteratorfix cws.
.
mav->tm: Please verify the issue.
Checked and verified in cws gciteratorfix -> OK !
This issue is closed automatically. It is in state 'verified/fixed' since 2 releases (OOo 3.1.1 and OOo 3.2). The policy [1] indicates that such older issues should be closed. If this issue still occur in a current build (OOo 3.2.1 or >DEV300m80) please reopen the issue and set the target accordingly. [1] : http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues