Bug 48717 - EDITING soffice.bin crashed with SIGSEGV in chart::SplineCalculater::CalculateBSplines()
Summary: EDITING soffice.bin crashed with SIGSEGV in chart::SplineCalculater::Calculat...
Status: RESOLVED DUPLICATE of bug 47632
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
3.5.0 Beta2
Hardware: x86 (IA32) Linux (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-14 18:40 UTC by Chris Peñalver
Modified: 2012-04-16 09:26 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Peñalver 2012-04-14 18:40:54 UTC 
Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/920441

1) lsb_release -rd
Description:    Ubuntu precise (development branch)
Release:    12.04

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.5.2-2ubuntu1
  Candidate: 1:3.5.2-2ubuntu1
  Version table:
 *** 1:3.5.2-2ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen in LibreOffice Calc via the Terminal:
cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/920277/+attachment/2688295/+files/testing.ods && localc -nologo testing.ods

click sheet graph -> double click the graph -> secondary click the graph -> click Chart type -> button Properties... -> radio button B-Spline -> button OK -> button OK and is it does not crash.

4) What happens instead is it crashes consistently.
Comment 1 Markus Mohrhard 2012-04-15 16:22:44 UTC 
Should be fixed in 3.5.2. It is a duplicate of another bug but I no longer remember the bug number.
Comment 2 Chris Peñalver 2012-04-15 16:46:52 UTC 
Markus Mohrhard, I'm a little confused as this is reproducible in 3.5.2. Do you have a commit that was/is supposed to address this exact issue?
Comment 3 Markus Mohrhard 2012-04-16 09:25:54 UTC 
Fix did not make it into 3.5.2 and will be in 3.5.3. Sorry mixed this with another fix.
Comment 4 Markus Mohrhard 2012-04-16 09:26:26 UTC 

*** This bug has been marked as a duplicate of bug 47632 ***