Description: I think the origin is that I had a temporary document open, which was in /tmp (opened from Thunderbird) when the system crashed, and naturally it is no longer there after reboot. Since then every time I open LibreOffice I'm greeted with a document recovery window that lists no files to be recovered. I can't open files directly when LibreOffice wasn't running already, because after dealing with this dialog the main window will always be the generic recent documents list. How can I get rid of this recovery window? The tips I found online: - Click on "Cancel" button -> no such button - Click on "Discard" button -> no such button - Find the item "RecoveryList" in registrymodifications.xcu -> no such item Actual Results: Document recovery window on every startup Expected Results: No document recovery window when there are no documents to be recovered Reproducible: Always User Profile Reset: No Additional Info: Please fill out this field.
Created attachment 194930 [details] recovery window
Have you tried backing up your user profile and starting with a fresh one? https://wiki.documentfoundation.org/UserProfile#Manual_procedure_(all_versions)
(In reply to Stéphane Guillou (stragu) from comment #2) > Have you tried backing up your user profile and starting with a fresh one? > https://wiki.documentfoundation.org/ > UserProfile#Manual_procedure_(all_versions) Removing the ~/.config/libreoffice directory did not fix the problem.
[Automated Action] NeedInfo-To-Unconfirmed
I also in recent month or so observe identical behavior. I am not certain if I had a crash with file from /tmp open to start with, but consequences are the same – LO always starts with an empty document recovery window. Removing .config/libreoffice did not change a thing. Version: 24.2.5.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 16; OS: Linux 6.9; UI render: Skia/Raster; VCL: x11 Locale: lv-LV (lv_LV.UTF-8); UI: en-US Debian package version: 4:24.2.5-1 Calc: threaded
Let's mark as "new" then.
Both reporters talked about a crash. That is important because there are different code paths that are followed when triggered by a crash verses when triggered by a timed autoRecovery. (I'm changing the version to unspecified since I doubt it really started in 24.2. But yes, there were significant changes to autoRecovery in 24.2, so it is possible.) I was able to reproduce a re-occuring dialog (I tested in 7.6) if I "X'd" out of the recovery dialog window and answered "no" to discarding the recovery info. But that makes perfect sense to me. HOWEVER Looking at the screenshot in comment 1, this is NOT the recovery dialog. It is simply an information dialog that occurs AS A CRASH IS HAPPENING. So if I understand this correctly, as the computer is starting up, it crashes. Since there are no files open yet (of course), the crash-information dialog is empty. That would also explain why RecoveryList doesn't exist, and why deleting the user profile doesn't "fix" anything. I assume that hitting OK must let LibreOffice start up normally at that point, or else our reporters would have stated that LO fails to work at all. I have no idea what next steps can be taken here. Since it is not user profile related, my guess would be something like a full hard drive, or some other non-LibreOffice issue with the hardware.
(In reply to almos from comment #0) > I can't open files directly when LibreOffice wasn't running already Is this a clue? I translate this to mean "I can't double-click on a file in my operating system's file manager and have it open in LO because the crash info dialog pops up". So, is the file you are trying to open causing LO to crash? (Although it sounds like you can open it without crashing using LO's File Open...) Nah, probably not a good clue. You say "when LO is not already running" so that suggests that it is simply the act of starting the LO program that is triggering the crash, and not the document itself. Do you get any useful output if you start LO from a terminal? (soffice)
(In reply to Justin L from comment #8) > (In reply to almos from comment #0) > > I can't open files directly when LibreOffice wasn't running already > Is this a clue? I translate this to mean "I can't double-click on a file in > my operating system's file manager and have it open in LO because the crash > info dialog pops up". > > So, is the file you are trying to open causing LO to crash? (Although it > sounds like you can open it without crashing using LO's File Open...) > > Nah, probably not a good clue. You say "when LO is not already running" so > that suggests that it is simply the act of starting the LO program that is > triggering the crash, and not the document itself. > > Do you get any useful output if you start LO from a terminal? (soffice) Okay, so this means that Libreoffice has a crash on startup, shows the crash recovery dialog, then starts normally. Weird. The KDE menu entry calls `libreoffice --calc %U`. When I try the same thing in a terminal it works fine. Weird.