Description: If a whole row is selected by clicking the row number, Libre Office Calc crashes Steps to Reproduce: 1.Open a spreadsheet 2.Click on a row number to select row 3. Actual Results: Calc crashes Expected Results: Row selected Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: This only happens on a single spreadsheet. THe spreadsheet in question is 65.6Kb in size, has 404 rows and 29 columns The problem can be sorted via a work-around of saving the file as an .xlxs file type and then re-saving as an .ods file. This is not suitable in all cases e.g. where formatting etc may be lost in the conversion.
Created attachment 153376 [details] Crash message
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Dear Dave Potter, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping
Problem has since disappeared after reboot. Closing bug.
(In reply to Dave Potter from comment #4) > Problem has since disappeared after reboot. Closing bug. Thanks Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been identified.