desktop-packages team mailing list archive

[Bug Watch Updater <157249@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 13 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=33393.

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
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2011-01-24T05:24:00+00:00 Bryan Quigley wrote:

Created attachment 42354
Read_Error_file

Attaching file that exhibits the issue.  I have manually remove over 22
graphics from the file (removing from content.xml, manifest.xml and pictures
folder when unzipped).  I had to do this manually due to the issue that when I
resave the file, it no longer will exhibit this behavior.  This behavior occurred originally without any manual editing of odt files, but is much more difficult to reproduce.

This is a long-standing regression compared to OpenOffice.org

Steps to reproduce:
Download the file to the desktop (DO NOT OPEN DIRECTLY)
Open the file
Set autorecovery on and to 1 minute.
Change/Add text on the first page (delete 09)
Wait at least one minute, maybe two
Note the Read-Error Message

For the data loss part, simply save the file, then reopen.

This bug has been reported elsewhere:
https://bugs.launchpad.net/openoffice/+bug/157249
https://bugzilla.novell.com/show_bug.cgi?id=440795

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/16

------------------------------------------------------------------------
On 2011-01-24T06:10:16+00:00 Libreoffice-z wrote:

I see the effect with "LibreOffice 3.3.0 RC4 - WIN7  Home Premium
(64bit) German UI  [OOO330m19 (build 6 / tag 3.3.0.4)]". The question is
what we can do, currently it seems to be a damaged document causing some
problems. The effect seems to disappear when I copy / paste all contents
to a new WRITER document, but I also was not able to reproduce the
problem with the original document in further tests.

@Bryan Quigley:
Please contribute information concerning your Platform and OS!
Any chance to reproduce

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/17

------------------------------------------------------------------------
On 2011-01-24T06:17:06+00:00 Bryan Quigley wrote:

I believe the file was originally created on Ubuntu 9.04 or 9.10 and the
corresponding version of OpenOffice, but I am not entirely sure.

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/18

------------------------------------------------------------------------
On 2011-01-24T06:18:33+00:00 Bryan Quigley wrote:

Once you save the file, the issue will no longer reappear reliably.
The method I used to make this file, was the best I could do at making
it easy to reproduce the effect.

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/19

------------------------------------------------------------------------
On 2011-03-17T07:38:07+00:00 Y9a7s7tj-steve-si9yrl01 wrote:

Hi.
I had this in OO a year or so ago, think I filed a bug, can't remember.
I have a feeling it related to EPS images in my case and then images just kept disappearing. What was happening was that the linking was damaged. 
I.e after the the save when the image was read-error I could go into the odt file and the image was still there, what had broken was the reference to the image.

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/20

------------------------------------------------------------------------
On 2011-05-30T21:12:18+00:00 Lpsolit-r wrote:

I can reproduce with LibO 3.4rc2. Why is the severity "normal" only?
Dataloss is pretty critical.

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/23

------------------------------------------------------------------------
On 2011-05-31T04:45:49+00:00 Libreoffice-z wrote:

(In reply to comment #5)
> I can reproduce 

With what documents?

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/24

------------------------------------------------------------------------
On 2011-05-31T08:41:21+00:00 Tlillqvist-k wrote:

> Why is the severity "normal" only?

Because the severity field is fairly meaningless here, as anybody can
change it.

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/25

------------------------------------------------------------------------
On 2011-05-31T22:03:32+00:00 Lpsolit-r wrote:

(In reply to comment #6)
> With what documents?

With the document attached to this bug, as well as some of my own
documents used at work.

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/26

------------------------------------------------------------------------
On 2011-09-07T12:33:18+00:00 achristoffersen wrote:

I have this also - and have had it with several versions of OOo / LO.

I can't say exactly how it happens, but I did most of my work on a linux
box, exchanging documents with Windows users I begged and finnally
convinced to download LO. Yey very often when email a version back and
forth - this would happen.

Currently I am on a mac with LibreOffice 3.4.1 (Build:103) and it still
happens. My collaborators does not complain about it, so I wonder if it
is a *nix thing.

I really hope this will get some attention. Please tell me how I can
help (technical bugfixing skillz = zero)

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/27

------------------------------------------------------------------------
On 2011-11-17T23:51:10+00:00 Eugeneb wrote:

I am having the same problem with Read Error replacing my graphics in LO
Writer 3.4.4 (build 402) since switching to LO. I am using native ODT
format and occurs with several of my ODT docs. The images are actually
lost from the data, 8 MB file becomes 1 MB file.

Documents were originally created in OO. We did not have the problem
until moving to LO 3.3. I had hoped that 3.4.4 would resolve this
significant issue.

Initially we thought this was related to errors caused by MAC users. We
did some testing and opened the file under Mac LO 3.4.4, saved, closed,
then opened in the same version with Windows 7 LO. The images were
present, then at some point they were replaced with Read Error. Mac user
does not have the same problem. This error was not seen when alternately
opening OO files between Mac and Windows.

Error occurs whether files are on my local Windows 7 machine or on the
network drive.

My testing shows that corruption occurs during autosave. Manually saving
the file first does not eliminate the error. I am able to reproduce the
problem easily.

Eugene

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/29

------------------------------------------------------------------------
On 2011-11-18T18:29:35+00:00 Eugeneb wrote:

We spent a few hours going back and forth between Windows and Mac,
opening vulnerable LO files in Mac and Windows, pasting the content into
new files, saving, using network and local file copies, and editing with
autosave enabled and disabled. The Read Error for the images is
associated with autosave and occurs under Windows and Mac regardless of
the other variables.

All of the images are png. We did find that a small png button that we
placed during this testing was not lost, only the larger images.

We edited a file in Lotus Symphony and brought it back into LO in
Windows and the Read Error still occurred with Autosave. Older files
from OO also experienced the Read Error with autosave.

We have used OO for years to create user manuals, which contain many
images and extensive use of styles. In addition to the image read error
bug, we also found that when an image is inserted, the document view
jumps to the bottom of the document. This is an undesirable
characteristic that was introduced with LO, and not present in OO.

IBM Lotus Symphony opens the ODT docs without error, but under Mac it
only opens the files on our server as read-only. Symphony was stable;
autosave worked correctly, and image insertion did not change the
document view. However, Symphony does not seem to have the math
component which we used for formula objects, although it did allow
editing of existing math objects. Nevertheless, it is a very good
replacement candidate for those looking to avoid the mentioned LO bugs.

Corel does a poor job of opening ODT files, the formatting was
completely lost.

For now, we are reverting to OO 3.3.0 until compelled to make a change
or these LO bugs are fixed.

Eugene

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/30

------------------------------------------------------------------------
On 2011-11-19T10:03:24+00:00 Cno wrote:

Never seen this problem with whatever old files I use.

So to be able to track down to the source of this partictular issue
(some damaged file, as suggested in an earlier comment?), having a
simple test document would be useful.

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/157249/comments/31

-- 
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/157249

Title:
  [Upstream] [ooo-build] images deleted from file after auto-save occurs

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Incomplete
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  I have opened an existing file for the first time in Gutsy with OOo
  2.3.  After some modifications brought to this file, I noticed some
  images had disappeared, but not all images, and an error message was
  displayed in a frame of the size of the disappeared image indicating a
  read error.  Then, I don't saved it to keep my file in its last
  correct state, and I made a copy of this file and opened it in
  parallel. And at this time the images reappeared in my first modified
  file.  So, I saved it and closed. After reopening, all images which
  had disappeared were not present (not an empty frame, but totally
  removed this time).

  After, I opened a new copy of my file and I insert a space and remove it in order to have "save" button enabled and my file not modified, and then I saved it.   I wondered why the size increased from 155566 bytes to 159378 with exactly the same content, maybe a new version of ODF used in OOo 2.3 as this file was created with OOo 2.0 and last modified on 2.1???  I have redone the same modifications and this time there was no problem.
  I noticed that when I had finished to redo the same modifications, automatic saving was triggered, that I didn't see the first time. I say that as this is may be linked to this problem, and the images in the first time disappeared after a duration of the same order, but this is only an hypothesis and I'm not sure at all of that (I will try to made some new tests).

  I condider this as critical as it leads to a content loss.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/157249/+subscriptions