Bug 137977 - LibreOffice Writer changes Table values to 0
Summary: LibreOffice Writer changes Table values to 0
Status: RESOLVED DUPLICATE of bug 131025
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.6.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-04 03:57 UTC by najmun1111
Modified: 2021-10-29 14:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
the offending file with table contents turned into 0 (23.20 KB, application/vnd.oasis.opendocument.text)
2020-11-04 03:58 UTC, najmun1111
Details
Reproduced file where the text turned to 0 (22.31 KB, application/vnd.oasis.opendocument.text)
2020-11-04 04:24 UTC, najmun1111
Details
Another reproduced file, now with other formatting. (27.09 KB, application/vnd.oasis.opendocument.text)
2020-11-04 05:12 UTC, najmun1111
Details

Note You need to log in before you can comment on or make changes to this bug.
Description najmun1111 2020-11-04 03:57:27 UTC
Description:
I was creating a table with LibreOffice writer. I wrote it all down and saved, the next morning the texts in those tables turned to 0.

Steps to Reproduce:
1. Make a table
2. fill that table
3. save
4. open it again

Actual Results:
nothing

Expected Results:
NOTHING but the file that I have changed the texts in the table to 0


Reproducible: Couldn't Reproduce


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.4.6.2 (x64)
Build ID: 0ce51a4fd21bff07a5c061082cc82c5ed232f115
CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: GL; VCL: win; 
Locale: en-GB (en_GB); UI-Language: en-GB
Calc: CL
Comment 1 najmun1111 2020-11-04 03:58:43 UTC
Created attachment 166987 [details]
the offending file with table contents turned into 0
Comment 2 najmun1111 2020-11-04 04:18:35 UTC
I have been able to reproduce the bug now, uploading the reproduced file in a moment.
Comment 3 najmun1111 2020-11-04 04:20:56 UTC
Steps to Reproduce:
1. Make a table
2. fill that table
3. Choose a formatting
4. save
5. open it again

Actual Results:
The column filled with Text and Text with numbers had changed to 0

Expected Results:
The text should not turn into 0


Reproducible: Yes
Comment 4 najmun1111 2020-11-04 04:24:30 UTC
Created attachment 166988 [details]
Reproduced file where the text turned to 0

Originally it works fine until I changed the formatting of the table. When I do that, the contents of the table turned to 0 after saving, closing, and reopening it.

Included in the file is a screenshot as to how the table looked like before it was closed.
Comment 5 wingednova 2020-11-04 04:33:56 UTC
(In reply to najmun1111 from comment #4)
> Created attachment 166988 [details]
> Reproduced file where the text turned to 0
> 
> Originally it works fine until I changed the formatting of the table. When I
> do that, the contents of the table turned to 0 after saving, closing, and
> reopening it.
> 
> Included in the file is a screenshot as to how the table looked like before
> it was closed.

I've tried out all your steps:
1. Create a table in Writer,
2. Fill in cells with alphabetic strings, numeric strings, and alphanumeric strings,
3. Format the table,
4. Save and exit,
5. Reopen the file.

I'm able to retain all values on reopening. I tested out both your attachments, it works perfectly for me.

Perhaps you could specify which formatting you've used?
Comment 6 Mike Kaganski 2020-11-04 04:43:09 UTC
Likely a duplicate of bug 131025.
Comment 7 najmun1111 2020-11-04 05:12:15 UTC
Created attachment 166989 [details]
Another reproduced file, now with other formatting.

I used the Autoformat styles, and created my own and saved it there for the first two files.

But the result is still the same with other Autoformat styles like, Academic, Box List Blue, Elegant, & Simple Grid Rows.
Comment 8 Telesto 2020-11-04 13:46:36 UTC

*** This bug has been marked as a duplicate of bug 133611 ***
Comment 9 Buovjaga 2021-10-29 14:42:26 UTC

*** This bug has been marked as a duplicate of bug 131025 ***