Bug 157701

Summary: LibreOffice Calc crashes when trying to apply formatting to entire row
Product: LibreOffice Reporter: dennis <djvg>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: normal CC: buzea.bogdan, ilmari.lauhakangas, raal, stephane.guillou
Priority: medium    
Version: 7.6.2.1 release   
Hardware: All   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description dennis 2023-10-11 15:02:02 UTC
Description:
Calc crashes every time if I try to apply conditional formatting to an entire row. This happens even in an empty spreadsheet.

Sometimes, Calc also crashes if I try to apply e.g. bold font to an entire row.
(this happened several times in spreadsheets with approx 400 rows and 40 columns of data)

Steps to Reproduce:
1.open a new (empty) Calc spreadsheet
2.select a row by clicking on a row number
3.click on Conditional -> Condition in menu bar, use defaults: "Cell value", "Is equal to", 0
4.click OK


Actual Results:
at first nothing seems to happen (condition dialog remains in place)...
then a "not responding" dialog appears, with options "force-quit" and "wait"...
then a second not responding dialog appears...
regardless of whether I click Wait or do nothing, Calc simply closes after some time, and any work is lost

Expected Results:
I would expect (conditional) formatting to be applied where applicable, without problems


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 9d0b4c0791fc17bc4181a67fd90c5aaed576d1c0
CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Kira Tubo 2023-10-13 02:46:54 UTC
Not reproduced on Windows. Linux-only bug, maybe? 

Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 2 raal 2023-10-13 17:17:51 UTC
No repro with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9f44f9fad759dea644356b67b9cd0fab030e8b77
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded
Comment 3 dennis 2023-10-17 10:20:25 UTC
Not sure if this helps, but I'm on Ubuntu 22.04.3 LTS, GNOME 42.9, using Wayland, in a dual screen setup.

Before posting the issue, I was able to reproduce the issue more than 10 times in a row, and Calc would crash every single time, after waiting some 5-10 seconds. 

Today I tried again, multiple times, also after reboot, and the "not responding" dialogs *do* appear every time, but Calc does *not* crash/close completely every time. Sometimes the "not responding" dialogs disappear after approx. 5 seconds, and I can proceed normally, other times Calc does crash completely after approx. 5 seconds. On very few occasions, the "not responding" dialog only appeared on the Condition window, not on the main window. I tried, but cannot find a pattern here.

Regardless of whether the complete Calc crash occurs, even the appearance of the "not responding" dialogs and the several second delay are inconvenient.

I attempted to take a screenshot while the "not responding" dialogs were visible. That caused some kind of ubuntu crash, closing apps that were open at the time (Calc, Firefox) and logging me out.

I also tried a fresh install of LibreOffice on Windows 10, and the issue does not arise there (at least not in the ten times I tried to reproduce it.)

Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 9d0b4c0791fc17bc4181a67fd90c5aaed576d1c0
CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 4 BogdanB 2023-10-17 19:17:42 UTC
No problem with
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 5 BogdanB 2023-10-17 19:21:00 UTC
Also I filled 586 rows and until FT column with data, and I selected a whole row, and bold, and I have a 1 second working process, than all is done. No freeze.

Ubuntu 22.04.3
64
42.9
X11
Comment 6 Buovjaga 2023-10-27 13:43:49 UTC
No problem here.

Arch Linux 64-bit, X11
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 60(Build:1)
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
7.6.2-3
Calc: threaded
Comment 7 Stéphane Guillou (stragu) 2023-10-27 15:34:30 UTC
No issue here either on Ubuntu 20.04 + GNOME + Wayland + 2 monitors:

Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Can you please check if the issue is not reproduced:
- after installing all system updates
- without gtk3, for example using from the command line:
SAL_USE_VCLPLUGIN=gen libreoffice7.6
- in x11 (use Ubuntu on XOrg when logging in)
Comment 8 QA Administrators 2024-04-25 03:16:28 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2024-05-26 03:15:06 UTC
Dear dennis,

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-FollowUp