https://issues.apache.org/ooo/show_bug.cgi?id=118983
--- Comment #5 from Dorel <[email protected]> --- The issue is that in some cases the user is shown as “unknown” user (see below) or as another user. .doc / .odt filetype Microsoft Word | AOO Writer MS Word “locked by userName” message | “locked for editing by Unknown User” AOO Writer “locked for editing by another user” | “locked by userName” message Description of steps: 1. Open a document in Microsoft Word (or create and open it) 2. Share the document over the network 3. Open the document from the network (on another computer) using AOO Writer Microsoft Word and AOO Writer can be inter-switched - the document may be created in AOO Writer and opened in Microsoft Word. Actual: A message is shown informing the user that the document is opened by "Unknown User" (AOO Writer) / "another user" (Microsoft Word), although opening the document using the same office suite user's name is shown. See attached screenshots: Word – Word: file created in Word and opened in Word Word – Writer: file created in Word and opened in Writer Writer – Word: file created in Writer and opened in Word Writer – Writer: file created in Writer and opened in Writer The issue also reproduced when using LibreOffice Writer instead of AOO Writer. Expected: When opening a file opened by another user, the user is expecting to see the name of the user that opened the file. Opening the file using the same office suite the name of the person that already opened the file is shown in the message box. Configurations used: 1. OS Mac OS X Yosemite (10.10.1) Windows 7 Pro x64 Windows 8.1 Pro x64 2. Office suite Microsoft Office 2007 AOO Writer 4.1.1 AOO Writer 4.2.0 Libre Office 4.3.5 Different cases / scenarios that might point to the problem: Case 1 – different file formats: While investigation I found that bot Microsoft Office and Open Office store the name of the user that has the file opened in a temporary file: -Open Office temp file (.~lock.filename.odt#) contains: firstName lastName, ComputerName/Username,computerName,date hour, file:///C:/Users/Username/AppData/Roaming/OpenOffice/4; -Microsoft Office (~$test2): Username U s e r n a m e M S G o t h i c Ŕ 3 Đ 3 As it can be seen, different formats are used by the office suites – this may indicate a problem in interpreting the contents of the file by another office suite (in this case AOO Writer). Case 2 – improper quitting of Writer: Quitting improperly (killing the office process; AOO crashes; etc.) and therefore, not deleting the owner file (.~lock) the file appears as being opened by the user that previously opened the file (the user for which the office suite quitted improperly). If the same user tries to open the file, it appears as being locked by himself. Deleting the owner file (.~lock) while another user still has the message box shown on the screen, trying to open the file the message “locked for editing by Unknown User” is shown. This issue might be transformed in another bug. Impact of the bug: There is a high chance that users encounter this behavior, especially if more users have to edit the same file. In my personal experience I encountered this when in my company we used a network file for our daily reports and there were many persons trying to edit the same file. It was useful to know who was last editing the file in case something happened (e.g. case 2 above) and the file could not be opened for some time. Similar bugs: Searching the bug database for similar issues, I could not find any. If a user opens the file in Word and another user opens the file in Writer (or vice-versa) – the message shown is “locked for editing by Unknown User” - this might be a issue on how AOO reads contents from lock files of other office suites (see Case 1 above). If opening the file it is locked by another person Case 2 above might apply. A partial solution for this is to check that the file is not opened in another place, deleting the .~lock file and then opening the file. In order to figure out the exact case the reporter is encountering, some exact steps on how the reporter reproduced the issue would help. -- You are receiving this mail because: You are the assignee for the issue. You are watching all issue changes.
