[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 User mav changed the following: What|Old value |New value Status|RESOLVED |VERIFIED --- Additional comments from m...@openoffice.org Fri Dec 3 13:12:43 + 2010 --- Development issue, verified by myself. - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 User mav changed the following: What|Old value |New value Status|NEW |RESOLVED Resolution| |FIXED --- Additional comments from m...@openoffice.org Fri Nov 19 09:57:08 + 2010 --- Workarounded in the cws fwk160, ftruncate() is now used in the scenario only when an existing file has been opened. The file is truncated to be empty before writing in this case. But as I have mentioned already, ftruncate() is an important functionality, and incomplete implementation of it might cause other problems. - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 User mav changed the following: What|Old value |New value Target milestone|OOo 3.3 |OOo 3.4 --- Additional comments from m...@openoffice.org Fri Jul 2 14:31:01 + 2010 --- Changing the target to 3.4, not enough resources to do it for OOo3.3. - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 User tm changed the following: What|Old value |New value Assigned to|tm|mav --- Additional comments from t...@openoffice.org Mon Nov 9 10:35:04 + 2009 --- reassigned - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 User mav changed the following: What|Old value |New value Target milestone|--- |OOo 3.3 --- Additional comments from m...@openoffice.org Mon Nov 9 11:06:56 + 2009 --- Although the bug has a low priority, it should not be difficult to introduce the workaround for the scenario. Thus I set the target to OOo3.3 for now. - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 User mav changed the following: What|Old value |New value Priority|P3|P5 --- Additional comments from m...@openoffice.org Thu Mar 5 11:11:49 + 2009 --- @sb: Thank you for the investigation, 'svn annotate' has confused me. Indeed, the approach looks to be there from the very beginning of ucb, it was moved from chaos project. The ftruncate() call here looks to be for the case when the target file can be overwritten. In this case the target file is not truncated before writing. Instead, the new information is written and afterwards the expected size is set to throw away the rest of old data ( in case the old file was bigger that the new version ). It does not look to be really necessary for the new file insertion. Anyway, ftruncate() is a very important functionality, and must be supported. The current implementation is partially based on this call. If an operational system does not support it completely, some office functionalities would not work. Changing the priority accordingly. The bug is not about not using ftruncate at all, the bug is about not using it in case of new file creation without overwriting. - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 User of changed the following: What|Old value |New value CC|''|'mav' --- Additional comments from o...@openoffice.org Wed Mar 4 09:06:22 + 2009 --- @ mav: Can you please have a look? - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 User sb changed the following: What|Old value |New value CC|'mav' |'mav,sb' - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 --- Additional comments from cche...@openoffice.org Thu Mar 5 03:53:50 + 2009 --- I determined what was happening exactly and was able to get the gvfs developers to work around the issue it was causing. What was happening was when writing a file it truncates the file to the size of the file, which should basically be a NOP, but since gvfs fuse didn't support truncate at all it was causing the save to fail. - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 --- Additional comments from cche...@openoffice.org Thu Mar 5 03:55:37 + 2009 --- Oh yea I forgot to mention the way they worked around it was support truncate to 0 and truncate that is the same size as the current file size since they are both easy to implement. For the most part implementing truncate to larger or smaller sizes than current file size is very hard to implement in gvfs backends since the backends don't tend to have ways to support resizing of files. - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99833 --- Additional comments from s...@openoffice.org Thu Mar 5 07:57:23 + 2009 --- [...@mav, for completeness: Issue 37704 appears to be unrelated here after all. shell::write (ucb/source/ucp/file/shell.cxx) called aFile.setSize before and after SVN rev. 99499. The thing that actually changed there was to no longer call aFile.sync but instead check the return value of aFile.close, which calls the close system call, which in turn is assumed to call COMMIT in case of an NFS file.] - 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
[framework-issues] [Issue 99833] change CreateOwnLockFile() or code it calls to not use ftruncate size != 0
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 + 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
