> And actually in the FTP case it could very well be your ftp server is buggy.
> There is a known bug in pureftpd that causes gvfs not to work properly.
Chris, In fact I don't think this is an issue with gvfs or pureftpd. pureftpd may affect other bugs, but it is not the case here. I have tested it on vsftpd locally. OpenOffice still fails with the same error.
-Files can be written to folder via nautilus.
-Files can be saved through the gedit save dialogue.
-File cannot be saved from the OOo save dialogue.
I found, with more tests, that OOo does create a lock file,
Chris can we schedule some software testing for "saving/editing OOo docs on remote filesystems". It would be worth testing this use case with smb, ftp, sftp and nfs as well. Please keep in mind that I am currently running these tests on both intrepid and jaunty. Please ping me if you are interested.
> If that case it is probably not a bug caused by gvfs.
You're correct seb. I don't think this problem is with gvfs since it only seems to affect OOo for now. If anything, it is the way OOo treats the remote file system.
> And actually in the FTP case it could very well be your ftp server is buggy.
> There is a known bug in pureftpd that causes gvfs not to work properly.
Chris, In fact I don't think this is an issue with gvfs or pureftpd. pureftpd may affect other bugs, but it is not the case here. I have tested it on vsftpd locally. OpenOffice still fails with the same error.
-Files can be written to folder via nautilus.
-Files can be saved through the gedit save dialogue.
-File cannot be saved from the OOo save dialogue.
I found, with more tests, that OOo does create a lock file,
cat /home/ftp/ dropbox/ .~lock. testsave. odt# default, 28.03.2009 20:19,file: ///home/ ubuntu/ .openoffice. org/3;
,ubuntu,
Chris can we schedule some software testing for "saving/editing OOo docs on remote filesystems". It would be worth testing this use case with smb, ftp, sftp and nfs as well. Please keep in mind that I am currently running these tests on both intrepid and jaunty. Please ping me if you are interested.
> If that case it is probably not a bug caused by gvfs.
You're correct seb. I don't think this problem is with gvfs since it only seems to affect OOo for now. If anything, it is the way OOo treats the remote file system.