使用ssconvert转换XLSX为CSV/TXT时断言失败的排查求助

Let's walk through how to diagnose and fix this issue with ssconvert failing on Office 2013 XLSX files. Those critical assertion errors usually point to either compatibility gaps between your ssconvert version and the XLSX format, or issues with the file itself. Here's what to check step by step:

1. Verify your ssconvert/Gnumeric version first #

Older versions of Gnumeric (the toolkit behind ssconvert) often lack full support for newer XLSX features introduced in Office 2013. Run this command to check your version:

ssconvert --version

If you're running a version older than 1.12.40 (as of 2024), updating is your best first step. Use your package manager to grab the latest stable release:

• For Debian/Ubuntu: sudo apt update && sudo apt install --only-upgrade gnumeric
• For Fedora/RHEL: sudo dnf update gnumeric

2. Double-check your command syntax #

You might be mixing up import/export flags. Try explicitly specifying the XLSX import and CSV export modules with these commands:

# Try the ooxml import module
ssconvert -I Gnumeric_Excel:ooxml test.xlsx test.csv

# Or the excel_xml module if ooxml doesn't work
ssconvert -I Gnumeric_Excel:excel_xml test.xlsx test.csv

If your XLSX has multiple sheets, specify the sheet name explicitly to rule out issues with sheet handling:

ssconvert test.xlsx:"Sheet1" test.csv

3. Validate the XLSX file itself #

Office 2013 sometimes saves XLSX files with non-standard quirks that trip up ssconvert:

• Open the file in LibreOffice Calc or Google Sheets, then re-save it as a fresh XLSX. Try converting this re-saved file with ssconvert.
• Check if the file is encrypted. ssconvert doesn't support password-protected XLSX files—you'll need to remove encryption first.
• Ensure there are no corrupted cells, unusual formulas, or embedded objects (like macros) that might break parsing.

4. Enable debug logging for deeper insight #

To get more details about where the conversion is failing, run ssconvert with debug messages enabled:

G_MESSAGES_DEBUG=all ssconvert test.xlsx test.csv 2>&1 | tee conversion_log.txt

Look for lines that mention parsing errors, missing XML elements, or unsupported features in the XLSX structure. This can pinpoint exactly what's causing the assertion failures.

5. Use a fallback tool if needed #

If ssconvert still won't cooperate, use LibreOffice's headless mode as a reliable alternative for conversion:

libreoffice --headless --convert-to csv test.xlsx

This will generate test.csv in the same directory, and it handles most Office 2013 XLSX files flawlessly.

内容的提问来源于stack exchange，提问作者Alan MacNeill