To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=93071
User fs changed the following:
What |Old value |New value
================================================================================
Assigned to|dbaneedsconfirm |fs
--------------------------------------------------------------------------------
Ever confirmed| |1
--------------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
--------------------------------------------------------------------------------
OS/Version|Mac OS X |All
--------------------------------------------------------------------------------
Platform|Macintosh |All
--------------------------------------------------------------------------------
Target milestone|--- |OOo 3.1
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Thu Jan 8 13:13:45 +0000
2009 -------
okay, can finally reproduce.
There's a number of important points, the following sketch is a minimal
description, I think:
- start OOo (important: do not use -norestore :)
- open a DBDoc
- modify this DBDoc
important: do *not* save it
- crash OOo, e.g. by executing the following Basic macro:
createUnoService("com.sun.star.frame.DispatchHelper"). _
executeDispatch(StarDesktop, ".uno:Crash", "", 0, Array())
important: The crash *must* be "soft" enough that the crash reporter can be
started and successfully run
=> an error box pops up, information about the crash, and saying that the
DBDoc will be recovered
- confirm the box with OK
- restart OOo (if not done automatically)
=> the recovery wizard pops up
- allow the wizard to recover the DBDoc
- make modifications to the DBDoc
- save and close the DBDoc
- close and restart OOo
- re-open the DBDoc
=> the most recent changes are lost
In fact, if you look into the file history (menu: File/Recent Documents), you'll
notice a DBDoc entry with a strange "temporary" location - this is what you
actually worked on after the recovery, not the original document.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
