Issue 2257 - Crash if trying to "recover a session" twice simulataneously.
Summary: Crash if trying to "recover a session" twice simulataneously.
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 638
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-22 14:04 UTC by osavill
Modified: 2002-01-21 14:16 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description osavill 2001-11-22 14:04:55 UTC 
Following a crash I had "recovered" the document. This was now named foobar.tmp, so I save it as the origional, but deleted by Open Office !, document. I then received an e-mail with a document attached, clicked the document and waited and waited and waited (well, it is the Linux version :-)  ) until Open Office started, but instead of starting it popped up a dialog asking if I wanted to recover a document. Unknown to me this was the same recovery that I had made origionally. Open Office #2 crashed. 



This raises a couple of issues:



1) Why hadn't the first recovery been tagged as recovered ?



2) Since Open Office was already up and running isn't it a bit extreme to bring up another complete Open Office. Surely the new document could have been placed inside the already running Open Office.
Comment 1 stefan.baltzer 2001-11-26 14:27:45 UTC 
This does not look like "word processor only" -> I changed the component to framework.
Reassigned to Thorsten.
Comment 2 thorsten.martens 2001-12-17 15:45:57 UTC 
I wasn`t able to reproduce this problem. When using a internal 641
running under Linux Suse 7.2 all works fine and the mentioned problem
doesn`t occur.
Comment 3 thorsten.martens 2002-01-21 14:16:53 UTC 
Due to missing any further information and the fact, that this issue worksforme, it is closed !