Bug 56761

Summary: FILEOPEN: .odm crashes after update to 3.6.2
Product: LibreOffice Reporter: Kara <kara>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: critical CC: cedric.bosdonnat.ooo, michael.stahl, pmladek
Priority: high    
Version: 3.6.2.2 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Crashes on updating styles

Description Kara 2012-11-05 09:13:51 UTC
Existing master document crashes app on opening. Asks to update links and styles, and then crashes all Libreoffice apps without error or trace. Same behaviour with newly crafted .odm as soon as some changes in styles were made (Header formats). No error message when calling doc from terminal, but same behaviour.
Comment 1 Petr Mladek 2012-11-13 11:00:40 UTC
Hmm, I am unable to reproduce this with the LO-3.6.3 on Linux. I created new master document, modified some styles (Default, Header 1), wrote some text using these styles, saved and reopened the file. It worked fine.

Kara, could you please attach sample file that shows the problem?
Comment 2 Kara 2012-11-13 20:25:35 UTC
Created attachment 70029 [details]
Crashes on updating styles

Two people confirmed here http://libreofficeforum.org/node/4676#comment-21062
Comment 3 Petr Mladek 2012-11-26 13:03:44 UTC
Ah, I forgot to add myself into CC and missed your comment :-(

Hmm, I am still not able to reproduce the crash. I can open the attached document without problems. Note that it does not ask to update any style or links. I wonder if the sample is incomplete or I do something wrong.

Kara, could you please provide more detailed steps to reproduce? Something like:

1. Open the document blabla.odm
2. Select in menu ....
3. ...

Result: Crash,...
Comment 4 Petr Mladek 2012-11-26 13:26:43 UTC
Anyway, master document is a feature used only by limited group of experienced users. It seems that we have a regression here and should fix it ASAP. On the other hand, it could not block the the release of 3.6.4 bugfix release with many other useful fixes => slightly reducing the severity.
Comment 5 QA Administrators 2013-07-18 06:16:03 UTC
Dear Bug Submitter,

Please read the entire message in its entirety before continuing - also please respond directly to FDO when replying - do not reply via email.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 6 QA Administrators 2013-09-24 02:06:29 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO