Bug 133559 - Calc crashes when ungrouping charts
Summary: Calc crashes when ungrouping charts
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-31 16:58 UTC by Joaquin Marquez Bugella
Modified: 2021-06-30 03:55 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example ODS file causing the crash (15.47 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-11-28 14:02 UTC, Leyan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joaquin Marquez Bugella 2020-05-31 16:58:11 UTC
Description:
Calc crashes after ungrouping charts in a copied sheet.
Steps to reproduce:
Given that:
- Sheet 1 contains a grouped set of charts
- Make a copy of Sheet 1 (ctrl + drag&drop)
- In this copied sheet, ungroup the set of charts (right click's contextual menu on the charts group -> ungroup)
After that, a regular mouse-scrolling down makes Calc to crash

Steps to Reproduce:
1.Make a copy of a sheet that contains a grouped set of charts (method: ctrl + drag&drop)
2.Ungroup the set of charts in the copied sheet.
3.A regular mouse-scrolling down makes Calc to crash

Actual Results:
Calc crashes

Expected Results:
Being able to ungroup the set of charts and continue working, obviously to modify the charts' data sources in the new sheet (and not crashing :) )


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.4.3.2
Build ID: 1:6.4.3-0ubuntu0.20.04.1
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: es-ES (en_GB.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Julien Nabet 2020-05-31 18:34:08 UTC
Would it be possible you attach an example file?
Of course, don't forget to "sanitize" it (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission)
Comment 2 QA Administrators 2020-11-28 04:29:15 UTC Comment hidden (obsolete)
Comment 3 Leyan 2020-11-28 14:02:16 UTC
Created attachment 167637 [details]
Example ODS file causing the crash

I can reproduce it using the example file. No need to copy to a new sheet, simply ungrouping the two charts then scrolling down causes a message to appear:

LibreOffice 7.0 - Fatal Error
/build/libreoffice-fresh/libreoffice-7.0.2.2/svx/source/unodraw/unoshap2.cxx:297

However, the same file on master does not crashes so I could not get a backtrace.
Comment 4 Xisco Faulí 2020-11-30 15:06:18 UTC
I can't reproduce it in

Version: 7.2.0.0.alpha0+
Build ID: 79ec66700266a22966d9e308a716be56c9c3a4a7
CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 5 QA Administrators 2021-05-30 04:13:44 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-06-30 03:55:07 UTC
Dear Joaquin Marquez Bugella,

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