Bug 169577 - IMporting xls export
Summary: IMporting xls export
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.8.0.4 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-20 16:56 UTC by Craig Keefner
Modified: 2025-12-04 19:29 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
leads scan export from IAAPA trade show in Orlando in November 2025 (9.94 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2025-11-20 18:22 UTC, Craig Keefner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Keefner 2025-11-20 16:56:08 UTC
Description:
Trade show exports leads in latest strict ooxml format (ecma-376). LibreOffice (and also Google Drives) chokes on it and fails on the desktop. I have 25.8 LO on linux.

Oddly enought LibreViewer on my Android phone can view the xls just fine.

Actual Results:
LO sees as corrupt, tries to repair and then generates I/O error

Expected Results:
see the xls file


Reproducible: Always


User Profile Reset: No

Additional Info:
🔥 1. The new file uses “Strict OOXML” format (Excel 2013+ XML)

Most lead-scanner systems export using:

ECMA-376 Strict Open XML format

LibreOffice and Google Sheets struggle with “Strict” because:

LibreOffice still relies heavily on the Transitional OOXML standard

Google Sheets cannot reliably parse shared strings tables and extended properties

Older files (like your 2015 Excel export) used Excel 97–2003-compatible XML, which all platforms read easily.

🔥 2. The new file probably contains a very large sharedStrings.xml

Your 2025 sheet has 36 columns × ~1000 rows.
That can generate:

A huge shared string table

Long XML nodes

Repeated rich-text cell styling

Google Sheets is notorious for choking on XLSX files with large sharedStrings.xml maps.

The 2015 file is tiny, so it loads instantly.

🔥 3. The 2025 file contains “relationships” files that Sheets/LibreOffice ignore

Modern Excel exports include:

/xl/printerSettings/

/xl/drawings/vmlDrawing1.vml

/xl/styles.xml with extended fonts

/docProps/app.xml with custom properties

/xl/_rels/workbook.xml.rels

Google Sheets simply discards these and often errors.

Old file?
It had none of these.

🔥 4. The new file uses features not supported in LibreOffice or Google Sheets

Even if they aren’t visible to YOU, the exporting system may embed:

Custom cell formatting rules

“Hidden” metadata worksheets

Rich text XML within cells

Boolean flags for scanning devices

Date/Time stamps in OADate format

Unicode metadata from badges

These silently break non-Excel parsers.

Your 2015 file is simple text — no formatting, no metadata.

🔥 5. Google Sheets has a 10 MB internal processing limit for XLSX import

Even if the file is physically smaller than 10 MB, the XML expansion may exceed Google’s internal threshold.

A 1 MB XLSX can expand to >40 MB XML internally.

Your 2025 file has:

Many text fields

High repetition

XML-heavy lead system metadata

Your 2015 file is extremely lightweight.

🔥 6. EventLead / ExpoPass / Cvent / Aventri-style scanners export Excel using Microsoft's API

Their XLSX output expects Microsoft Excel, not compatibility tools.

LibreOffice reverse-engineers XLSX but does not fully support all XML rules (especially strict SAX-based parsing).
Comment 1 raal 2025-11-20 17:51:05 UTC
Please attach test file. Thank you.
Comment 2 Craig Keefner 2025-11-20 18:22:20 UTC
Created attachment 204149 [details]
leads scan export from IAAPA trade show in Orlando in November 2025
Comment 3 m_a_riosv 2025-11-20 23:15:16 UTC
Opens without any issue with:
Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 620(Build:0)
CPU threads: 16; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: threaded
Comment 4 Robert Großkopf 2025-11-21 10:35:32 UTC
Could open the attached file without any problem:

Version: 25.8.3.2 (X86_64)
Build ID: 8ca8d55c161d602844f5428fa4b58097424e324e
CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

Might be a problem of the packages of the Linux distribution. 

Please copy the Version Information from 
Help → About LibreOffice
Comment 5 Craig Keefner 2025-11-21 15:50:49 UTC
Running latest PopOS Linux on x86
LbreOffice -- 25.8.3.2 (x86_64)
Flatpak

Google Drive has same problem -- typical Microsoft....
Comment 6 Craig Keefner 2025-11-21 15:54:17 UTC
Apparently I am running the latest available
https://www.libreoffice.org/download/download-libreoffice

The LibreOffice Viewer on my Android Google Pixel 9a shows version 25.8.3.2

It works for some reason.

Craig
Comment 7 Robert Großkopf 2025-11-21 16:41:30 UTC
Why don't you do this:
Please copy the Version Information from 
Help → About LibreOffice
?

Have a look at the Build-ID. If it is a short Build-ID it will be a special package of you Linux system.

You have chosen for Hardware x86 (IA32). There are only packages for 64bit available for LibreOffice 25.8.0.4 or newer. So I change the entry.
Comment 8 Craig Keefner 2025-11-21 17:23:44 UTC
Version: 25.8.3.2 (X86_64) / LibreOffice Community
Build ID: 8ca8d55c161d602844f5428fa4b58097424e324e
CPU threads: 16; OS: Linux 6.17; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded
Comment 9 Robert Großkopf 2025-12-04 19:29:32 UTC
Craig answered to me per private mail.
As I understood: Problem is solved.
So I will set this one to WORKSFORME.