Bug 91257 - Cells show wrong numbers
Summary: Cells show wrong numbers
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.3.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-13 10:21 UTC by q12w
Modified: 2018-06-28 05:57 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
File with a bug (29.22 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-05-13 10:21 UTC, q12w
Details
Example where to find this problem (20.27 KB, image/png)
2015-05-13 10:21 UTC, q12w
Details
Cell format (88.28 KB, image/png)
2018-06-12 17:15 UTC, raal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description q12w 2015-05-13 10:21:04 UTC
Created attachment 115555 [details]
File with a bug

In file (see attachment test.ods) created and edited with LibreOffice we found a bug with cells content when you double click it.
Comment 1 q12w 2015-05-13 10:21:54 UTC
Created attachment 115556 [details]
Example where to find this problem
Comment 2 raal 2015-05-13 11:16:19 UTC
I can confirm with LO 4.4.3, win7
Are you able to reproduce the bug with new file?
Comment 3 q12w 2015-05-13 11:30:16 UTC
No. This file was earlier created with Ctrl+C and Ctrl+V from another program. And now copying from that program is correct.
Comment 4 GerardF 2015-05-13 14:14:39 UTC
Have a look at Format > Cell for each individual cells.
Ctrl + M fixes the problem.

Copy/paste from another program (what program) paste weird formatting.
Paste special would have worked I presume.
Comment 5 QA Administrators 2016-09-20 09:42:24 UTC Comment hidden (obsolete)
Comment 6 raal 2018-06-12 17:15:05 UTC
Created attachment 142683 [details]
Cell format

The cells are formated as strings, so no bug in LO when show the values. Maybe a bug when copy/paste the content. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem.
Comment 7 q12w 2018-06-28 05:57:17 UTC
I suppose this bug is not a bug. So let's close it.