Bug 46650 - FILEOPEN - Writer does not open existing .odt, .ott files.
Summary: FILEOPEN - Writer does not open existing .odt, .ott files.
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86-64 (AMD64) Windows (All)
: medium blocker
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-26 09:26 UTC by Zsolt Farkas
Modified: 2012-03-02 08:44 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Zsolt Farkas 2012-02-26 09:26:33 UTC 
I closed an edited writer document and restarted the system (W7profx64) without quit from running LibO 3.5.
I can not open any .odt after restart. :( .doc, .docx and other .od? files open well. I can not open any .ott also.
I tried to repair install with 7 installed program feature.
I tried uninstall and reinstall the sw, but the problem remained.
Comment 1 Florian Reisinger 2012-02-26 22:54:30 UTC 
Is there any error message...
Comment 2 Zsolt Farkas 2012-02-27 14:46:15 UTC 
There is no any error message, just a freezed open window remains till Task Manager stop the process.
Comment 3 Zsolt Farkas 2012-02-27 14:52:58 UTC 
(In reply to comment #1)
> Is there any error message...

There is no any error message, just a freezed open window remains till Task
Manager stop the process.

I tried to remove saved profile data from user profile also, but freeze remained.
Comment 4 Zsolt Farkas 2012-02-27 14:58:36 UTC 
I reinstalled OOo 3.3 because I have to continous editing... That works well! ;)
Comment 5 Petr Mladek 2012-03-02 08:44:44 UTC 
I am afraid that we can't do much here without a way to reproduce or more information for debugging.

I wonder if it might help to restart the whole system. It is possible that something wrong remained in the memory.

Anyway, I close the bug for now. Feel free to reopen it it if you see it again with LO-3.5.1 or newer.