Bug 88022 - FILEOPEN: Once opened (even after closed or or saved as), initial .xls (MSO 2003 XML inside) kept open until LO exits
Summary: FILEOPEN: Once opened (even after closed or or saved as), initial .xls (MSO 2...
Status: RESOLVED DUPLICATE of bug 87751
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.0.1 rc
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-04 15:07 UTC by Anton Derbenev
Modified: 2015-01-05 11:10 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Derbenev 2015-01-04 15:07:59 UTC
When an document is open, corresponding file kept open. This is normal.
But lock should be removed and file closed when document is closed. Currently it's not happening.

Prepare 1.xls: create new spreadsheet, save it as Microsoft Office 2003 XML (.xml). You can keep .xml extension or change to .xls for easier opening (because of registry association). Close the file. I'll refer it as 1.xls in following examples.

Case 1:
1. Open 1.xls with LibreOffice.
2. Close document (Ctrl+W), but don't close LibreOffice.
3. Try to do something with the file (outside of LO), you'll fail. Check opened file descriptiors for LO (handles.exe or procexp.exe), you'll see that LO, despite file isn't open anymore, keeps it opened on system level.

Case 2:
1. Open 1.xls with LibreOffice.
2. Save it as 2.xml (or anything else)
3. Check as before. You'll see that 1.xls kept open / locked.
4. Close document (Ctrl+W), but don't close LibreOffice. 1.xls sill kept open, though 2.xml is properly closed.

Note that .lock files created and removed appropriately, despite file itself kept open.
Comment 1 raal 2015-01-04 19:34:54 UTC
Hello,

Thank you for reporting the bug. Can you see if bug 87751 is similar to your problem so that I can mark your report as a duplicate of it? (Later bugs are generally marked as duplicates of earlier bugs).
Comment 2 Anton Derbenev 2015-01-05 11:10:09 UTC
@raal err, yep, sorry. I searched for duplicates, but haven't found that one.

*** This bug has been marked as a duplicate of bug 87751 ***