https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #19 from Luke Kendall ---
I think it's plausible that this is a duplicate of bug 99607, yes.
But please note the UI error noted in comments 10 and 11 - the text describes
actions that LO does not do. I think the text is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
Matthias Basler changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
Peter Steinbrueck changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
sdc.bla...@youmail.dk changed:
What|Removed |Added
Blocks||77999
--
You are receivin
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #17 from Luke Kendall ---
Thanks, Alex. Ubuntu's apport, when I tried to report the bug, said it
couldn't because various packages needed updating. I ran Synaptic, and 30 mins
later all was done, and I restarted just LO, not
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #16 from Alex ---
(In reply to Luke Kendall from comment #14)
> Aargh! Just lost an hour's work, since I was so absorbed in
> composition/writing. And of course, as usual, autosave, despite
> interrupting me regularly, had sa
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #15 from Luke Kendall ---
Yeah, took me between an hour and a half to two hours to recreate most of what
I had before the crash. (The difference between being in a "flow state", and
not.)
--
You are receiving this mail becau
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #14 from Luke Kendall ---
Aargh! Just lost an hour's work, since I was so absorbed in
composition/writing. And of course, as usual, autosave, despite interrupting
me regularly, had saved Nothing.
I don't understand why this
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #13 from Alex ---
(In reply to Luke Kendall from comment #12)
> Because the directory modification time seems to change at 10 min intervals,
> matching the auto-save times, my guess is that the file is saved and then
> immediat
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #12 from Luke Kendall ---
Just installed LO 5.1.1.2, along with a bunch of other updates for Ubuntu
16.04LTS (development).
I was re-opening 8 recent documents I'd been working on, and on about the 6th
LO just crashed.
But for
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
Beluga changed:
What|Removed |Added
Version|5.0.5.2 release |5.0.2.2 release
--
You are receiving th
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
Alex changed:
What|Removed |Added
Version|5.0.2.2 release |5.0.5.2 release
--
You are receiving this
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #11 from Luke Kendall ---
Created attachment 123020
--> https://bugs.documentfoundation.org/attachment.cgi?id=123020&action=edit
Screenshot of the auto-recovery "completion" dialogue
The promised screenshot showing the text
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #10 from Luke Kendall ---
Since my Linux system crashed while reporting this bug, I'm in position to note
that as expected, since the backup area was empty, none of the documents were
recovered from there.
But I would like to
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #9 from Luke Kendall ---
I've just done a little test, and I don't think so.
On the occasions when I have looked in the backup area, it is usually empty.
I just modified an open file; my auto-recovery backup interval is set t
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
Beluga changed:
What|Removed |Added
CC||todven...@suomi24.fi
--- Comment #8 from
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
Peter Steinbrueck changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #7 from Alex ---
Autosave does not work after you save an opened file.
If you open a file and work with it without saving, autosave function works and
backup file is created. If you save file and continue to work with it, backu
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #6 from Luke Kendall ---
FWIW, it happened again today. I closed a file, and LO (all documents being
edited) crashed. The document recovery process on this occasion, however,
recovered all documents except the important one,
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #5 from -pk- ---
I forgot to mention it was on Windows 7.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bug
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #4 from -pk- ---
I had a similar experience. After a crash, it said the document recovered in
the status bar, however it displayed error prompts and asked me to save it to
my documents. No document was saved or recovered. Autos
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #3 from Luke Kendall ---
Created attachment 120471
--> https://bugs.documentfoundation.org/attachment.cgi?id=120471&action=edit
Zip file of scree shots of the recovery process
As part of bug 95267 reporting, I had just selec
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #2 from Luke Kendall ---
Oh, I should add that a normal Save takes about 10 seconds; the autosave takes
the same length of time. (Even though there is no file in the backup area
afterwards.)
--
You are receiving this mail be
https://bugs.documentfoundation.org/show_bug.cgi?id=95591
--- Comment #1 from Luke Kendall ---
If it helps, I just observed the save progress bar on an autosave (at 17:04),
and checked - the directory is empty, but strangely, the directory itself was
modified:
$ ls -la ~/.config/libreoffice/4/us
24 matches
Mail list logo
