Bug 101311 - EDITING: Characters fade or get bold or print one on another - random crashes
Summary: EDITING: Characters fade or get bold or print one on another - random crashes
Status: RESOLVED DUPLICATE of bug 100925
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2016-08-04 23:02 UTC by Kai
Modified: 2016-08-06 20:06 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Screen Shots of "fading characters" (92.08 KB, application/pdf)
2016-08-04 23:02 UTC, Kai

Note You need to log in before you can comment on or make changes to this bug.
Description Kai 2016-08-04 23:02:07 UTC
Created attachment 126599 [details]
Screen Shots of "fading characters"

The problem described is related to a spreadsheet that has originally been created in Excel 2003 BUT is being used in *.ods format for a while without any problems. It should be mentioned, that the problem described does NOT appear in new spreadsheets generated in LO directly.

When entering or editing data in a cell, the characters either fade, become bold or sometimes are written one on another. When leaving the cell withe ENTER the data appear in a normal, readable way. When data have been written into a cell and need additional editing, there is no response, the data being written first remain as they are and there is now way to edit them. Pressing ESC leaves a empty cell.

Build-ID: 066b007f5ebcc236395c7d282ba488bca6720265
CPU-Threads: 4; BS-Version: Linux 4.4; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE.UTF-8)

OS = PCLinuxOS


Besides, sometimes LO crashes an logs me off. I do have to log-in again and to restart all applications. Unfortunately the circumstances when this phenomenon happens are not clear to me. Sometimes it happens when LO has been started and the computers remains with no action for a while (lets say 20 minutes) the next action in LO leads to the collapse.
Comment 1 Buovjaga 2016-08-06 20:06:43 UTC

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