Bug 165825 - double click into the cell - text invisible
Summary: double click into the cell - text invisible
Status: RESOLVED DUPLICATE of bug 165621
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
25.8.0.0 alpha0+
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2025-03-19 18:29 UTC by raal
Modified: 2025-03-19 18:47 UTC (History)
3 users (show)

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 raal 2025-03-19 18:29:30 UTC 
Description:



Steps to Reproduce:
1.open new Calc file
2.insert text into cell 
3.press Enter - text is visible
4.double click into the cell

Actual Results:
text is not visible. Cursor is in the cell

Expected Results:
text is visible


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ddaea18557b1ec60d9e360f9eab539c8f551061f
CPU threads: 4; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded
Comment 1 raal 2025-03-19 18:31:04 UTC 
This seems to have begun at the below commit in bibisect repository/OS linux-64-25.8.
Adding Cc: to Armin Le Grand ; Could you possibly take a look at this one?
Thanks
 5b49816630d227360233914789b558e0b5bedeee is the first bad commit
commit 5b49816630d227360233914789b558e0b5bedeee
Author: Jenkins Build User <tdf@maggie.tdf>
Date:   Tue Mar 4 00:06:04 2025 +0100

    source 9b4dac8bf180f3fd5441b447a60439fb258854d4
    
    source 9b4dac8bf180f3fd5441b447a60439fb258854d4
    source 897d70c1f710c88f9c321cf72af739b21de427ca

181904: Avoid short blinking of text when activating TextEdit | https://gerrit.libreoffice.org/c/core/+/181904
Comment 2 Buovjaga 2025-03-19 18:47:22 UTC 
Already fixed.

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