Summary: | LibreOffice won't start when there is an unreachable file in "recent documents" list | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | roethig_j |
Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | ilmari.lauhakangas, mongolie2006-freedesktop, stephanv778 |
Priority: | medium | ||
Version: | 7.2.0.4 release | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=145607 | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 104742 |
Description
roethig_j
2021-09-17 07:26:02 UTC
we have been waiting for a solution for so long ... *** Bug 145623 has been marked as a duplicate of this bug. *** I confirm this extremely annoying bug for LibreOffice 7.2.2.2 on Fedora workstation. Even rebooting the computer doesn't help. But if, the network being available, I close LibreOffice, reopen it without opening a file through the network, close LibreOffice again, unplug from the network and then reopen Libreoffice again, then it works, until I go to "Recent documents". For the moment my workaround is removing "Recent files" from menu. You can do this one for all this way: tools → options → LibreOffice → Advanced → Open Expert Configuration. Then search for "PickListSize" (or go to org.openoffice.Office.Common → History → PickListSize). This is the number of recent documents to remember. Set it to 0. This bug is very similar to old bug #96215 of LibreOffice 5. On my Windows 10 it doesn't "hang" like described but just needs about a minute to start. In my opinion it is bad practice to check the existence of the files of recent documents category on startup. I can confirm this on openSUSE Tumbleweed: Version: 7.2.3.1 / LibreOffice Community Build ID: 20(Build:1) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded Bug 131850 was fixed. The fix went into the versions 7.4.0, 7.3.0.0.beta2 and 7.2.5. Could you re-test with a new version? 7.2.5 will be released soon: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.5_release Dear roethig_j, 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 |