Bug 60960 - EDITING: CRASH when copy CHART what is related to empty cells
Summary: EDITING: CRASH when copy CHART what is related to empty cells
Status: RESOLVED DUPLICATE of bug 60420
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: Other Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-02-16 18:39 UTC by Rainer Bielefeld Retired
Modified: 2013-02-16 18:45 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Sample Document (12.65 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-02-16 18:39 UTC, Rainer Bielefeld Retired 		Details
View All 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 Rainer Bielefeld Retired 2013-02-16 18:39:32 UTC 
Created attachment 74946 [details]
Sample Document

Has been reported on <discuss@de.libreoffice.org> ([de-discuss] [bug-per-mail] LO Calc 4.0.0 stürzt bei ab Versuch, ein Diagramm zu kopieren)  by user Jörn.

Steps how to reproduce [Reproducible] with Server Installation of "LibO  4.0.0.3   -  GERMAN UI / German Locale  [Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89)]"  {tinderbox: @6, pull time 2013-01-31 11:30(?)} on German WIN7 Home Premium (64bit) with separate  new User Profile  

1. open attached sample document
2. Single click on chart
3. <control+c> for copy
   > CRASH
Comment 1 Rainer Bielefeld Retired 2013-02-16 18:45:57 UTC 
I am pretty sure that this one is a DUP of "Bug 60420 - Copy chart leads to cras".

Reasons:
a) appearance (more or less LibO 4.0)
b) Sample for Bug 60420 also contains Chart related to empty cells
c) I reproduce the Bug here with Master 4.1 and Branch 4.0.1 until short before
   fix date 2013-02-07, all my later Builds don't crash any more

Please feel free to reopen this Bug if you find evidence that we have an independent issue here  (for example because the fix for the other bug does not work for you).

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