To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 Issue #|99833 Summary|change CreateOwnLockFile() or code it calls to not use | ftruncate size != 0 Component|framework Version|OOo 3.0.1 Platform|Unknown URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|tm Reported by|ccheney
------- Additional comments from cche...@openoffice.org Tue Mar 3 22:26:04 +0000 2009 ------- I am working on trying to get OOo to work (save files) across gvfs fuse backends for Ubuntu. This currently doesn't work due to what I think is an issue in CreateOwnLockFile() which causes ftruncate() at some point to be called with a non zero size. Truncating to non-zero is not supported under gvfs-fuse. I am not sure exactly what is being written into the lock file and at what times, but would it be possible to truncate the file to zero when it needs to truncate and then write out the data in full again (if needed)? The current way it seems to work is when you save it creates the lock file seems to fail at some point with ftruncate size !=0 and leaves the lock file behind. If you then try to save again with the same file name it works fine. This is very non-optimal... :-( --------------------------------------------------------------------- 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: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
