Bug 55536 - bad interpreted .rels file inside XLSX (slash in relative XLSX path!!) critical !!
Summary: bad interpreted .rels file inside XLSX (slash in relative XLSX path!!) critic...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-10-02 12:59 UTC by Martin
Modified: 2015-02-11 19:51 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2012-10-02 12:59:37 UTC
After inziping XLSX, in the _rels folder, you'll find the .rels XML file. In it, you'll find
somewhere with the Target tag, and the contents is "/docProps/core.xml".
This is the problem. LibreOffice can only accept the Target tag with a value
of "docProps/core.xml". Note the first slash character.

If you remove the starting slash character, then re-zip the whole thing,
rename as XLSX, LibreOffice opens it fine.

Fix "docProps/app.xml" and "docProps/custom.xml" and "/docProps/app.xml" and "/docProps/custom.xml" must do the same!

Funnily, LibreOffice accepts "/xl/workbook.xml" for the workbook part. So I dont know why dont accept slash before "docProps/app.xml" and "docProps/custom.xml".
Comment 1 Markus Mohrhard 2012-10-03 14:43:52 UTC
This is far from being a critical or even a blocker bug.

While it is annoying it seems that your file is not created by MS Excel.
Comment 2 Martin 2012-10-03 17:56:25 UTC
This file IS NOT generated by Excel but it is generated by OpenDocument SDK from Microsoft (.NET library for generating XLSX files)
Comment 3 QA Administrators 2015-01-05 17:51:58 UTC
** 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 (4.3.5 or later): 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)

Thank you for your help!

-- The LibreOffice QA Team
Comment 4 Buovjaga 2015-01-20 16:01:40 UTC
Martin: is this still a problem for you? If yes, attach an example file as this has not been confirmed by QA yet.
Comment 5 QA Administrators 2015-02-11 19:51:49 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 

Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-02-11