Bug 34171 - Bad user reported when file is locked
Summary: Bad user reported when file is locked
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Libreoffice (show other bugs)
Version: 3.5.0 Beta2
Hardware: All All
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
: 64391 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-11 02:35 UTC by sf
Modified: 2014-07-20 19:34 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description sf 2011-02-11 02:35:20 UTC
There is strange behaviour with file locking when xls file are accessed by LibreOffice and Excel. This behaviour (maybe) is common to all other program like Writer, Impress,...

Situation:

   * user A with Excel 2000
   * user B with LibreOffice 3.3 / OpenOffice 3.2

Example 1, step to reproduce:

   * user A open, modify,save and close "example.xml" file with Excel 2000
   * user B open "example.xml" with LibreOffice 3.3
   * user A open "example.xml" and Excel tell the user that file is
     opened by user A (expected: user B)
   * user A open "example.xml" with LibreOffice and the program tell
     the user that file is opened by user B (as expected)


Example 2, step to reproduce:

   * user B open, modify,save and close "example.xml" file with LibreOffice 3.3
   * user A open "example.xml" with Excel 2000
   * user B open "example.xml" and LibreOffice tell the user that file is
     opened by "unknown user" (expected: user A)
   * user B open "example.xml" with Excel and the program tell
     the user that file is opened by user A (as expected)

In mixed environment, Excel and Calc, seems that is not possible to know who is locking the file. If I know who is locking the file, for example, I could ask him to close the file.
Comment 1 sf 2011-02-11 02:54:34 UTC
In mixed environment, Excel and Calc, seems that is not possible to know who is
locking the file. If I know who is locking the file, for example, I could ask
him to close the file. This behaviour (maybe) is common to all other program like Writer, Impress,...

Situation:

   * user A with Excel 2000
   * user B with LibreOffice 3.3 / OpenOffice 3.2

Example 1, step to reproduce:

   * user A open, modify,save and close "example.xml" file with Excel 2000
   * user B open "example.xml" with LibreOffice 3.3
   * user A open "example.xml" and Excel tell the user that file is
     opened by user A (expected: user B)
   * user A open "example.xml" with LibreOffice and the program tell
     the user that file is opened by user B (as expected)


Example 2, step to reproduce:

   * user B open, modify,save and close "example.xml" file with LibreOffice 3.3
   * user A open "example.xml" with Excel 2000
   * user B open "example.xml" and LibreOffice tell the user that file is
     opened by "unknown user" (expected: user A)
   * user B open "example.xml" with Excel and the program tell
     the user that file is opened by user A (as expected)
Comment 2 Björn Michaelsen 2011-12-23 11:42:55 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 3 sf 2011-12-27 05:01:52 UTC
Same behaviour in LODev 3.5.0beta2 .  If you try to open a file that is already opened by Microsoft Excel, Lib0 tell me that the file is locked by "unknown user". This info is useful only if there is a name and if the name is correct.
Obviously, all software (Excel and LibO) have a registered user.
Comment 4 James 2013-03-03 13:01:15 UTC
I tried reproducing this with LO 4.0.1.1 (nightly).

* I created an excel file and saved that to example.xml
* then Opened that file in LO while keeping excel open
* modify then tried to save file in LO
* choose XML (instead of odf)
-> crash (log: http://pastebin.com/iyiSbTZa)

This is still valid for LO 4.0.1.1. Also the crash is reproducible.

Setting platform from "Windows" to "All" since I'm on OS X.

Since this results in a reproducible crash of LO setting importance from "medium" to "high" and severity from "normal" to "major".

Maybe a dev can look into this?
Comment 5 m.a.riosv 2013-05-09 14:15:25 UTC
*** Bug 64391 has been marked as a duplicate of this bug. ***
Comment 6 bfoman 2013-08-14 22:40:48 UTC
(In reply to comment #4)
> I tried reproducing this with LO 4.0.1.1 (nightly).
> * I created an excel file and saved that to example.xml
> * then Opened that file in LO while keeping excel open
> * modify then tried to save file in LO
> * choose XML (instead of odf)
> -> crash (log: http://pastebin.com/iyiSbTZa)

Seems this should be filed in new bug report.
Comment 7 James 2013-08-15 09:20:38 UTC
bfoman: done: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=68139

Not sure what's up with this bug here. Could you try reproducing with latest LO?
Comment 8 foss 2013-10-28 08:11:31 UTC
No feedback for 2 months. Setting to NEEDINFO.
Comment 9 Jean-Baptiste Faure 2014-01-02 19:01:49 UTC
Could some MS-Office / MS-Windows user explain how MS-Office's locking file system works? 
In the case of LibreOffice the name of the current user is filed in the lock file (.~lock.<filename>#).


Best regards. JBF
Comment 10 bfoman 2014-01-02 21:31:27 UTC
(In reply to comment #9)
> Could some MS-Office / MS-Windows user explain how MS-Office's locking file
> system works? 
> In the case of LibreOffice the name of the current user is filed in the lock
> file (.~lock.<filename>#).

The same is for MS Office - you can find user data in the lock file ~$filename.
Comment 11 Jean-Baptiste Faure 2014-05-11 18:02:45 UTC
Thank you for the answer and sorry for taking it into account so late.
Can't test with MSO, so set status back to unconfirmed.

Best regards. JBF
Comment 12 Jean-Baptiste Faure 2014-05-11 18:04:43 UTC
set back importance and priority to default values because comment #4 is another bug.

Best regards. JBF
Comment 13 Jean-Baptiste Faure 2014-07-20 19:34:15 UTC
Sorry, my bad, the status of this bug report shouldn't be unconfirmed but new or needinfo. As the question in comment #7 has not been answered I set the status back to needinfo.

Best regards. JBF


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.