Bug 53176 - report builder - error when opening a report containing a chart.
Summary: report builder - error when opening a report containing a chart.
Status: RESOLVED DUPLICATE of bug 48056
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
3.5.5.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-06 17:42 UTC by Dan Lewis
Modified: 2012-08-12 07:34 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Database with the problem report (Monthly Average) (878.25 KB, application/vnd.sun.xml.base)
2012-08-06 17:42 UTC, Dan Lewis 		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 Dan Lewis 2012-08-06 17:42:38 UTC 
Created attachment 65190 [details]
Database with the problem report (Monthly Average)

I created the report using LO 3.5.5.3. I place a chart in the page footer. Then I saved the report and saved the database document file. Then when I tried to open the report, I get an error: An exception of type com.sun.star.lang.WrappedTargetException was caught. I closed the database and also closed LO 3.5.5.3. I then opened the database in LO 3.4.6. The report opened correctly. Then I tried LO 3.3.0.4. It gave me the same error as LO 3.5.5.3. Is this a regression? I am attaching the database with the problem.
Comment 1 Zoltán Reizinger 2012-08-09 17:13:01 UTC 
I can confirm it with LibO 3.5.5.3 and Libo 3.6.0 under win7. Same happened with AOO 3.4 (where the report builder bugfixing/devlopment stopped) when changes introduced in Chart module not followed change in report builder code.
Comment 2 Zoltán Reizinger 2012-08-09 17:16:05 UTC 
Confirmed.
Comment 3 Robert Großkopf 2012-08-12 07:34:44 UTC 
It doesn't work since LO 3.5, only with LO 3.3. Also it doesn't work with OOo 3.3. I have reported this some times before. So I would mark this as a duplicate.

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