To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54567





------- Additional comments from [EMAIL PROTECTED] Tue Aug 14 17:24:58 +0000 
2007 -------
FYI. I may have stumbled across the cause of this bug and, in our case, the
cause was found to be that either of the following products on a Mac OS X
machine had the file open: OpenOffice.org X11 or NeoOffice.

Although I initially suspected that the bug was in SAMBA or the OOo Windows
code, I eventually found that the code that caused this problem was the Mac OS X
code in sal/osl/unx/file.cxx.

Some time ago, a Sun engineer changed the file locking code from using the Linux
and Solaris file locking logic to custom logic. In short, by reverting the file
locking code back to using the Linux and Solaris logic, opening a file from Mac
OS X no longer caused errors for OOo Windows clients.

To determine if this bug is the same as the bug I found, try the following:

1. Determine if you have any Mac OS X machines that are connected to your SAMBA
file server that are running OOo X11 or NeoOffice. If the answer is no, then
ignore this post as it isn't applicable to your case.

2. Open a file that no machine has open on a Mac OS X machine using a recent
version of OOo X11 or NeoOffice.

3. After the file is opened in writable mode on Mac OS X, try opening the file
using OOo Windows.

If you cannot open the file and OOo Windows gives you an error dialog, then this
is likely to be the cause of the bug. If you want to be absolutely sure that
this is the cause, install NeoOffice 2.1 plus Test Patch 9 from the following
URL (search for Patch-7-Test-9 in the bug to find the test patch URL for your
Mac OS X platform):

http://bugzilla.neooffice.org/bug.php?op=show&bugid=2443

Once you have NeoOffice 2.1 plus Test Patch 9 installed, repeat steps 1 through
3. If OOo Windows can now open the file in read-only mode, then we have
confirmed the cause of the bug.

For the Sun developers, the fix is very simple: remove all of the following
custom Mac OS X code from sal/osl/unx/file.cxx so that file locking is handled
the same as Linux and Solaris:

#define HAVE_O_EXLOCK
adjustLockFlags()

---------------------------------------------------------------------
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]

Reply via email to