Issue 94415 - Lockfiles for users with ',' or ';' in name are not parsed correctly; causes saves to error and owner to change.
Summary: Lockfiles for users with ',' or ';' in name are not parsed correctly; causes ...
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.0 RC2
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: OOo 3.0.1
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
: 95000 (view as issue list)
Depends on:
Blocks:
 
Reported: 2008-09-29 10:32 UTC by mirror176
Modified: 2009-08-20 23:46 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description mirror176 2008-09-29 10:32:32 UTC
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.
Comment 1 thorsten.martens 2008-09-29 14:20:59 UTC
TM->MAV: Please have a look, thanks !
Comment 2 mikhail.voytenko 2008-09-29 16:00:25 UTC
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.
Comment 3 mikhail.voytenko 2008-09-29 16:49:54 UTC
The fix is commited to the childworkspace fwk94. The childworkspace will be
integrated in OOo3.0.1 version.
Comment 4 mikhail.voytenko 2008-10-02 10:53:44 UTC
Setting fl in CC.
Comment 5 mikhail.voytenko 2008-10-02 10:55:47 UTC
Changing the title accordingly.
Comment 6 mikhail.voytenko 2008-10-06 11:05:19 UTC
mav->tm: Please verify the issue.
Comment 7 mikhail.voytenko 2008-10-28 11:21:22 UTC
*** Issue 95000 has been marked as a duplicate of this issue. ***
Comment 8 thorsten.martens 2008-11-06 11:52:17 UTC
Checked and verified in cws fwk94 -> OK !
Comment 9 thorsten.martens 2008-12-04 12:26:04 UTC
closed
Comment 10 realgrouchy 2009-03-09 18:00:44 UTC
I'm still getting this problem on 3.0.1.

I'm running OOo on XP2 on Parallels on an Intel iMac running OSX 10.5.6.

For reference, the lockfile contains the following information (where "foobar"
is the username on the mac):

,FOOBAR/Administrator,foobar,09.03.2009
12:44,file:///C:/Documents%20and%20Settings/Administrator/Application%20Data/OpenOffice.org/3;

Details: The User Data section in OOo is completely blank. I am opening the file
using the "open a file" link in the OOo splash. The file is located withtin my
public folder on the mac. After closing OOo (including the QuickStarter), the
lockfile is not deleted (not that it should be there in the first place...)

I'm wondering if this is related to why I can't double-click on a networked file
on the mac for it to open in OOo while browsing it in Windows.

Or possibly it thinks that it's being opened in the Mac environment.

All I know is it's costing me a lot of productivity at work. My workaround will
be reinstalling 2.4. 
Comment 11 mikhail.voytenko 2009-03-09 19:03:11 UTC
mav->realgrouchy: First of all, sorry, but you have written yourself that in
your case the lock file does not contain the symbols. That mean that you can not
have _this_ problem.

Secong, as you have already written the problem is that the lock file is not
removed during office shutdown in your case. But the lock file you have
mentioned is from windows platform. It looks like the file is still open from
windows machine "foobar". So for now I see no bug here at all.
 
If you would like to discuss the problem further please open a new issue. I
would kindly ask not to mix multiple bugs together.
Comment 12 peterkodermac1234 2009-08-20 23:46:38 UTC
I'm getting same problem on 3.1.0. When I save and then close file and and try
to open it again I get message the object can not be accessed due to
insufiecient user rights. (Linux Fedoar) User rights are ok ! It happen just
with OO version 3 not older ones. But I see no lock file and I also do not have
user name contains ',' and ';' characters.