Crashed, Lost my work (!)

2 replies [Last post]
Last seen: 4 weeks 4 days ago
Joined: 12 Apr 2012
Posts: 4
I filed a bug report about this.

I’m running on OSX El Capitan. Today, I accidentally pressed CMD-Q (quit) which is right near CMD-W, and the application locked up in trying to save 4 documents, three of which were “UNTITLED 1”. After about 10 minutes, I had to Force Quit the application, as it was clear nothing was happening.

Upon restart, I selected Recovery mode which failed due to $(ARG1) being undefined for the three “UNTITLED 1” documents and proceeded to just open up three blank pages.

The first issue is a lack of confirm-on-quit dialog for OSX, which is a really obvious issue. But I won’t discuss that further.

Now, I had been working on this very long report all day and I’m completely beside myself that my work may have been obliterated. So, before I write anything more to the system, I want to know if there is a cache somewhere I can recover or if I am indeed screwed.

Any help would be appreciated.


Last seen: 4 weeks 4 days ago
Joined: 12 Apr 2012
Posts: 4
I did some poking around and
I did some poking around and was able to find these:

~/Library/Application Support/LibreOffice/4/user/temp/lu10952lki62.tmp

$ ls -al
total 992
drwx——— 13 faldrich staff 442 Apr 26 17:27 .
drwxr-xr-x 8 faldrich staff 272 Apr 26 17:30 ..
-rw———- 1 faldrich staff 0 Mar 29 14:08 lu10952lki7j.tmp
-rw-r—r— 1 faldrich staff 14378 Apr 13 12:07 lu10952lkibp.tmp
-rw-r—r— 1 faldrich staff 14434 Apr 14 15:21 lu10952lkicl.tmp
-rw-r—r— 1 faldrich staff 391112 Apr 26 16:04 lu10952lkifk.tmp
-rw-r—r— 1 faldrich staff 26924 Apr 26 17:24 lu10952lkihw.tmp
-rw———- 1 faldrich staff 752 Apr 26 17:27 lu10952lkii0.tmp
-rw———- 1 faldrich staff 456 Apr 26 17:27 lu10952lkii1.tmp
-rw———- 1 faldrich staff 456 Apr 26 17:27 lu10952lkii2.tmp
-rw———- 1 faldrich staff 485 Apr 26 17:27 lu10952lkii3.tmp
-rw———- 1 faldrich staff 0 Apr 26 17:27 lu10952lkii5.tmp
-rw———- 1 faldrich staff 36864 Apr 26 17:27 lu10952lkii7.tmp

I copied a couple of them over to *.odt files, opened and then I was able to recover my report. Whew!

I never ever want to experience that again. So I maintain the above scenario is a bug and should probably not have happened (1), but that (2) on OSX it would be extremely useful to have a confirm-on-quit dialog available. It’s not great that OSX designs Q and W this way, but it is what it is. For Mac users, this is a must have fix.

Any other suggestions, or if this is a known bug, please by all means post.


Last seen: 4 weeks 3 hours ago
Title: ★★★
Joined: 21 Mar 2013
Posts: 38
Forrie, I may be telling you
Forrie, I may be telling you the obvious, but use autosave, especially on critical documents. I have mine set to 5 minutes, so in case of a crash, most work I can ever lose is the last 5 Minutes worth, bad, but not as bad as losing a whole days work Wink
LO5.0.5.2 Windows 10 Home

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.