User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 Build Identifier: Version: 5.1.5.2 Build ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5 Hi. When the filter is active in a spreadsheet and the field contents is a date, after applying a filter and trying to select “all”, Calc crashes. Reproducible: Always Steps to Reproduce: Steps to reproduce: Open test file provided Open the filtering pane in field7 Select option “Not Empty” The filter is applied ok Open the filtering pane again Select option “All”, at the bottom Calc crashes. Actual Results: This behavior only happens with columns that have dates, and not with other types of data like time or numbers. Note that if the option “2016” is selected, the “All” option also is activated, and Calc would not crash, so this serves for a workaround. This is related to bug 99422 for LO 5.2 wich was fixed Reset User Profile?No
Created attachment 127754 [details] Test file with dates
Created attachment 127756 [details] Screenshots
Hi @Rober, reproducible with Win10x64 Version: 5.1.5.2 (x64) Build ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5 CPU Threads: 1; OS Version: Windows 6.19; UI Render: default; Locale: es-ES (es_ES); Calc: CL not reproducible Win10x64 Version: 5.2.2.2 (x64) Build ID: 8f96e87c890bf8fa77463cd4b640a2312823f3ad CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Locale: es-ES (es_ES); Calc: CL but even it is a crash, no reproducible with newer versions. Happens only with date fields, not i.e. with time fields.
Robert: following Mariosv's comment, could you give a try to brand new 5.2.2?
Not reproducible with Version: 5.2.2.2 (x86) Build ID: 8f96e87c890bf8fa77463cd4b640a2312823f3ad CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Locale: es-MX (es_MX); Calc: group on Windows 10 and other PC with WinXP SP3
this bug has been confirmed -> set back to NEW. Best regards. JBF
From French QA ML : reproduced on Linux too. Best regards. JBF
Not reproducible on 5.1.4.1 (x64) on Win7 SP1 x64.
(In reply to Jouni Järvinen from comment #8) > Not reproducible on 5.1.4.1 (x64) on Win7 SP1 x64. Build ID: a4d48e4ff0e9f93e78b6356ca7b0b6303e360356
Jean-Baptiste: 1) Since the bug appears in 5.1 branch, perhaps just in 5.1.5 (following Jouni's comment, number 8) and not in 5.2.2 2) 5.1 branch is EOL or will be soon (see https://wiki.documentfoundation.org/ReleasePlan/5.1) => may we put this one to WFM or do you have information it's reproduced in 5.2 branch?
My comment in bug 99422 : Could it be possible that bug 102904 is a duplicate of this one but for version 5.1.5 ? If this is the case could it be possible to backport the fix to 5.1.6 ? Best regards. JBF
Looks fine close this one as duplicate of bug#99422, because besides it's have been already asked for backport in that bug.
I have tested this bug with Version: 5.1.6.2 Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909 CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Locale: es-MX (es_MX); Calc: group on Windows XP SP3 and Windows 10 and it seems to be corrected, maybe because of the fix of bug 101165 I leave this for some one else to confirm
Seems to work with Version: 5.1.6.1 (x64) Build ID: f3e25ec0581f5012f54d8810dcddd5824f4ee374 CPU Threads: 1; OS Version: Windows 6.19; UI Render: default; Locale: es-ES (es_ES); Calc: CL *** This bug has been marked as a duplicate of bug 101165 ***