Bug 97132 - Cell Contents Do Not Update for Screen Display (Screen Scrolling Needed)
Summary: Cell Contents Do Not Update for Screen Display (Screen Scrolling Needed)
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.0.2 rc
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2016-01-14 12:38 UTC by Kevin Suo
Modified: 2016-03-10 23:50 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Suo 2016-01-14 12:38:18 UTC 
Steps to Reproduce:
1. Type in anything in A1, hit ENTER.
--> Contents in A1 disappear.
2. Scroll your Calc screen.
--> Contents in A1 appear again.

Version: 5.1.0.2 (x64)
Build ID: ecd3574d51754b043f865cf5bafee286d24db7cc
CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; 
Locale: zh-CN (zh_CN)
Win 10 X64.

I set version to master because at this moment there is no 5.1.0.2 in version list.
Bug exists in both zh-CN and en-US locale.

P.S.: I am using parallel install (msiexec /a LibreOffice_5.1.0.2_Win_x64.msi, see https://wiki.documentfoundation.org/Installing_in_parallel/Windows)

Works OK in version 5.1.0.1, so this is a regression.
Comment 1 Kevin Suo 2016-01-14 12:51:36 UTC 
A further investigation suggests this may be related to fonts:
My default westen font for cells is Arial, and default Chinese font is Microsoft Yahei.

1. Type in anything in A1, hit ENTER.
--> Contents disappear.

2. Type anythin in A2 and A3, hit ENTER
--> Contents disappear.

3. Explicitly set fonts of column A to Times New Roman, then type in anthing in any other cells.
--> Works OK.
Comment 2 Kevin Suo 2016-01-16 00:47:04 UTC 
Set version to 5.1.0.2 as this tag is now created.
Comment 3 Kevin Suo 2016-01-19 06:52:53 UTC 
Today I updated my Intel HD Graphic 3000 driver to version 9.17.10.4229 (through Windows Update), this bug behaviour (and also bug 97170) do not show up any more.

Mark as NOTOURBUG, and adding bug 97170 as see also.
Comment 4 Kevin Suo 2016-01-19 06:59:09 UTC 
(In reply to Kevin Suo from comment #3)
Sorry, my mistake. Bug 97170 still exists, the graphic driver update does not solve the issue in bug 97170. Remove from see also.
Comment 5 ChrisR 2016-03-08 18:00:16 UTC 
I encounter the same bug since the update to 5.1 on Win7x64 with Intel HD Graphics 3000 (IGP). Is it known what is causing this?
Comment 6 Kevin Suo 2016-03-09 00:27:48 UTC 
(In reply to ChrisR from comment #5)
Please do not change the version field, it should reflect the earlist version affected.
Please provide your Graphic driver version. Thanks.
Comment 7 ChrisR 2016-03-10 23:50:06 UTC 
(In reply to Kevin Suo from comment #6)
> Please do not change the version field, it should reflect the earlist
> version affected.
> Please provide your Graphic driver version. Thanks.
Sorry I taught the fields were for the own report not the whole thread. 
The Intel driver is v8.15.10.2827 (2012-07-31).