Bug 80982 - FILESAVE: Numbers with decimal places switch to displaying "###" after a save or autosave
Summary: FILESAVE: Numbers with decimal places switch to displaying "###" after a save...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2014-07-06 20:31 UTC by emefbee
Modified: 2015-04-01 14:51 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description emefbee 2014-07-06 20:31:06 UTC
Problem description: 

Numbers with decimal places switch to displaying "###" after a save or autosave. It can be corrected by using the menu of cell formatting and setting 1 decimal place there. It only stays so until next autosave.

When the displaying of those cells contents/results is OK, those cells also ignore a button that tells them to decrease the number of decimal places. But pressing a button to increase the number of decimal places suddenly makes them jump up to a single decimal place. This is in a sheet that has been copied via the sheet copy feature.

The cells in question have a simple equation "=H11/2", etc.

Steps to reproduce:
1. ....
2. ....
3. ....

Current behavior:
as above

Expected behavior:
spreadsheet software should NEVER EVER change the contents of the spreadsheet tables and properties willy nilly on its own.
Operating System: Ubuntu
Version: release
Comment 1 tommy27 2014-07-18 23:29:07 UTC
the 4.1.x version you are using is end-of-life
try upgrading to and tell if issue persists
Comment 2 Joel Madero 2014-07-19 01:19:30 UTC
Please at least provide the sample document. Marking as NEEDINFO.

Once you attach a sample document (and hopefully test against 4.2) - set the bug to UNCONFIRMED. Thanks
Comment 3 QA Administrators 2015-02-19 04:35:05 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

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

Warm Regards,
QA Team

Message generated on: 2015-02-18
Comment 4 QA Administrators 2015-04-01 14:51:47 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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

-- The LibreOffice QA Team This NEEDINFO Message was generated on: 2015-04-01

Warm Regards,
QA Team