Bug 131575 - FILEOPEN: LO can't open generated XLSX (without docsProps) that MSO opens - opens if [content_types].xml caps changed
Summary: FILEOPEN: LO can't open generated XLSX (without docsProps) that MSO opens - o...
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Mike Kaganski
URL:
Whiteboard: target:24.8.0 target:24.2.0.0.beta2
Keywords: filter:xlsx
Depends on:
Blocks: XLSX-External-Generators
  Show dependency treegraph
 
Reported: 2020-03-25 15:09 UTC by patrice.marchand
Modified: 2024-02-01 12:41 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
File xlsx (65.08 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2020-03-25 15:10 UTC, patrice.marchand
Details
Same file after Excel 2010 RT (72.28 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2020-03-25 15:49 UTC, Xisco Faulí
Details

Note You need to log in before you can comment on or make changes to this bug.
Description patrice.marchand 2020-03-25 15:09:42 UTC
Description:
When opening this simple xlsx file with calc, it says that the file is corrupted. With excel, no problem to open it. When you save it in excel and you reopen the file in calc it'OK. Problem with different version of LO : 6.4.2 , 6.3.5, ...
Thans for help

Steps to Reproduce:
1.Open xlsx file
2.
3.

Actual Results:
Dialog box saus corrupt file

Expected Results:
Dialog box saus corrupt file


Reproducible: Always


User Profile Reset: No



Additional Info:
Bug on several versions of CALC
Comment 1 patrice.marchand 2020-03-25 15:10:21 UTC
Created attachment 158990 [details]
File xlsx
Comment 2 Xisco Faulí 2020-03-25 15:45:57 UTC
Reproduced in

Version: 7.0.0.0.alpha0+
Build ID: 9163755e9f64a0b1dd5f2090e0702c19e31c12c9
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Version: 5.2.0.0.alpha1+
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8)

Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Comment 3 Xisco Faulí 2020-03-25 15:48:45 UTC
Hello Patrice,
The issue goes away if I open it in MSO Excel 2010 and save it
Comment 4 Xisco Faulí 2020-03-25 15:49:16 UTC
Created attachment 158997 [details]
Same file after Excel 2010 RT
Comment 5 patrice.marchand 2020-03-25 15:56:56 UTC
Thanks for your answer
The problem is that the xlsx file is an automatic export from another software and users don't have Excel on their computers.
Thanks.
Comment 6 himajin100000 2020-03-25 16:34:57 UTC
when I change

[content_types].xml to [Content_Types].xml, the xlsx file can be opened.
Comment 7 himajin100000 2020-03-25 16:36:42 UTC
by the way, should we mark this bug as NOTOURBUG?
Comment 8 Xisco Faulí 2020-03-25 16:46:48 UTC
(In reply to patrice.marchand from comment #5)
> Thanks for your answer
> The problem is that the xlsx file is an automatic export from another
> software and users don't have Excel on their computers.
> Thanks.

Which software is it ?
To me, it seems the problem is in that software but otoh, Excel can import it without any problem as well... maybe we could do the same
Comment 9 himajin100000 2020-03-25 16:48:50 UTC Comment hidden (obsolete)
Comment 10 patrice.marchand 2020-03-26 07:14:55 UTC
Hi, 
The software is https://www.salviadeveloppement.fr/en/property-management/

We are a french administration, we have tried to deal with the company but they just answer us that it's only compatible with excel !

If possible, it could be nice to fix it.
Thanks a lot.

(In reply to Xisco Faulí from comment #8)
> (In reply to patrice.marchand from comment #5)
> > Thanks for your answer
> > The problem is that the xlsx file is an automatic export from another
> > software and users don't have Excel on their computers.
> > Thanks.
> 
> Which software is it ?
> To me, it seems the problem is in that software but otoh, Excel can import
> it without any problem as well... maybe we could do the same

Hi, 
The software is https://www.salviadeveloppement.fr/en/property-management/

We are a french administration, we have tried to deal with the company but they just answer us that it's only compatible with excel !

If possible, it could be nice to fix it.
Thanks a lot.
Comment 11 Timur 2020-03-26 08:31:38 UTC
Cause is that XLSX is not properly generated. docsProps folder is missing.
(In reply to himajin100000 from comment #6)
> when I change
> [content_types].xml to [Content_Types].xml, the xlsx file can be opened.
Good and strange.
And that makes it somewhat different to bug 122336 and bug 76115 where simple rezip helps.
Comment 12 Kevin Suo 2021-11-04 07:55:52 UTC
$ zipinfo ./Etat_des_sorties\ \(1\).xlsx 
Archive:  ./Etat_des_sorties (1).xlsx
Zip file size: 66643 bytes, number of entries: 7
-rw----     4.5 fat     1035 b- defN 20-Mar-13 10:48 [content_types].xml
-rw----     4.5 fat      472 b- defN 20-Mar-13 10:48 xl\workbook.xml
-rw----     4.5 fat    74869 b- defN 20-Mar-13 10:48 xl\sharedstrings.xml
-rw----     4.5 fat      660 b- defN 20-Mar-13 10:48 xl\_rels\workbook.xml.rels
-rw----     4.5 fat    13005 b- defN 20-Mar-13 10:48 xl\styles.xml
-rw----     4.5 fat   606898 b- defN 20-Mar-13 10:48 xl\worksheets\sheet1.xml
-rw----     4.5 fat      370 b- defN 20-Mar-13 10:48 _rels\.rels
7 files, 697309 bytes uncompressed, 65833 bytes compressed:  90.6%

This zip file uses backslashes as filename. Mark as duplicate of bug 76115.

As a workaround, just change the extension to .zip, unzip, go into the unzipped folder, zip it with your OS zip tool (the root dir for the zip should be where [content_types].xml lives), then change the extension back to .xlsx.

*** This bug has been marked as a duplicate of bug 76115 ***
Comment 13 Mike Kaganski 2023-12-14 08:55:10 UTC
Not a dupe of 76115, has its own problem.
Comment 14 Mike Kaganski 2023-12-14 10:47:59 UTC
https://gerrit.libreoffice.org/c/core/+/160761
Comment 15 Commit Notification 2023-12-14 14:21:56 UTC
Mike Kaganski committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/df6a8667e6dd8b710bfae4944915f6eeb4efb233

tdf#131575: in repair mode, match names ASCII case-insensitively

It will be available in 24.8.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.
Comment 16 Commit Notification 2023-12-20 08:37:21 UTC
Mike Kaganski committed a patch related to this issue.
It has been pushed to "libreoffice-24-2":

https://git.libreoffice.org/core/commit/54d0f21a3f31cb8a16d6c250d8943d3824ff1848

tdf#131575: in repair mode, match names ASCII case-insensitively

It will be available in 24.2.0.0.beta2.

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.
Comment 17 Commit Notification 2024-02-01 12:41:25 UTC
Xisco Fauli committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/f6083293f4de9ac9037066d51f0ad1ab6a420eda

tdf#131575: sc_subsequent_filters: Add unittest

It will be available in 24.8.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.