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.
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)
[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
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.
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?
*** Bug 64391 has been marked as a duplicate of this bug. ***
(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.
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?
No feedback for 2 months. Setting to NEEDINFO.
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
(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.
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
set back importance and priority to default values because comment #4 is another bug. Best regards. JBF
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
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Message generated on: 2015-02-18
I tried today with LibreOffice 4.4 (Windows) and Excel 2000 : the bug is still present. LibreOffice tell me that the file in locked by "Unknow user"
I also still have the problem with LibO 4.4
Created attachment 113729 [details] File opened by another user ("unknown") If I open the same document with Excell I see the name of the user
(In reply to Marco A. from comment #17) > Created attachment 113729 [details] > File opened by another user ("unknown") > > If I open the same document with Excell I see the name of the user It seems there was recently a commit that fixed this (bug 67534). I was said "It will be available in 4.4.1." Marco: 4.4.1 was released as stable. Can you please test with it? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED DUPLICATE of 67534, if the problem went away.
I try now, and still remain LibO: Versione: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Versione locale: it_IT Excel: Excel 2003 SP3
Sorry, I guess it was a different fix. I'll actually set this to NEW as Marco is an independent confirmer.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Still occurs in 5.1.3.2.
Do we really need to care for foreign lock files? This might be inconvenient, but trying to "support" alien locking schemes (that aren't standardized) could bring more problems possibly. E.g., stale lockfiles of other programs. And why limit with only MSO? Let's do it for all possible office suites (and not only office - we support DXF - let's consider AutoCAD lock files, too)!
https://gerrit.libreoffice.org/64496
The proposed patch allows to check MS Office lockfiles ("Owner Files" in MS terminology [1]) when a document appears locked, and report the user name from it instead of "unknown user". Please note that MS Excel (at least 2016) does *not* create owner files for XLS/XML documents, while it does that for XLSX documents; thus, it will be impossible to tell this information for those types of spreadsheets. OTOH, MS Word creates owner files for all types of tested documents (DOC/DOCX/RTF/ODT). [1] https://support.microsoft.com/en-us/help/211632/description-of-how-word-creates-temporary-files
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/607b80ca3cddc239a35580470944a438ce144fc8%5E%21 tdf#34171: check foreign lockfiles to tell who has locked document It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.