Bug 103023 - When editing a cell, the leading character of that cell becomes corrupted.
Summary: When editing a cell, the leading character of that cell becomes corrupted.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-05 18:15 UTC by dlwhite67
Modified: 2017-05-31 10:47 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Calc w/ corrupted cell (131.56 KB, image/png)
2016-10-08 19:26 UTC, dlwhite67
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dlwhite67 2016-10-05 18:15:33 UTC
Description:
This IPv4 address appears correctly: 2001:0DB8:5F73:0008::/61

When I edit that cell to simplify the address to 2001:DB8:5F73:8::/61 the leading "2" character becomes corrupted and it appears as if a "3" is transposed on top of the "2."

I am using the Liberation Sans 10 point font. If I change to the DejaVu Sans 10 font, all characters are rendered correctly.


Steps to Reproduce:
1.Type 2001:0DB8:5F73:0008::/61 into a cell,
2.Simplify that address by removing the leading zeros "2001:DB8:5F73:8::/61",
3.The first character will become corrupted.

Actual Results:  
See above

Expected Results:
Characters should not become corrupted, after editing the contents of a cell.


Reproducible: Always

User Profile Reset: No

Additional Info:
I have seen this bug in other contexts (other text), on previous Libre Office versions and on other machines, but I never had the motivation to report it. I merely changed the font and moved on.


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.148 Safari/537.36 Vivaldi/1.4.589.38
Comment 1 Jean-Baptiste Faure 2016-10-06 19:29:01 UTC
Not reproducible with master under Ubuntu 16.04 x86-64.

Please, could you attach a screencopy?

Best regards. JBF
Comment 2 dlwhite67 2016-10-08 19:26:23 UTC
Created attachment 127881 [details]
Calc w/ corrupted cell
Comment 3 dlwhite67 2016-10-08 19:37:46 UTC
Attached, please find an example of the corrupted cell.

I copied and pasted the contents of cell J152 to J154.

At this stage, everything renders correctly in J154.

I edited J154 to simplify the IPv6 address (deleted the leading zeros).

The first character of J154 is now corrupted. It should be a "2," but it looks like a "3" is transposed over top of it.

Both cells are identically formatted and the font is Liberation Sans 10.

If I merge cell J154 with J155, the corrupted rendering does not change.

If I change the font of J154 to Deja Vu (or some others), the cell contents render correctly.
Comment 4 Aron Budea 2016-10-09 12:06:27 UTC
I wonder if this is related to the emoji autocorrect bug (bug 97191). That would cause :8: to be replaced with a clock symbol, which can't be seen in the screenshot, so I'm wondering if that's causing the visual corruption (since :8: is removed from the simplified address).

Can you go to Tools -> Autocorrect Options..., then Options tab, uncheck Use replacement table, and try again?
Comment 5 QA Administrators 2017-05-02 11:37:33 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2017-05-31 10:47:09 UTC
Dear Bug Submitter,

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-20170531