Bug 45902

Summary:	AUTOTEXT FILESAVE AFP - After edit autotext on afp volume: -5010 afpFileBusy
Product:	LibreOffice	Reporter:	Benjamin Hagemann <benny>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	medium	CC:	iplaw67, thb
Version:	3.4.5 release
Hardware:	x86-64 (AMD64)
OS:	Mac OS X (All)
Whiteboard:
i915 platform:		i915 features:

Description Benjamin Hagemann 2012-02-10 09:10:34 UTC

Mac OS X 10.6 with LibreOffice 3.4.5
My autotext-file test.bau is on a Mac OS X 10.6 Server with AFP Shares.

I start LibreOffice, create a new document, go edit,autotext, select one autotext of my autotext-file, click on the right side the AutoText Drop-down and select 'edit'.
Than the autotext opens and I can edit it, but I can not save or close with save this file.
On the Mac Server in the AFP log I found the error code -5010 for afpFileBusy.

The file handling for autotext files seems different to normale file handling in this point. Text documents and all other file types I can create, edit, save without problems.


I have the right permissions to the autotext-file (owner, read+write) and to the share (full-access). The error-code shows that it is not an permission-problem, it seems a filehandling special with afp.

Comment 1 Benjamin Hagemann 2012-02-14 04:24:21 UTC

I validate LibreOffice 3.5 - same behaviour :/

Comment 2 Benjamin Hagemann 2012-08-29 12:43:38 UTC

I validate this today with LibreOffice 3.6.1.2 on MacOS X 10.7.4, too.

Comment 3 Alex Thurgood 2012-08-29 19:28:34 UTC

Please see bug 40907.

IMO, this report is a duplicate of that bug.

Alex

Comment 4 Alex Thurgood 2012-08-29 19:28:56 UTC


*** This bug has been marked as a duplicate of bug 40907 ***

Comment 5 Alex Thurgood 2012-08-29 19:33:30 UTC

You'll note that there has been no progress on the AFP concurrent share lock up bug since Sept 2011, i.e. nearly a year.

Alex

Comment 6 Alex Thurgood 2012-08-29 19:35:15 UTC

Adding Thorsten to CC.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.