Bug 61145 - Open ODF result on crash
Summary: Open ODF result on crash
Status: RESOLVED DUPLICATE of bug 60132
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: Other macOS (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-19 23:59 UTC by Diogo Martins
Modified: 2013-02-25 17:35 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
This is a colaboration document, created on other computer and edited on my (144.72 KB, application/vnd.oasis.opendocument.text)
2013-02-19 23:59 UTC, Diogo Martins
Details
Apple Crash Report (73.68 KB, application/pdf)
2013-02-20 20:36 UTC, Diogo Martins
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Diogo Martins 2013-02-19 23:59:44 UTC
Created attachment 75143 [details]
This is a colaboration document, created on other computer and edited on my

This problem is on a collaboration document, created out of my computer and edited on my, with registry of edition and comments.
When i receive the document it open well, but after i edit, and close the document, then i open again and it crash the Write.
Comment 1 Julien Nabet 2013-02-20 17:54:26 UTC
On pc Debian x86-64 with master sources updated today, I didn't reproduce the crash.

Could you tell what's the environment and the version of LO on the other machine?
Does it crash on the other machine too or just yours?

Could you try to retrieve extra information by following this link?
https://wiki.documentfoundation.org/BugReport#How_to_get_debug_information_on_Mac_OS_X
Comment 2 Diogo Martins 2013-02-20 18:30:46 UTC
On other machines this happens too, in specific, on Windows, i think is Windows 7 and LibrOffice 4.0 too.
Comment 3 Diogo Martins 2013-02-20 18:31:18 UTC
(In reply to comment #1)
> On pc Debian x86-64 with master sources updated today, I didn't reproduce
> the crash.
> 
> Could you tell what's the environment and the version of LO on the other
> machine?
> Does it crash on the other machine too or just yours?
> 
> Could you try to retrieve extra information by following this link?
> https://wiki.documentfoundation.org/
> BugReport#How_to_get_debug_information_on_Mac_OS_X

On other machines this happens too, in specific, on Windows, i think is Windows 7 and LibrOffice 4.0 too.
Comment 4 Julien Nabet 2013-02-20 19:13:31 UTC
Diogo: thank you for your feedback.
As indicated in my previous comment, could you try to retrieve extra information by following this link?
https://wiki.documentfoundation.org/BugReport#How_to_get_debug_information_on_Mac_OS_X

PS : please don't answer from your mailer but directly on the bugtracker.

To add a comment or answer a question:
https://bugs.freedesktop.org/show_bug.cgi?id=61145#add_comment

To attach a file + let a comment:
https://bugs.freedesktop.org/attachment.cgi?bugid=61145&action=enter
Comment 5 Diogo Martins 2013-02-20 20:36:11 UTC
Created attachment 75204 [details]
Apple Crash Report
Comment 6 Julien Nabet 2013-02-20 21:06:39 UTC
Comment on attachment 75204 [details]
Apple Crash Report

Mimetype fixed
Comment 7 Julien Nabet 2013-02-20 21:18:17 UTC
Cédric/Michael: I don't reproduce this with master but reporter attached a bt. One for you?
Comment 8 Petr Mladek 2013-02-25 11:30:50 UTC
Diogo, could you please try it with 4.0.1.1 build from http://www.libreoffice.org/download/pre-releases/ ?

I tried to open the test document on Linux. I got "Read error" with 4.0.0.3 build but it opened fine with 4.0.1.1 => We evidently fixed a problem related to this document for 4.0.1 release. It might solve the crasher as well.

Otherwise, I reduce the severity a bit. We should fix it ASAP but it seems to be a bit specific to your document. Such bugs should not block the next bugfix release with many other useful fixes. I actually hope that it is already fixed in 4.0.1.
Comment 9 Michael Stahl (allotropia) 2013-02-25 17:35:33 UTC
that stack looks familiar

*** This bug has been marked as a duplicate of bug 60132 ***