Issue 113834

Summary: Opening locked file produces incorrect error
Product: General Reporter: cheyrou23 <cheyrou23>
Component: uiAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 3.2.1   
Target Milestone: ---   
Hardware: Mac   
OS: Mac OS X 10.5   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
Example error message
none
Example error message none

Description cheyrou23 2010-08-12 13:14:46 UTC 
Open a document in either Calc or Writer.

Attempt to open the same document on another Mac.

Error message appears stating:

"Error during shared access to <filename>"

Previously the error would appear as "File <filename> is in use by <username>".  The current error 
gives little indication the file is in use elsewhere.

Tested on Open Document format and Microsoft Office format in Writer and Calc.  Error is the same 
whether using File - Open from the menu or double-clicking on the file in Finder.

Testing carried out using files stored on an Apple File Server using AFP.

Also tested using DevSnapshot OOO330m3 (Build:9519) and found the same result.

Not tested on other platforms.
Comment 1 cheyrou23 2010-08-12 13:15:28 UTC 
Created attachment 71054 [details]
Example error message
Comment 2 cheyrou23 2010-08-16 11:53:49 UTC 
An important point about this issue - the different error no longer offers the option to open the document 
read-only when another user already has the document open.
Comment 3 cheyrou23 2010-10-28 17:40:19 UTC 
Created attachment 72771 [details]
Example error message
Comment 4 cheyrou23 2010-10-28 17:45:24 UTC 
Have also seen this issue recently.  Tested under 3.2, 3.2.1, and 3.3 (DevSnapshot).  Error is the same.

When document is stored on a Windows file system (connected via SMB in this case) the correct 
message appears giving the option to:

Open Read-Only
Open Copy
Cancel

Using identical machines (iMac running 10.5.8) and the same file stored on AFS the error appears as 
described above.

This was previously an issue in OO for a previous version but was resolved (I think by version 3.1).