Bug 142935 - Spinners don't spin in LibO 7.2 (KF5 VCL) breaking the extension manager (update checks do not complete and huge cpu usage)
Summary: Spinners don't spin in LibO 7.2 (KF5 VCL) breaking the extension manager (upd...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.2.0.0.beta1+
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-18 18:32 UTC by Callegar
Modified: 2022-05-03 11:17 UTC (History)
1 user (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 Callegar 2021-06-18 18:32:32 UTC
Description:
Pressing Check for Updates in the extension manager appears to be non working in 7.2 beta.
No update is found, even if updates exist and the little wheel that should indicate that the check is in progress does not spin.

Steps to Reproduce:
1. Open extension manager
2. Press check for updates

Actual Results:
The spinning indicator stalls, no info is provided whether updates exist or not.

Expected Results:
The dialog should work as in 7.1


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: StartModule
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 Callegar 2021-07-16 07:02:01 UTC
Probably the extension manager does actually work in LibO 7.2. The problem is that the spinners dedicated to showing that you need to wait while something is going on, including the one in the extension manager, do not spin in LibO 7.2 beta and RC 1 KDE.

This also happens for the spinner in the "Check for updates" window.
Comment 2 Marina Bakutina 2021-07-26 21:24:48 UTC
No repro
Version: 7.3.0.0.alpha0+ (x86) / LibreOffice Community
Build ID: 7458f19a254c799612795a0cddeb0910f71948d4
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 3 Callegar 2021-07-31 08:47:39 UTC
Issue is still present in 7.2.0.2. Please test with the KF5 (KDE) VCL, there is no issue with gtk3 (and I believe on non linux platforms).
Comment 4 Callegar 2021-08-13 05:24:03 UTC
Still present in 7.2.0.3 and will then likely be in 7.2.0 final.

Maybe related to the following output that you get on the terminal:

QObject::setParent: Cannot set parent, new parent is in a different thread
QObject::setParent: Cannot set parent, new parent is in a different thread
QObject::startTimer: Timers cannot be started from another thread
QObject::setParent: Cannot set parent, new parent is in a different thread
QObject::killTimer: Timers cannot be stopped from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::installEventFilter(): Cannot filter events for objects in a different thread.

The issue with this is that on certain actions you get the impression that some LibO task is frozen. For UI having visual elements indicating that processing is happening that to not work is unfortunately worse than not having them at all.
Comment 5 Callegar 2021-08-17 09:22:27 UTC
A side effect of this bug is that the extension update check does not complete.

The process hangs taking > 100% cpu until you force closed the window.

You see this not just because of the huge cpu usage, but also because in LibO 7.1 when the extension update check completes the "show all updates" tick box becomes checkable and this never happens on LibO 7.2.
Comment 6 Callegar 2021-08-28 05:57:15 UTC
Issue is still present in 7.2.1.1.  I wonder if someone could test on KF5 VCL so that the bug can be confirmed.
Comment 7 Callegar 2021-09-07 14:11:53 UTC
Tried on a completely different system - Manjaro ARM with the latest KDE updates.

LibO 7.2 with the KF5 VCL gives the same issue there.

I think that the issue should be confirmed as seen across different systems. Wonder if it must be seen cross-reporter to this aim.
Comment 8 Callegar 2021-09-11 09:39:54 UTC
Seems fixed in 7.2.1.2
Cannot say if something that got touched in that version may have affected the behavior because the bug logs at https://dev-builds.libreoffice.org/pre-releases/src/?C=M&O=D are empty files.
Comment 9 Xisco Faulí 2022-05-03 11:17:02 UTC
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.