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
Created attachment 179155 [details] Uninitialised form (v7.3.1.3) This is the C4U form after installing v7313
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.
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.
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.
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
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.
*** Bug 157812 has been marked as a duplicate of this bug. ***
Also happens on macOS according to duplicate bug 157812.
I confirm it has been always happening on Mac OS too.
Dear Dutch, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug