Bug 32884 - recovery should differentiate between crashes and session restoring
Summary: recovery should differentiate between crashes and session restoring
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.4.4 release
Hardware: x86 (IA32) All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 113579 (view as bug list)
Depends on:
Blocks: AutoSave-AutoRecovery-Backup Document-Recovery
  Show dependency treegraph
 
Reported: 2011-01-06 15:09 UTC by Mark
Modified: 2019-02-28 10:49 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark 2011-01-06 15:09:56 UTC
At the moment LibreOffice what happens when LibreOffice was closed without all documents saved is something which was seemingly build for a crash recovery. I use Linux (KDE) which has the benefit of a session management. It restores all the documents which were open when the system was shut down (regulary). I wish that LibreOffice would handle this specific case better:
- If I am using session management, I do not want to answer any questions, which documents should be restored. It should just happen.
- It does not make sense to try and restore documents which were stored in the /tmp-folder since this will be deleted on reboot. So I do not need any message which tell me that restauration failed on those.
Comment 1 Matthieu Moy 2011-04-09 07:34:52 UTC
Even for people without session management, the document recovery for files in /tmp is a real pain.

I often use libreoffice to open attachements to my emails. My mailer makes a copy in /tmp and after that, libreoffice keeps complaining about document recovery failures on startup, for a file that was deleted long ago. I couldn't find a better way than "rm -fr ~/.libreoffice" to get rid of the document recovery failure message in this case.
Comment 2 Björn Michaelsen 2011-12-23 11:33:49 UTC Comment hidden (obsolete)
Comment 3 Mark 2012-07-14 06:42:56 UTC
Additionally Libreoffice should (optionally is best, I guess) not block the shutdown of the system and instead just store the session. Or it shut just block the session for a limited time asking the user I he wishes to save, meanwhile store the session anyway and if there is no reaction let the shutdown go its way without permanently blocking it.
Comment 4 libreoffice 2013-06-21 11:04:21 UTC
Bump, because this is still a problem with KDE.

Example of good behaviour: kwrite interrupts (and potentially cancels) the shutdown/logout if files need saving. It reloads saved files on session load.
Comment 5 Stefan 2016-04-07 10:09:21 UTC
Not 100% sure but I think I'm referring to this bug with a slightly different use case too.

Steps to reproduce:
(On Windows 7 SP1 (64-bit) - tested with LibreOffice 5.0.5 (64-bit)):
1. Create a new document (for instance a LibreOffice calc document).
2. Make some changes and save the file.
3. Without closing LibreOffice shutdown Windows.
4. Bootup Windows again.
5. Open the document you just created.

Actual result:
Libre Office brings up the Document recovery dialog.

Expected result:
Document is opened without bringing up the document recovery dialog (since everything was saved correctly).

From a users point of view it therefore looks as if the recovery function in libre office doesn't check whether anything in the recovery file wasn't saved in the real document and/or the recovery file isn't deleted, when LibreOffice is closed due to a Windows shutdown.
Comment 6 Buovjaga 2019-02-28 10:49:16 UTC
*** Bug 113579 has been marked as a duplicate of this bug. ***