Bug 145419 - The writing cursor disappears
Summary: The writing cursor disappears
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.2.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 145005 145420 146143 (view as bug list)
Depends on:
Blocks: KDE, KF5
  Show dependency treegraph
 
Reported: 2021-10-30 19:59 UTC by u.fuchs
Modified: 2022-08-01 03:55 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description u.fuchs 2021-10-30 19:59:13 UTC
Description:
Version: 7.2.2.2 / LibreOffice Community
Build ID: 20 (Build: 2)
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo + xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Ubuntu package version: 1: 7.2.2 ~ rc2-0ubuntu0.20.04.1 ~ lo1
Calc: threaded

The writing cursor disappears
Create text document. Write a short text and create a table. Write text in a field in the table. Highlight part of this text and change the font and / or size. The writing cursor can no longer be placed in the document and you can no longer write. Neither inside the table nor outside it. Briefly minimizing the program window eliminates the problem. This is an extremely annoying bug when you have to make extensive changes of this kind to the document.

Steps to Reproduce:
1.Briefly minimizing the program window eliminates the problem.
2.
3.

Actual Results:
Writing possible.

Expected Results:
Writing possible


Reproducible: Always


User Profile Reset: No



Additional Info:
no information
Comment 1 m_a_riosv 2021-10-30 20:15:01 UTC
*** Bug 145420 has been marked as a duplicate of this bug. ***
Comment 2 Buovjaga 2021-10-31 06:04:53 UTC
I can't reproduce this, but someone I know reported the same issue

Arch Linux 64-bit
Version: 7.2.2.2 / LibreOffice Community
Build ID: 20(Build:2)
CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: fi-FI
7.2.2-1
Calc: threaded
Comment 3 Buovjaga 2021-10-31 12:08:42 UTC
Now I could reproduce it, one has to try more than once. There is no need to create a table. The problem seems to be that the toolbar or sidebar fields keep the focus, but actually the focus is not in a working state even in the fields. However, I can not reproduce this with an unstable build. I tested on two different machines.

This only affects kf5 by the way, not gtk3 or gen.

u.fuchs: could you test with a daily master build from: https://dev-builds.libreoffice.org/daily/master/current.html

I guess Linux-rpm_deb-x86_64@tb87-TDF-dbg is the easiest to just unpack and run.

Arch Linux 64-bit
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 6678b8123c9952c80a637d3a7f4e27511122009e
CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 27 October 2021
Comment 4 Jan-Marek Glogowski 2021-10-31 13:38:29 UTC
FYI: my whole clusterfuck from bug 144585, which we reverted for 7.2.2, might be related. I guess 7.1.* might have similar problems. The whole thing is about popup and focus handling in Qt. I guess you both changed the font size via the combo box popup.

We didn't revert the changes stemming from bug 144585 on master and there is now  https://gerrit.libreoffice.org/c/core/+/124525 (and https://gerrit.libreoffice.org/c/core/+/124500)

Note that the mentioned bug 145363 is not directly related to the first patch, but the 2nd depends on it. Modal handling in Qt clashing with LO modal expectations is definitely an other problem area since a long time, resulting in quite a few bugs over time.
Comment 5 u.fuchs 2021-10-31 16:19:19 UTC
I tested it with the daily master build.

Version: 7.3.0.0.alpha1 + / LibreOffice Community
Build ID: c6af59b234e8eb8182dc7f686290524feafd6ed6
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo + xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

The problem does not arise here.

It is true with 7.2.2 the problem does not arise until the second change of font or font size. To get the cursor back you can also click on the menu.
Comment 6 Buovjaga 2021-11-05 15:44:10 UTC
(In reply to Jan-Marek Glogowski from comment #4)
> We didn't revert the changes stemming from bug 144585 on master and there is
> now  https://gerrit.libreoffice.org/c/core/+/124525 (and
> https://gerrit.libreoffice.org/c/core/+/124500)

Master continues to work fine after these. Let's close.

Arch Linux 64-bit
Version: 7.3.0.0.alpha1+ / LibreOffice Community
Build ID: ae0767b0fbe5d5b56ebe406bf1ee7aca4aaa909f
CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 5 November 2021
Comment 7 Christian (Fuchs) 2021-12-06 22:43:11 UTC
Version: LibreOffice 7.2.3.2 20(Build:2)
VCL: kf5 (cairo + xcb)
Locale: de-CH (de_CH.UTF-8); UI: de-CH
Source: libreoffice-7.2.3.2-1.fc35.src.rpm

Im able to reproduce this bug in  7.2.2 and 7.2.3 on fedora 35 boxes, 
only with kf5 as VCL and under X11. 

After changing font size or font a couple of times via the corresponding dropdown, the cursor disappears. 

This is fixable via various focus changes, e.g. by opening and closing a dialogue such as file open. 

If it was supposed to be fixed in 7.2.3, I'm afraid it is not.
Comment 8 Buovjaga 2021-12-07 07:58:28 UTC
(In reply to Christian (Fuchs) from comment #7)
> Version: LibreOffice 7.2.3.2 20(Build:2)
> VCL: kf5 (cairo + xcb)
> Locale: de-CH (de_CH.UTF-8); UI: de-CH
> Source: libreoffice-7.2.3.2-1.fc35.src.rpm
> 
> Im able to reproduce this bug in  7.2.2 and 7.2.3 on fedora 35 boxes, 
> only with kf5 as VCL and under X11. 
> 
> After changing font size or font a couple of times via the corresponding
> dropdown, the cursor disappears. 
> 
> This is fixable via various focus changes, e.g. by opening and closing a
> dialogue such as file open. 
> 
> If it was supposed to be fixed in 7.2.3, I'm afraid it is not.

No, the patches were not cherry picked to 7.2.x
Comment 9 Christian (Fuchs) 2021-12-10 00:26:31 UTC
(In reply to Buovjaga from comment #8)

> > If it was supposed to be fixed in 7.2.3, I'm afraid it is not.
> 
> No, the patches were not cherry picked to 7.2.x

Okay, thanks. What version will the fix be in? 
7.3 seems to be quite far away  (February, iirc) and this is the kind of bug that makes work very hard.
Comment 10 Buovjaga 2021-12-10 06:34:14 UTC
(In reply to Christian (Fuchs) from comment #9)
> (In reply to Buovjaga from comment #8)
> 
> > > If it was supposed to be fixed in 7.2.3, I'm afraid it is not.
> > 
> > No, the patches were not cherry picked to 7.2.x
> 
> Okay, thanks. What version will the fix be in? 
> 7.3 seems to be quite far away  (February, iirc) and this is the kind of bug
> that makes work very hard.

7.3
Comment 11 Jean-Baptiste Faure 2022-01-25 15:37:46 UTC
*** Bug 146143 has been marked as a duplicate of this bug. ***
Comment 12 Michael Weghorn 2022-08-01 03:55:34 UTC
*** Bug 145005 has been marked as a duplicate of this bug. ***