Issue 121963 - my open office won't open past a restore window, window
Summary: my open office won't open past a restore window, window
Status: CLOSED DUPLICATE of issue 119006
Alias: None
Product: Writer
Classification: Application
Component: viewing (show other issues)
Version: 3.4.1
Hardware: Mac Mac OS X, all
: P3 Blocker (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-26 15:12 UTC by dylangeorgemetcalfe
Modified: 2017-05-20 10:14 UTC (History)
4 users (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 dylangeorgemetcalfe 2013-03-26 15:12:13 UTC 
when I click on the open office icon to open it, everything opens but a small window comes up saying, open office unexpectedly quite do you want to restore window or don't restore window. I try and click either of them and nothing happens. I then tried opening it in another application because I have important work that is due on it but they say they can't open the file.
Comment 1 simonorichards 2013-04-21 06:21:45 UTC 
I have the same problem, tried reinstalling OO still have the same problem
Comment 2 simonorichards 2013-04-21 06:35:34 UTC 
It appears the problem is due to corrupt restore state 
in 
Application Saved States from Mac OS X Resume

I found how to remove the problem at 

See 

http://osxdaily.com/2011/07/17/delete-specific-application-saved-states-from-mac-os-x-10-7-lion-resume/
Comment 3 JZA 2013-08-15 20:00:36 UTC 
Lack of response by the original creator could be a prove that the suggestion worked.
Comment 4 Rainer Bielefeld 2013-09-17 15:16:55 UTC 
IMHO not an individual bug.

For now I will mark all similar bugs as DUP of Bug 119006

Please feel free to reopen that bug if you find out that the workaround does
not help you.
Please feel free to reopen this Bug if you find evidence that we have an
independent issue here  (for example because the fix / workaround for the other
bug does not work for you).

*** This issue has been marked as a duplicate of issue 119006 ***