Apache OpenOffice (AOO) Bugzilla – Issue 56575
.odt Files can't be save over mounted Webdav Directory
Last modified: 2013-07-30 02:18:57 UTC
1.) One PC with Windows XP embedded with IIS 5.1 2.) One PC with Linux (Knoppix 3.9, Kernel 2.6.11, XFree 4.3) 3.) I mount with the Linux PC to the Xp PC over dvfs 2.6 (mount -t davfs http://192.1681.250/Documents /home/knoppix/Documents) 4.) The mount process works fine. I can create file change it, read and write it. 5.) Then I start OpenOffice (writer or calc) and create a new File with some simple content. 6.) Then I save the file 7.) I check now the File on teh Windows Side. The file was created but it is empty. 8.) I can open it on the linux site and it is still empty. 9.) Now I save a new File with the ave or another content but now with a different extension such as .doc or .pdf 10.) This works fine. The file is save on the windows directory. It seems to me that all Open Documents Formats can't be saved over a mounted wedav directory. I have made also another test: 1.) Start OpenOffice and start writing a letter. 2.) Save it on teh Linux PC. This works fine. 3.) Copy the file to the mounted webdav directory. 4.) It can be open on the windows site without any problems. For me it seems to be a problem in the saving mechanism in conjunction with davfs. I will also report this problem to the guys of davfs. I hope you can fix this problem. Thank you. Best regrads Juergen
Hi Juergen, I will forward this issue to Kai, who is the expert on OOo's WebDAV Content Provider. But before I do so, let me adjust the severity / priority (which you specified as 'P1'). I do accept that this might be a severe issue for you, but the OpenOffice.org bug reporting guidelines (http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html) should provide some hints why this is probably not a 'P1' issue, but 'P2' at best. Hi Kay, can you please have a look at this issue? Thanks, Matthias
We're not talking about OOo's WebDAV Provider here. From OOo's perspective the DAV resource appears as 'normal' file system directory (this is what davfs is for). Thus, the problem cannot be located in the WebDAV Provider, but in either the File-UCP or the Package-UCP. Lets start with the File-UCP, which is with Andreas. Andreas, handing the issue over to yoy.
set to 2.0.3
abi->hro: Well, the problem is here, that we do not have the possibility to lock the file for writing, which is, using the current design, mandatory for OO to write files. We do have the same problem with linux systems having no lockdaemon running. Some more general solution is needed .... like a new command - "write-to-unlocked" or something like that.
.
KSO: Not enough time left to fix this for 2.0.3 Retargeting to 2.0.4
The problem is here the nonavailability of locking.
KSO: No time to fix this in 2.0.4 timeframe. Setting target to 2.1.
ABI->messiman: Well - I was not able to reproduce the bug with my current linux system and an OpenOffice 2.0.4. But generally, OpenOffice tries to lock the file for writing and that might be the problem - in the system wide configuration file of davfs there is the option use_locks, which should be set to "1" to enable locks. There are then also several questions with regard to zero length files on the mailing list of davfs and I guess, you do have a problem with dav, otherwise. OpenOffice handles the filesystem in a completly transparent way.
is this issue still valid ? set target to 3.x.
work just fine with option use_locks 1
Reset assignee on issues not touched by assignee in more than 2000 days.