Description: If you run libreoffice while some other window is open, covering most of the desktop; and if LO is trying to restore documents since it was killed unexpectedly last time; and if it fails in some of these restorations (especially more than one), you may find yourself in a situation where some mode dialogs/notices requiring your "Ok" click are opened _behind_ the dialog listing the files to be restored. And then - you're just waiting and waiting and nothing happens. Only if you move that dialog will you see the modal message - and even then it might be partially covered by the startup splash-screen with the progress bar, which is stuck while LO is waiting for your click. Annoying! This happens to me with: Version: 6.3.2.2 Build ID: 1:6.3.2-1 CPU threads: 4; OS: Linux 5.2; UI render: default; VCL: gtk3; Locale: he-IL (en_IL); UI-Language: en-US Calc: threaded Steps to Reproduce: See above. Actual Results: See above. Expected Results: See above. Reproducible: Sometimes User Profile Reset: No Additional Info:
I can't reproduce it in Version: 6.5.0.0.alpha0+ Build ID: b92293b3943423324064a8513c2e114d18817179 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded launching LibreOffice from commandline. Does it happen to you launching soffice from commandline ?
Ok, so, I can't manage to reproduce it _exactly_ like I describe. But - regardless of whether you started it from the command-line or not - if the focus changes to another app for some reason while the "/path/to/file.odt doesn't exist" modal dialog is up; and then you switch focus back - you'll get the dialog with the list of documents awaiting recovery, covering the dialog.
Dear Eyal Rozenberg, 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
(In reply to Eyal Rozenberg from comment #2) As far as I can tell, there has not been any traction regarding this issue.
As far as I can tell, there has not been any traction regarding this issue.