Bug 57003 - EDITING: CRASH when 'delete - contents - comments' in particular .ods
Summary: EDITING: CRASH when 'delete - contents - comments' in particular .ods
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) rc
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-11-12 06:45 UTC by Rainer Bielefeld Retired
Modified: 2013-09-24 02:06 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2012-11-12 06:45:55 UTC
I found this prolbem during my research for "Bug 56983 - EDITING: CRASH when copy / paste cell"

Steps how to reproduce with "LibreOffice" German UI/ German Locale [Build-ID: 58f22d5] on German WIN7 Home Premium (64bit) 

0. Download  sample document Attachment 69916 [details] from a.m. bug
1. Open sample document from LibO Start center
2. In slide "St__Hout art_ 8_2_3" click top left row + column heading to
   select all 
3. Menu 'Edit -> Delete Contents - Uncheck all except "Comments" -> <ok>

Still  [Reproducible] with parallel installation of Master "LOdev   -  ENGLISH UI / German Locale  [Build ID: 70ec82)]"  {tinderbox: @16, pull time 2012-11-09 00:53:19} on German WIN7 Home Premium (64bit) with separate User Profile for Master Branch

Was already [Reproducible] with Server Installation of  "LibreOffice  English UI/ German Locale [Build-ID: 1e73405],{tinderbox: Win-x86@9 pull time 2012-10-05 15:31:15}  on German WIN7 Home Premium (64bit) 

Was ok with 
- Server Installation of "LibreOffice release”  German UI/ German Locale [Build-ID:  da8c1e6]

With the versions I tested reproducibility is identical to Bug 56983, so may be the crashes have the same root, or even this one might be a dUP?

This problem seems to be related to very particular circumstances. No crash when I save original sample from LibO and do test
Comment 1 Markus Mohrhard 2012-11-24 18:09:55 UTC
Seems to no longer crash in current master.
Comment 2 bfoman (inactive) 2012-11-30 10:02:18 UTC
Could not reproduce as sample document attachment 69916 [details] is no longer available.
Please update status if fixing bug 56983 solved this issue.
Comment 3 QA Administrators 2013-07-18 06:16:05 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: 

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 4 QA Administrators 2013-09-24 02:06:33 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