Issue 101899 - General input/output error when opening locked files
Summary: General input/output error when opening locked files
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.1 RC2
Hardware: Mac Mac OS X, all
: P3 Trivial with 3 votes (vote)
Target Milestone: OOo 3.1.1
Assignee: thorsten.martens
QA Contact: issues@framework
Keywords: regression
Depends on:
Blocks: 101565
  Show dependency tree
Reported: 2009-05-13 22:13 UTC by roger6106
Modified: 2010-06-07 11:49 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description roger6106 2009-05-13 22:13:14 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 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: 3.0.1 opened these files without any problem. I had to revert
back to it because of this bug.
Comment 1 arguspanoptes 2009-06-17 01:08:31 UTC
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.)
Comment 2 dvaneynde 2009-07-03 13:41:16 UTC
*** Issue 101899 has been confirmed by votes. ***
Comment 3 mdxonefour 2009-08-03 09:14:42 UTC
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.
Comment 4 mikhail.voytenko 2009-08-03 09:25:49 UTC
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.
Comment 5 mikhail.voytenko 2009-08-03 15:23:30 UTC
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.

Comment 6 mikhail.voytenko 2009-08-03 15:48:49 UTC
The fix is commited to gciteratorfix cws.
Comment 7 mikhail.voytenko 2009-08-03 15:49:30 UTC
Comment 8 mikhail.voytenko 2009-08-04 08:25:29 UTC
mav->tm: Please verify the issue.
Comment 9 thorsten.martens 2009-08-04 13:30:20 UTC
Checked and verified in cws gciteratorfix -> OK !
Comment 10 thorsten.ziehm 2010-06-07 11:49:17 UTC
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] :