Bug 133698

Summary:	Calc crash if I mark a line in an empty table, select Data->Sort->Sort Key 1 (Column A)
Product:	LibreOffice	Reporter:	Jan <jan.coenen>
Component:	Calc	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INVALID
Severity:	normal	CC:	jan.coenen, ming.v.hua, rene
Priority:	medium
Version:	6.1.5.2 release
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description Jan 2020-06-05 10:32:17 UTC

Description:
Calc crash if I mark an empty line in an empty table, select Data->Sort->Sort Key 1 (Column A)

Need to switch tty with ctrl-alt-F3, login as root and pskill soffice

fully reproducable

Steps to Reproduce:
1. open calc
2. click on line 1 to select whole line
3. Select Data, Sort, Sort Key 1 Popup (Column A)

Actual Results:
Session non - responsive, weird grafic displays

Expected Results:
Popup open to select sort column


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 6.1.5.2
Build ID: 1:6.1.5-3+deb10u6
CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: de-DE (en_US.UTF-8); Calc: group threaded

OpenGL: under Tools ▸ Options ▸ LibreOffice ▸ View I have unchecked 'Use Hardware acceleration' and 'Use anti-aliasing' but the error still persists.

Comment 1 Ming Hua 2020-06-05 11:05:10 UTC

Can't reproduce on Windows with either 6.1.6 or 6.4.4:

Version: 6.1.6.3 (x64)
Build ID: 5896ab1714085361c45cf540f76f60673dd96a72
CPU threads: 2; OS: Windows 10.0; UI render: GL; 
Locale: zh-CN (zh_CN); Calc: group threaded

Version: 6.4.4.2 (x64)
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 2; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; 
Locale: zh-CN (zh_CN); UI-Language: en-US
Calc: threaded

Adding Rene to CC since the user reported against the official Debian version.

Comment 2 Jan 2020-06-05 12:02:48 UTC

On Debian 10 with 6.1.5 switched to clean new system user account: Error gone.

Switched back to own account, safe-mode, reset to factory settings, reset settings and user interface modifications, reset entire user account. Complete system reboot. Error still present.

Now uninstalled 6.1.5 and installed 6.4.4. Error gone.

Comment 3 Timur 2020-06-05 12:55:31 UTC

(In reply to Jan from comment #2)
If this was confirmed it would be WFM then (fix could be found). 
But it wasn't and not clea if on empty or specific ODS,  so I set Invalid.