Bug 148231 - First Check For Updates creates dummy form
Summary: First Check For Updates creates dummy form
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.2.2 release
Hardware: x86-64 (AMD64) All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 157812 (view as bug list)
Depends on:
Blocks: Updates
  Show dependency treegraph
 
Reported: 2022-03-28 07:33 UTC by Dutch
Modified: 2023-10-19 07:46 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Uninitialised form (v7.3.1.3) (255.26 KB, image/png)
2022-03-28 07:34 UTC, Dutch
Details
Uninitialised form (v7.1.x) (11.57 KB, image/png)
2022-03-28 07:36 UTC, Dutch
Details
Uninitialised form (v7.3.2.2) (241.91 KB, image/png)
2022-04-08 07:11 UTC, Dutch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dutch 2022-03-28 07:33:09 UTC
Description:
When starting Check For Updates for the first time from the main LibreOffice application started from Win10 desktop shortcut, a form pops up that is garbled with uninitialised controls, and does nothing. The second attempt works as advertised. This is a recurring problem I noted to affect LO at least since 7.1.x.

Steps to Reproduce:
1.Start LO from the Windows desktop shortcut
2.Click Help
3.Click Check For Updates...

Actual Results:
A form pops up with uninitialised controls, with overlap, no Check For Updates is actually performed. Only option is to close the form.

Expected Results:
The form shall produce output consistent with checking for updates (check, info, review...).


Reproducible: Always


User Profile Reset: No



Additional Info:
This occurs consistent every time, the first check always gives the non-working form after which the Check For Updates appears to work normally, even after a restart of the LO application from the Windows desktop shortcut.

Version: 7.3.1.3 (x64) / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded
Comment 1 Dutch 2022-03-28 07:34:31 UTC
Created attachment 179155 [details]
Uninitialised form (v7.3.1.3)

This is the C4U form after installing v7313
Comment 2 Dutch 2022-03-28 07:36:22 UTC
Created attachment 179156 [details]
Uninitialised form (v7.1.x)

This is from LO 7.1.x, captured just minutes before installing v7.3.1.3.
Comment 3 Dutch 2022-03-28 07:39:34 UTC
The unititialised form seems to generate only once in a Windows user session. After a reboot or logoff/logon the form is generated rather consistently, every second attempt works as advertised, even when closing/restarting the LO application.
Comment 4 Dutch 2022-04-08 07:11:29 UTC
Created attachment 179401 [details]
Uninitialised form (v7.3.2.2)

Just installed v7.3.2.2 over v7.3.1.3 and again I get the faulty Check For Updates screen. It seems that this faulty form appears right after the installation, any next activation appears to work correctly.
Comment 5 csyu.279 2023-01-28 23:50:48 UTC
The very first time I ran Check for Updates in version 7.4.4.2, I got the window shown in Dutch's attachments. But the next time I ran Check for Updates in 7.4.4.2 and 7.5.0.0 builds, Check for Updates ran fine. 

Version: 7.4.4.2 (x64) / LibreOffice Community
Build ID: 85569322deea74ec9134968a29af2df5663baa21
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 5a1f41a0d3aab15c113651f2edc9d4137ae99063
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 6 Buovjaga 2023-01-30 14:02:09 UTC
NEW per comment 5.

I notice earlier reports like bug 121909. Comments in bug 50421 also talk about first launch and it had some duplicates saying the same.
Comment 7 Stéphane Guillou (stragu) 2023-10-18 11:29:52 UTC
*** Bug 157812 has been marked as a duplicate of this bug. ***
Comment 8 Stéphane Guillou (stragu) 2023-10-18 11:30:42 UTC
Also happens on macOS according to duplicate bug 157812.
Comment 9 Fabio 2023-10-19 07:46:17 UTC
I confirm it has been always happening on Mac OS too.