Created attachment 88105 [details]
Error messages in french
Problem description: Error saving file to a Vnxe 3100 SAN in NAS CIFS mode
Steps to reproduce:
Install Librofice 4.x
Create a document in a share folder on a Vnxe3100
After 1 or to oepartion, errot message and file is locked
Tested in the same envirronement with Openoffice 4 : OK
Operating System: Windows 7
Version: 184.108.40.206 release
Olivier: just for the test, could you give a try to pre release 4.1.3? (see http://www.libreoffice.org/download/pre-releases/)
(In reply to comment #1)
> Olivier: just for the test, could you give a try to pre release 4.1.3? (see
220.127.116.11 installed this morning, same problem.
Michael: do you know who may help here?
BTW, quick translation of error messages:
Error during saving of the document ..., access denied
IO Error for second screenshot.
Looks like a duplicate of Bug 68082 (see especially Bug 68082 comment 4), which might be in turn caused by the same cause as (the recently fixed) Bug 67534.
@Olivier MORIN: Could you please run LibreOffice installation, choose 'Modify' and uncheck the installation of Windows Explorer extensions? Does it solve your problem?
Yes after unsinstalling this extenion it is OK.
I have installed the libreoffice-4-1~2013-10-25_22.57.18_LibreOfficeDev_18.104.22.168.0_Win_x86 and it is also OK.
(In reply to comment #5)
> I have installed the
> libreoffice-4-1~2013-10-25_22.57.18_LibreOfficeDev_22.214.171.124.0_Win_x86 and it
> is also OK.
Did you install it from the command line with 'WRITE_REGISTRY=1'? If not it's irrelevant, because dev buils don't write the appropriate registry values by default.
Anyway I'm able to reproduce this bug using 126.96.36.199 with a simple Windows 7 share. Uninstalling shell extensions solves the problem.
Yes i did !
Maxim: first thank you for the help here.
About fdo#67534, the fix is present from 4.1.4 not 4.1.3 so it's normal you can reproduce the problem with 4.1.3
(In reply to comment #8)
> About fdo#67534, the fix is present from 4.1.4 not 4.1.3 so it's normal you
> can reproduce the problem with 4.1.3
Yes I know, just wanted to prove that it's related to shell extension.
What we have now: Olivier MORIN confirmed that it's fixed in 4.1 dev build. I can also confirm the same for several master builds, the oldest one is from 2013-10-15_15:51:52. master build from 2013-10-10_06.40.14 still had that bug. The fixes for Bug 67534 were pushed at 10-11 & 10-14. So it's resonable to assume that it's indeed a duplicate. Closing as RESOLVED FIXED.