Bug 36107

Summary: Base ReportBuilder: Background other than "color" non-functional
Product: LibreOffice Reporter: pierre-yves samyn <pierre-yves.samyn>
Component: DatabaseAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium CC: iplaw67, lionel, serval2412, zreizinger
Version: 3.3.2 release   
Hardware: Other   
OS: Windows (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 61723    
Attachments: Chart in edit mode
Chart in open mode
Sample database

Description pierre-yves samyn 2011-04-09 23:38:05 UTC
Created attachment 45449 [details]
Chart in edit mode

Hello

My environment: XP - 3.3.2 Libo
Reproduced on Vista

Steps to reproduce:

Database: Create a report with the report builder and include a diagram.
Set a background other than "color" to the chart wall or chart area (gradient, hatching, bitmaps).

OK in edit mode
Open or preview the report: the effect is lost, transformed into gray or black

View attachments and Gradient4_EditMode.png Gradient4_OpenMode.png


Note

However, some bitmap as "Fiery"  are well reproduced (see sample database attached)

Search through the bugs on "gradient" gives these results:
https: / / bugs.freedesktop.org / show_bug.cgi? id = 33591
https: / / bugs.freedesktop.org / show_bug.cgi? id = 35681

But as they seem more focused on transparency and "Presentation", I preferred to create another report ...

Cordially
Comment 1 pierre-yves samyn 2011-04-09 23:38:38 UTC
Created attachment 45450 [details]
Chart in open mode
Comment 2 pierre-yves samyn 2011-04-09 23:39:14 UTC
Created attachment 45451 [details]
Sample database
Comment 3 Zoltán Reizinger 2011-05-09 23:20:21 UTC
Same happens in OOo 3.4beta.
Comment 4 ribotb 2011-06-18 02:34:34 UTC
Hi, Pierre-Yves

I reproduce with LibO 341 (under Windows 7 SP1).

Bernard
Comment 5 Björn Michaelsen 2011-12-23 12:04:39 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 6 pierre-yves samyn 2011-12-24 03:40:03 UTC
Hello

Still persists with LOdev 3.5.0beta2+ Build ID: 62b9587-7ef74e0-7bf1c81

Worse, even the version that worked before no longer works.
Comment 7 Julien Nabet 2014-08-31 13:08:56 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce this.

I noticed these kind of console logs:
warn:chart2:3317:1:chart2/source/view/main/PropertyMapper.cxx:117: Exception caught. Type: N3com3sun4star3uno9ExceptionE, Message: 
warn:svx.uno:3317:1:svx/source/svdraw/svdobj.cxx:3002: a UNO shape took over an SdrObject previously owned by another UNO shape!
warn:legacy.osl:3317:1:embeddedobj/source/general/docholder.cxx:1161: Just a disaster...
warn:dbaccess:3317:1:dbaccess/source/core/api/RowSetBase.cxx:211: ORowSetBase::getValue: Illegal call here (we're before first or after last)!
warn:dbaccess:3317:1:dbaccess/source/core/api/RowSetBase.cxx:1192: firePropertyChange: Exception on column 0
warn:dbaccess:3317:1:dbaccess/source/core/api/RowSetBase.cxx:211: ORowSetBase::getValue: Illegal call here (we're before first or after last)!
warn:dbaccess:3317:1:dbaccess/source/core/api/RowSetBase.cxx:1192: firePropertyChange: Exception on column 1
août 31, 2014 2:49:25 PM org.pentaho.reporting.libraries.xmlns.parser.AbstractXmlReadHandler startElement

I wonder if there could be different problems here.
Comment 8 Alex Thurgood 2015-01-03 17:40:42 UTC
Adding self to CC if not already on

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.