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
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
** 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
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
** 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
** 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
** 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
** 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
** 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
30 matches
Mail list logo
