To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=94278
                 Issue #|94278
                 Summary|OOo doesn't restart after crash until soffice.bin proc
                        |ess is killed
               Component|framework
                 Version|OOo 3.0 RC2
                Platform|PC
                     URL|
              OS/Version|All
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|tm
             Reported by|lendo





------- Additional comments from [EMAIL PROTECTED] Wed Sep 24 13:08:32 +0000 
2008 -------
After OOo crashes, OOo and the file recovery utility don't start until the
process "soffice.bin" will be killed with the Task Manager of Windows XP.

Steps:
* Crash OOo.
* A window appears, that inform you of the document recovery utility after
restart. Close the windows.
* Try to start an OOo application. - Nothing happens.
* Go to the Task Manager of Windows XP and kill (one of) the process(es)
"soffice.bin".
* Start an OOo application.
* Follow the recovery instructions ...

I tested this with and without the Quick Starter enabled.

I for one can simply kill the "soffice.bin" process , but an inexperienced user
can not do that. So, this is very annoying.

---------------------------------------------------------------------
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]

Reply via email to