To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=44808
                  Issue #:|44808
                  Summary:|OOo won't start after crash
                Component:|Word processor
                  Version:|OOo 1.1.3
                 Platform:|Other
                      URL:|
               OS/Version:|Linux
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|ui
              Assigned to:|mru
              Reported by:|rajmarshall





------- Additional comments from [EMAIL PROTECTED] Fri Mar 11 05:35:31 -0800 
2005 -------
I have a OOo writer file that caused Ooo 1.1.2 to crash - I have 1.1.3 also
installed on this machine and I then attempted to run 1.1.3 (the user concerned
hadn't tried 1.1.3 yet) and it would not start. Tried it from the command line
but there were no error messages and the OOo Writer window would not appear.

I eventually found a file in /tmp called
OSL_PIPE_500_SingleOfficeIPC_858830f47980b329a4ab88f2bc7934c8
which I deleted and then 1.1.3 started ok (and 1.1.3 would read in the problem
file without any problems!)

I suggest that the code that fails when this /tmp file exists ought to produce
and error message to give the user some indication of what they need to do to
get things going again!

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