To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=62229
------- Additional comments from [EMAIL PROTECTED] Sun Feb 19 10:38:31 -0800 2006 ------- There is a recently posted (Feb. 6, 2006) suggestion at: http://www.oooforum.org/forum/viewtopic.phtml?t=31367&highlight=afp which argues: ************************* Solved! Here's a tip I found in another forum: Comment out two lines in the soffice file. Right or control click on the application and select Show Package Contents. Double click on Contents and again on openoffice.org2.0. Double click on the program folder and open the file soffice using TextEdit or some other plain text editor. Add comments (#) to the lines which enable file locking so they appear as below. # file locking now enabled by default #SAL_ENABLE_FILE_LOCKING=1 #export SAL_ENABLE_FILE_LOCKING Save the changes and start OOo. Everything should work as expected. *************************** I saw other comments which suggested that this was not a solution including the statements on the OpenOffice Mac support forum (which is at trinity, not at oooforum.) Of course, turning off file locking does not solve the problem, it just means you can now corrupt the subject file ;=} WHile this may be a workaround for short term, I don;t think its a good diea to have all Mac users turning off file locking in ordfer to be able to use OOo --------------------------------------------------------------------- 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]
