Bug 100230 - FILEOPEN: excel 2003 xml file is locked after close document
Summary: FILEOPEN: excel 2003 xml file is locked after close document
Status: RESOLVED DUPLICATE of bug 63995
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.0.3 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-05 20:51 UTC by Falcon
Modified: 2016-06-13 11:57 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Falcon 2016-06-05 20:51:27 UTC 
Steps:
0. Calc is not running.
1. Open any excel 2003 xml file (for example 1.xml).
2. Open any ods file (for example 1.ods). (do not close 1.xml!).
3. Close 1.xml (do not close 1.ods!).
4. Open 1.xml - you get message "Document file '1.xml' is locked for editing by ..."

Result: excel 2003 xml file is read only after close and open.

This is reproduced in 100% attempts for me.

(win7/win8.1 + LO 5.1.3.2 and win7 + LO 4.4.0.3)

Also this bug is reproduced in Open Office Calc 4.1.2: https://bz.apache.org/ooo/show_bug.cgi?id=126986
Comment 1 Buovjaga 2016-06-10 09:45:51 UTC 
Not reproduced. Maybe I need to test on Windows later.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.3.0.0.alpha0+
Build ID: 2d2a33934ecb952433a635ce5dab76cb2837b8a0
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on June 9th 2016
Comment 2 Buovjaga 2016-06-13 11:56:17 UTC 
Repro.

Win 7 Pro 64-bit, Version: 5.1.3.2 (x64)
Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: fi-FI (fi_FI)

Version: 5.3.0.0.alpha0+ (x64)
Build ID: f536a83d51443d19dba58157cea28fb67a090e02
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2016-06-13_01:19:21
Locale: fi-FI (fi_FI)
Comment 3 Buovjaga 2016-06-13 11:57:27 UTC 

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