Bug 139707 - Calc loses spreadsheet rows when creating .xlsx file from .CSV file containing CR (ascii=13) character. Creating plain .xls file works properly.
Summary: Calc loses spreadsheet rows when creating .xlsx file from .CSV file containin...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-17 17:04 UTC by teccardt
Modified: 2021-12-09 04:30 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
This CSV file causes the problem (1.52 KB, text/csv)
2021-01-17 18:06 UTC, teccardt
Details
file saved as xslx with LO 7.1.4.0.0+ (6.81 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2021-05-10 20:07 UTC, Jean-Baptiste Faure
Details

Note You need to log in before you can comment on or make changes to this bug.
Description teccardt 2021-01-17 17:04:15 UTC
Description:
I lost a lot of by-hand-input data when I created an XLSX file, starting from a CSV file, and adding a few columns.

Subsequent experimentation showed that this loss was not caused by additional data,  but Calc will not save ANY data when a CSV file with CR char is used.  For some reason, saving to plain XLS file works.

Steps to Reproduce:
1. Create a CSV file with an asci=13 (CR) character in one text cell (within quotes)
2. Click on it to open it with Libreoffice CALc
3. Notice that file looks okay in LibreOffice (contains data from CSV file)
4. Save file as a XLSX file.
5. Click on XLSX file and notice that all data after the line with the CR character is gone.
6. Now try same procedure, but saving as an XLS file.  This works correctly.

Actual Results:
XLSX file is missing all data after the CR (ascii=13) character

Expected Results:
XLSX should look like XLS file


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 5.1.6.2
Build ID: 1:5.1.6~rc2-0ubuntu1~xenial10
CPU Threads: 4; OS Version: Linux 4.15; UI Render: default; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 1 teccardt 2021-01-17 18:06:54 UTC
Created attachment 168955 [details]
This CSV file causes the problem

The attached file has a non-print character in the 12th position that causes the problem.
Comment 2 Jean-Baptiste Faure 2021-05-10 20:07:10 UTC
Created attachment 171836 [details]
file saved as xslx with LO 7.1.4.0.0+

Not reproducible for me with LibreOffice 7.1.4.0.0+ built at home under Ubuntu 18.04 x86-64. See attached xslx file.

Best regards. JBF
Comment 3 Jean-Baptiste Faure 2021-05-10 20:09:13 UTC
I see that you use a very old version of LibreOffice. Please, could you try an recent one?

Status has been set to NEEDINFO, please set it back to UNCONFIRMED once requested information has been provided.

Best regards. JBF
Comment 4 QA Administrators 2021-11-08 04:08:39 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-12-09 04:30:52 UTC
Dear teccardt,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp