Issue 8269 - file crash
Summary: file crash
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Impress
Classification: Application
Component: ui (show other issues)
Version: 643
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: wolframgarten
QA Contact: issues@graphics
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-10-12 12:23 UTC by manfredr
Modified: 2003-09-08 16:54 UTC (History)
3 users (show)

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


Attachments
presentation made in OOo 1.0.1 small changes in 643 -> crash (1.39 MB, application/octet-stream)
2002-10-12 12:28 UTC, manfredr
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description manfredr 2002-10-12 12:23:12 UTC
Impress crashed my presentation - at least 15 hour work
please help - I need the presetation at www.common-d.de
asap
Comment 1 manfredr 2002-10-12 12:28:23 UTC
Created attachment 3145 [details]
presentation made in OOo 1.0.1 small changes in 643 -> crash
Comment 2 prgmgr 2002-10-13 17:30:30 UTC
Manfred, thank you for using and supporting OOo.

Please post this support question to the users mailing list.
Comment 3 manfredr 2002-10-13 20:06:11 UTC
1.
with the file as attachment?
2.
Do you think anybody on the users@openoffice.og can help me?
3.
Or do you mean users@de.openoffice.org?
Comment 4 lohmaier 2002-10-14 14:54:22 UTC
reopening issue since OOo crashes with self-created document.
I don't see a single reason to close this one as invalid. Please
explain why you did so...
Comment 5 prgmgr 2002-10-14 15:05:39 UTC
Manfred, posting to either users@openoffice.org or
users@de.openoffice.org is a good start.

Christian, a few things about this issue:

From the initial comment, it's more of a support issue than it is a
valid issue report.  We cannot help users recover their data from
corrupted data files.

There is no way to replicate this issue and one does expect the file
to have some sort of corruption if OOo crashes.

643 on RH 8.0 opens the file fine.  However 643 is a developer release
and I don't want to mislead the user into thinking some sort of data
recover is possible ( which is why I never mentioned the result ).

Christian, feel free to help this user offline to recover their data
if you want to.
Comment 6 lohmaier 2002-10-14 15:45:40 UTC
> We cannot help users recover their data from corrupted data files.

That's right, but if OOo creates these corrupted files itself or
crashes, than this issue should be handled nevertheless.
I agree with you that the description/subject (everything) is far from
being ideal.

> 643 on RH 8.0 opens the file fine.

Same here.

> However 643 is a developer release and I don't want to mislead the
> user into thinking some sort of data recover is possible ( which 
> is why I never mentioned the result ).

I know Manfred from the de-Project and he should know the difference :-)

> Christian, feel free to help this user offline to recover their 
> data if you want to.

I'll do so, but first I'd like to see if theres an issue or not. Even
if 643 is a developer release, bugs in there should be fixed. So it
depends whether this is reproducible or not.

Manfred,
please give step-by-step instructions to reproduce the crash.
The attached document loads fine in OOo1.0.1 and OOo643. I can watch
the slideshow without any problem. I also made some small changes
(added some text, deleted or resized some graphics) but OOo did not crash.
Unable to reproduce. (You can assign this issue to me (or the
german-lang-Project)
Comment 7 manfredr 2002-10-14 17:32:24 UTC
Hi Christian,

please give step-by-step instructions to reproduce the crash.
The attached document loads fine in OOo1.0.1 and OOo643. I can watch
the slideshow without any problem. I also made some small changes
(added some text, deleted or resized some graphics) but OOo did not crash.

Hinweis: Nachdem ich nichts anderes einen Export als HTML gemacht
hatte, wollte 643 wieder speichern. Ich habe gespeichert. 
Danach war der Inhalt bei mir weg.
So nun reichts. 

Hi PM
this was my last bug-report.