Description: I marked some range like (for example) H1:V50 which included occasional empty rows (but the head row H1:V1 always had data) and wanted to have it sorted by column. I navigated via menu and submenu and issued the sort command through a popup dialog by mouse. Reference: crashreport.libreoffice.org/stats/crash_details/9532106c-f9a8-41ad-adc2-6ddfb7449c58 Steps to Reproduce: 1. enter strings (rotate:90 degrees for compactness) in first row 2. enter sparse numbers in only a few of the cells 3. mark a sub-range of that table including the top row: a range not starting in col.A but further to the right and including only a few dozen rows down, not all 4. try to sort this sub-range BY COLUMN 1 E.g. mark range E1:J25 where E1:J25 is filled with string data and few other cells of E2:J25 have numeric data, then sort by column. Actual Results: crash (see description) Expected Results: (no crashing of the program?) (whatever error message would have been better than just a crash, at least to avoid that in future) Reproducible: Didn't try User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Forgot to mention: The pop-up dialog has two tab panes; the first with dropdowns for the sort criteria. The second offers half a dozen checkboxes which I had not noticed and therefore had not altered the defaults - other than switching the very bottom radiobutton ON (the one specifying the sort by columns instead of rows). In some more tries now I did the same but also unchecked the second checkbox (roughly: range contains headline columns) and that way, sorting by columns does not cause Calc to instantly crash. However, it also does not reliably sort the table range as desired. - I continued trying around, switched the two panes and repeated switching the second checkbox (of the second pane), but found no sure path to get the marked range to become properly sorted by columns.
Hello, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug.
(In reply to Xisco Faulí from comment #2) > Hello, > Thank you for reporting the bug. Please attach a sample document, as this > makes it easier for us to verify the bug. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Dear Bug Submitter, 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-20180530
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180703