Bug 121496 - FILESAVE save as 2003 xml fails
Summary: FILESAVE save as 2003 xml fails
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: MSO-XML2003
  Show dependency treegraph
 
Reported: 2018-11-18 19:26 UTC by raal
Modified: 2026-05-19 03:14 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
file (76.00 KB, application/vnd.ms-excel)
2018-11-18 19:29 UTC, raal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description raal 2018-11-18 19:26:52 UTC
Description:
export error when exporting to 2003 XML format

Steps to Reproduce:
1. open attached file "budget.xls"
2.File -export - Microsoft excel 2003 XML

Actual Results:
error

Expected Results:
file is exported


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 raal 2018-11-18 19:29:00 UTC
Created attachment 146725 [details]
file
Comment 2 m_a_riosv 2018-11-19 01:58:09 UTC
Maybe a dup of https://bugs.documentfoundation.org/show_bug.cgi?id=68752
Comment 3 Timur 2018-11-21 14:21:18 UTC Comment hidden (obsolete)
Comment 4 raal 2018-11-21 15:40:45 UTC
(In reply to Timur from comment #3)
> Could be a dupe. There are empty rows in first 3 sheets.
> 
> *** This bug has been marked as a duplicate of bug 68752 ***

Hi Timur, I'm not sure, because in my case LO doesn't crash. But tester has Mac, maybe it crash only on MAc
Comment 5 Timur 2018-11-22 15:31:44 UTC Comment hidden (obsolete)
Comment 6 Timur 2022-08-01 12:23:51 UTC
Repro 7.1 and 7.
Comment 7 raal 2024-05-18 06:47:25 UTC
Still reproducible in Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 6d5d9eaa61505cebaf3bde4bfc157d8e19fec8de
CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded Jumbo
Comment 8 QA Administrators 2026-05-19 03:14:22 UTC
Dear raal,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug