Apparently the LibreOffice bug described in the previous posts is still
in operation on version 5.3. The other day, while I was working in a
document in LibreOffice 5.3 a split-second outage made my computer shut
down. The 'save auto-recovery information every' field was selected and
set at
However I also have to discard hardware problems or even viruses, no
matter how improbable be.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream]
This bug has returned to live. LibreOffice 4.2.8.2 Compilation Id.
420m0 (build:2), with autobackup active each 15 min. Running on Ubuntu
14.04 LTS. ext4 hard disk.
I opened a .doc, (previously created by LOW), made modifications (6 hour
session) while continuously saving (each 5 minutes or
A recovery option worked for me:
http://stackoverflow.com/questions/22542527/recovering-odt-file-using-
scalpel
Scalpel and foremost are forensic tools which can recover from any kind
of filesystem by greping all bytes on the disk. Works well for FAT USB
stick...
--
You received this bug
Cor reports some significant slowdowns at first-ever-start it seems
we're doing a load of fsyncs on that code-path (140 or so) - but it'd be
good to get some strace -ttt -f data from him on that.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I added Fix submitter as assignee because this will ease queries and bug
tracking.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved
Is there a chance that this will get an SRU for lucid?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document lost by power
This bug was fixed in the package libreoffice - 1:3.5.1-1ubuntu4
---
libreoffice (1:3.5.1-1ubuntu4) precise; urgency=low
* version bump for bug 930217
libreoffice (1:3.5.1-1ubuntu3) precise-proposed; urgency=low
* fix typo in control.in
libreoffice (1:3.5.1-1ubuntu2)
** Changed in: df-libreoffice
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice
I have my odt-files on a NAT system, which is accessed via NFS.
Today, my day was ruined because one odt-file which was open (by
LibreOffice 3.5.0rc3 on a debian Lenny system) when I shut down the
system yesterday was gone today without a trace. Thank god another odt-
file that was also open is
Michael Meeks committed a patch related to this issue.
It has been pushed to libreoffice-3-5:
http://cgit.freedesktop.org/libreoffice/core/commit/?id=c6e22c0fc0cc4ce1508f8401c4b0c14fc89df942g=libreoffice-3-5
fdo#40607 - osl_syncFile having written, and avoid doing that on start
It will be
Hi Robert, sorry to hear about your data loss:
I've been using OpenOffice 2.4 for several years with the same NAT, the same
NFS-setup, the same OS and the same odt-files - and I have never had dataloss.
It is worth pointing out that this (missing fsync) is -exactly- the same
in the OpenOffice
pushed fix to master.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document lost by power outage
(became 0 bytes long) -
Michael Meeks committed a patch related to this issue.
It has been pushed to master:
http://cgit.freedesktop.org/libreoffice/core/commit/?id=d3192948fe968fc4d6a8ec0e6fda232f265b3c4c
fdo#40607 - osl_syncFile having written, and avoid doing that on start
--
You received this bug notification
Hello Michael, thanks for your reply.
Please use fsync, even if it may cause some frozen GUI for a few
milliseconds, keeping your data safe should be priority to *everything
else*. And if only older Linux-systems are caught, even more so. (And I
say that as a debian-Lenny user. Older
** Changed in: libreoffice (Ubuntu)
Assignee: (unassigned) = Björn Michaelsen (bjoern-michaelsen)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream]
fix commited on upstream master and backported to 3-5:
http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-3-5id=c6e22c0fc0cc4ce1508f8401c4b0c14fc89df942
** Changed in: libreoffice (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are
backported to packaging with:
http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commitdiff;h=5384155d746ac839af7b3ff311d20f6c7e77bfad
(will be fixed in upstream 3.5.2)
** Changed in: libreoffice (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: libreoffice
Not sure when I could fit that in ... I'll see.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document lost by power outage
Doing a bit more code reading; it seems that the likeliest place to add
an osl_syncFile - or somesuch UNO call to either the ucb/ or package/
code is the SfxMedium code:
sfx2/source/doc/docfile.cxx (Transfer_Impl)
perhaps this, or hereabouts:
// copy the temporary storage into
Created attachment 55932
gdb trace of all the calls to close(2) when saving a document
Seems reasonable. I used gdb to find all the stacks that call close when
saving a file (in 3.4.4, since I didn't have time to build my own
package with symbols). There's a lot of calls (27), but most are very
A really useful trace - thanks for that ! :-) it seems that a load of
these are related to the flurry of /tmp files that we create (apparently
for no really good reason).
Re-running with:
diff --git a/sal/osl/unx/file.cxx b/sal/osl/unx/file.cxx
index aa6cc26..6b3c56c 100644
---
Using my own patch for a save I got:
Close on '/tmp/lu4uaci5.tmp/lu4uaci9.tmp'
Close on '/tmp/lu4uaci5.tmp/lu4uaci9.tmp'
Close on '/tmp/lu4uaci5.tmp/lu4uacia.tmp'
Close on '/tmp/lu4uaci5.tmp/lu4uacib.tmp'
Close on '/tmp/lu4uaci5.tmp/lu4uacib.tmp'
Close on '/tmp/lu4uaci5.tmp/lu4uacib.tmp'
Close on
Actually on second thought there is a simpler and more robust approach,
just run realpath() on the document file and then scan /etc/mtab for the
longest mount point that is a prefix of the document's path. That way
tmpfs and such can be detected correctly. That appears to be how df
works.
--
You
Created attachment 55617
Small utility to test if fsync() is desirable for a certain path
Here you go. Tested on ext3, ext4, tmpfs, none filesystems, procfs,
sysfs, and bind mounts, including mount points that are renamed after
they are mounted and mount points with whitespace in their paths. I
Created attachment 55644
sal fsync patch ...
Thanks Tristan ! you provoked me into doing something here, and thanks
for the tips. As you say it shouldn't be so hard. I attach a sample
patch to LibreOffice. The only real problem that remains (beyond
removing the debug), is to work out -which- of
Hi Tristan,
FYI, the parse_mounts in your patch won't work for paths containing
whitespace. The whitespace characters are translated into octal escape
sequences in the file. You'd be better off using setmntent and friends,
which handle that for you.
Doh - I should have read your code much
Created attachment 55708
Small utility to test if fsync() is desirable for a certain path
Discovered a small bug in my code, attaching a fixed version.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
FYI, the parse_mounts in your patch won't work for paths containing
whitespace. The whitespace characters are translated into octal escape
sequences in the file. You'd be better off using setmntent and friends,
which handle that for you.
--
You received this bug notification because you are a
Marking triaged.
@DonMick: please do not assign yourself to a bug's task unless you are
actively working on fixing it.
** Changed in: libreoffice (Ubuntu)
Status: Confirmed = Triaged
** Changed in: libreoffice (Ubuntu)
Assignee: DonMick (donmick) = (unassigned)
--
You received
Were you using the latest LibreOffice version?
The info says you were using LO 3.3.2.
Package: libreoffice-core 1:3.3.2-1ubuntu5
The latest Final release is 3.4.5 (libreoffice.org)
The latest in LP is 3.5.1.
I would recommend using 3.4.5 to avoid errors related to LO not calling
functions
--
@Evan See comment #26--I tested 3.5.0 Beta 2 too and it still repros.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice
@Tristan Oh. What about 3.4.5?
(That is the latest final release on their website)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved
** Changed in: libreoffice (Ubuntu)
Assignee: (unassigned) = DonMick (donmick)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved
After powering up, the GEdit document is intact and contains the latest
content, whereas the LibreOffice document is gone forever.
Thanks for testing. This is as expected, unless we use 'rename' - and
the code needs fixing to do that. *Unfortunately* the code is far worse
than a rats nest here.
Tested 3.5.0 Beta 2 and the bug persists. My repro steps:
1) Open LibreOffice, type something, and save it.
2) Open GEdit Text Editor, type something, and save it.
3) In a terminal, run sync. The previously-saved versions are now on disk.
4) Change the LibreOffice document and save again.
5)
(In reply to comment #13)
If some
enterprising kernel hacker wants to create a nice, ultra-liberally licensed
library that turns a dev_t into a boolean: int is_it_safe_to_fsync (dev_t *t);
then I'd be more than happy to see it used un-conditionally in our
system-abstraction for Unix / Linux.
Hi Tristan,
I was actually looking into that recently as part of another project
and it's pretty easy. Basically ...
Sounds cool :-) any chance you can knock up a nice fragment of tested C
code that would do this for Linux under MPL/LGPLv3+ that we can couple
up ? We'd want to add that to
I'm not sure the enhancement category is the right fit here. I'm sure
loss of data was not one of the design criteria, so it doesn't seem to
me like this aspect of LibreOffice can be considered to be working as
designed.
I'll try out 3.5.0 beta 1 when I get a chance.
--
You received this bug
** Changed in: df-libreoffice
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document
According to comments 6, 7 and 8, the relevant category seems to be enhancement.
LibreOffice works as designed but something could be improved when saving files.
Best regards. JBF
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: df-libreoffice
Importance: Critical = Wishlist
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document
I just lost a document I have been working on for weeks, due to the Ubuntu
overheating-problem, which caused a power-failure, and then due to this bug in
LibreOffice, which cost me weeks of work.
I am depending on Libreoffice due to the special features I require, which make
it easier to write
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still
** Changed in: df-libreoffice
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document
Yeah sorry about the Java comment, I thought for some reason that
LibreOffice was written in Java. Ignore that.
Doing the atomic rename as Michael suggests is a good middle-ground
between robustness and performance. ext4 in recent builds supposedly
adds an fsync to that if it is missing.
--
You
This is a tricky area. It is fine to ask people to call fsync like
drunken sailors on ext4 or btrfs - the costs are low; however for ext3
systems an 'fsync' can take many seconds to complete (if one has not
been run recently) during which the entire system is un-responsive to
I/O and the user
Severity Critical since this scenario causes data loss.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document lost by
Why do you think an example using Java, on Android even (comment #3) has
relevance for LibreOffice? Just asking in case you think LibreOffice is
written in Java...
Also a disk crash causes data loss. If you are working on important
documents, without doing backups to another device (preferrably a
** Changed in: df-libreoffice
Importance: Medium = Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document lost
** Changed in: libreoffice (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/817326
Title:
[Upstream] Previously-saved LibreOffice document
Launchpad has imported 5 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=40607.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
As a stopgap measure, I suggest not relying on the auto-save and using
save as and changing the filename everytime, for example appending v1,
v2, etc. I'm guessing if the last used file is scrapped by an outage or
suspend, the previous one won't.
--
You received this bug notification because you
I just lost a document I'd been working on for days. I saved it, closed
LibreOffice, then suspended my system. This morning I woke up my system
and the file was gone. Just like that. NOT happy.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Thanks (to myself) for hourly backups, although I spent most of another
hour finding out what happened.
Upstream is still marked NEW so I doubt this is getting the proper
attention.
** Changed in: libreoffice (Ubuntu)
Importance: Undecided = High
--
You received this bug notification
I have lost the minutes of an important one-day business meeting due to
this bug. Without this bug fixed I simply cannot afford to rely on
libreoffice (in fact I wonder if anyone knowing this bug takes the risk
to use libreoffice). I fully agree with the previous comments that this
is a highly
Libreoffice is in the main section and the _default_ ubuntu office
application. Not taking this bug seriously will give Ubuntu a very bad
PR! This IMHO includes setting the importance to Critical ASAP.
As a side note/question: What about the operating system level
workaround mentioned in Bug
Problem can be reproduced easily (tried on an Ubuntu 11.10):
1. Open LibreOffice
2. Create and save a document
3. Write busily and save regulary using Ctrl+S
4. Shut down the computer by removing the power cable
I fully agree with the previous comments that this is a *highly*
critical bug,
@Eduard I suspect LibreOffice is saving the file in such a cavalier way
that the kernel work-around is not even able to detect that it should be
saved transactionally.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in
Should not this bug be set to Importance: High?
Everyone is affected by it, it's just that most of the users will not know it
before they lose all what they have written.
Using a office suite that can at any time, with a little bad luck, erase all
you have written is not a reliable office
I agree, but normally it is courtesy to let the developers assign the
priority. You may want to comment on the upstream report at
https://bugs.freedesktop.org/show_bug.cgi?id=40607 about the importance.
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Summary changed:
- Previously-saved LibreOffice document lost by power outage (became 0 bytes
long) - LibreOffice should call fsync
+ [Upstream] Previously-saved LibreOffice document lost by power outage (became
0 bytes long) - LibreOffice should call fsync
--
You received this bug
** Bug watch added: freedesktop.org Bugzilla #40607
http://bugs.freedesktop.org/show_bug.cgi?id=40607
** Also affects: df-libreoffice via
http://bugs.freedesktop.org/show_bug.cgi?id=40607
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
I just lost a report I've been working on for four hours due to this
bug. My machine crashed very shortly after saving, and upon reboot
LibreOffice asks if I want to recover the file (it always asks this) but
fails. The file is now at zero bytes and there is nothing in
~/.libreoffice/3/user/backup
64 matches
Mail list logo
