Issue 111024 - Links are modified/destroyed/fucked up after crash and recovery
Summary: Links are modified/destroyed/fucked up after crash and recovery
Status: CLOSED DUPLICATE of issue 107968
Alias: None
Product: Impress
Classification: Application
Component: code (show other issues)
Version: OOO320m12
Hardware: PC HP-UX
: P3 Trivial (vote)
Target Milestone: ---
Assignee: graphicsneedsconfirm
QA Contact: issues@graphics
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2010-04-20 20:25 UTC by owqcd
Modified: 2010-06-24 17:04 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description owqcd 2010-04-20 20:25:56 UTC
Hello,

after crash and recovery, relative links to images are fucked up in an .odp
document. This is comparable to issue 107968, but the latter is only stated for
the "Spreadsheet" component.

I compared the buggy version with a backup working version. I checked the
content of the files "content.xml". It appears that the bug makes the following
modification : "href=(relative link)" -> "href=../../..(absolute link)".
Of course, the last link leads nowhere. 

Details :
Excerpts from "content.xml" of a working version:
<draw:image
xlink:href="../../../../../lycee/TGMAT/chimie/oxydoreduction/presentationDecoupe/laserPlaque.jpg"
<draw:image xlink:href="../../types_de_lasers/cavite_elliptique.png"

Excerpts from the "content.xml" after crash/recovery:
<draw:image
xlink:href="../../../home/me/backup/lycee/TGMAT/chimie/oxydoreduction/presentationDecoupe/laserPlaque.jpg"
<draw:image
xlink:href="../../../home/me/backup/enst/lasers/cours/types_de_lasers/cavite_elliptique.png"

PS: This file was important and I was loosing one day of work (what's the use of
the auto-save... ? it did not help at all !). I was able to correct the
"content.xml" file (after many hours of python scripting) and saved my work.
Comment 1 wolframgarten 2010-04-28 08:08:24 UTC
Is the crash reproducible and what did you do then? If this is not reproducible
we cannot do anything about it.
Comment 2 nalimilan 2010-06-14 12:08:57 UTC
I think that's a duplicate of Issue 107968, since symptoms are similar accross
all OO.o components. No need to reproduce the crash, you only need to trigger
recovery (kill -9 will do).
Comment 3 Rainer Bielefeld 2010-06-14 12:49:59 UTC
@nalimilan
Thank you for your hints how to reproduce!

*** This issue has been marked as a duplicate of 107968 ***
Comment 4 Mechtilde 2010-06-24 17:04:42 UTC
duplicate -> closed