Even if I simplify this file by deleting other sheets in the workbook and saving it as .ods (it was .xls), it still crashes if I try to sort. I can't easily send the file as it is a list of members and under data protection legislation.
Hi Hazel.. Please do this to remove confidential data: https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission And please provide steps to reproduce the problem. Then change status back to UNCONFIRMED after all required provided here.
Sanitising the file as suggested was enough to stop the bug ...
Hazel: what about if you just remove the private/confidential part? Would it be possible you attach the resulting file? If you really can't, you can try to retrieve an useful backtrace by following this link: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace
Hello Hazel, try to install LO 4.3.2, for example bug 80874 is resolved in this version.
Crashes for me as well occasionally, sometimes only on 2nd sort. The attached file, sorting selection to column L with 300 rows makes it crash
Created attachment 108858 [details] sample to make sort crash I noticed, sort is a lot more stable with this file when loaded from disk rather than directly from an email attachment when the file lives in /tmp rather in some folder owned by me
(In reply to Lutz from comment #6) > Created attachment 108858 [details] > sample to make sort crash > > I noticed, sort is a lot more stable with this file when loaded from disk > rather than directly from an email attachment when the file lives in /tmp > rather in some folder owned by me How do you proceed to sort your file? Which cell range? Which sort key? Best regards. JBF
In the sample file, I tried to sort cell range a1:L300 (or so, number of rows pretty variable and sorted column L ascending. Also crashed with other columns or directions, sometimes only the second time. I noticed, it crashed a LOT more frequently when I opened the file directly from my emil client. If I save it first and open the saved copy, it's more stable. Maybe it's related to the fact that in the former case the temporay file sits in /tmp rather than in $HOME/tmp and in /tmp I am an "other" instead of the owner. permissions on /tmp are all good, though, rwx for ugo. Maybe to reproduce one needs to email the file as attachment and then open from an email client.
Any update with last stable LO version 4.4.2? (+ brand new profile, see https://wiki.documentfoundation.org/UserProfile#Windows) Also, if still reproducible, would it be possible to retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace) Meanwhile, let's lower importance since it's not reproducible each time + Windows only.
*** Bug 93356 has been marked as a duplicate of this bug. ***
Confirmed duplicates with other OSes, raising priority and importance.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
I can no longer reproduce the crash in Versión: 5.3.0.3 Id. de compilación: 7074905676c47b82bbcfbea1aeefc84afe1c50e1 Subpr. de CPU: 1; Versión de SO: Windows 6.1; Repr. de IU: predet.; Motor de trazado: HarfBuzz; Configuración regional: es-ES (es_ES); Calc: group Closing as RESOLVED WORKSFORME Feel free to move it back to NEW if you can still reproduce the issue on your side.