[framework-issues] [Issue 94415] Lockfiles not parsed corre ctly; causes saves to error and owner to chang e.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94415 User mav changed the following: What|Old value |New value CC|''|'fl' --- Additional comments from [EMAIL PROTECTED] Thu Oct 2 09:53:44 + 2008 --- Setting fl in CC. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[framework-issues] [Issue 94415] Lockfiles not parsed corre ctly; causes saves to error and owner to chang e.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94415 Issue #|94415 Summary|Lockfiles not parsed correctly; causes saves to error |and owner to change. Component|framework Version|OOo 3.0 RC2 Platform|All URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|tm Reported by|mirror176 --- Additional comments from [EMAIL PROTECTED] Mon Sep 29 09:32:32 + 2008 --- New lockfiles of OpenOffice.org 3 fail to parse escaped characters correctly when the lockfile is read. Having a comma in the name (such as to set a last name suffix) causes the name to be written with a backslash in front of the comma; I think the '\,' comma is still viewed as a comma and the lockfile check begins checking to comparing contents following the comma to the next field and dropping the comma. This results in a lock not being considered as held by the creator. Enhancing the error dialog to say who holds the lock would make the error easy to diagnose. I am not sure if any other characters also cause problems. A temporary workaround is to either manually deleting the lockfile before opening a file (to avoid 'read only') and saving a file or not using the native OOo formats. I have confirmed this to give me trouble on RC1, RC2, and DEV300m30 on FreeBSD and both RC versions on Windows XP and Vista. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[framework-issues] [Issue 94415] Lockfiles not parsed corre ctly; causes saves to error and owner to chang e.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94415 User tm changed the following: What|Old value |New value Assigned to|tm|mav --- Additional comments from [EMAIL PROTECTED] Mon Sep 29 13:20:59 + 2008 --- TM-MAV: Please have a look, thanks ! - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[framework-issues] [Issue 94415] Lockfiles not parsed corre ctly; causes saves to error and owner to chang e.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94415 User mav changed the following: What|Old value |New value Ever confirmed| |1 Status|UNCONFIRMED |NEW Target milestone|--- |OOo 3.0.1 --- Additional comments from [EMAIL PROTECTED] Mon Sep 29 15:00:25 + 2008 --- Yes, there is a problem if the user name contains ',' and ';' characters. The lock file is not parsed correctly in this case. I would suggest not to use the symbols in the user name as a workaround until the fix is integrated. Setting the target to OOo3.0.1. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[framework-issues] [Issue 94415] Lockfiles not parsed corre ctly; causes saves to error and owner to chang e.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94415 User mav changed the following: What|Old value |New value Status|NEW |RESOLVED Resolution| |FIXED --- Additional comments from [EMAIL PROTECTED] Mon Sep 29 15:49:54 + 2008 --- The fix is commited to the childworkspace fwk94. The childworkspace will be integrated in OOo3.0.1 version. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
