Bug 52584

Summary: VIEWING: Pie chart with gradient filling rendered without anti-aliasing
Product: LibreOffice Reporter: Alexander Wilms <f.alexander.wilms>
Component: ChartAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: LibreOffice
Priority: medium    
Version: 3.6.0.0.beta2   
Hardware: Other   
OS: All   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: A document containing such a diagram

Description Alexander Wilms 2012-07-27 13:05:08 UTC
Created attachment 64777 [details]
A document containing such a diagram

Problem description: 



Steps to reproduce:
1. Create a pie chart
2. Apply a gradient to a segment
3. Leave LO Chart by clicking somewhere in the document

Current behavior:

The edge is partly jagged

Expected behavior:

It should always be anti-aliased

Platform (if different from the browser): 
              
Ubuntu 12.04 64 bit
Comment 1 Thomas Hackert 2012-09-02 14:38:42 UTC
Hello Fabian, *,
I can confirm your bug with (parallel installed) LOdev Version 3.6.2.0+ (Build ID: c3148ae) and installed LO Version 3.6.1.2 (Build ID: e29a214), both with Germanophone UI/Help pack, under Debian Testing AMD64 ... :( Interestingly, it seems, that is only the left side, which looked somehow as painted by hand ... ;)
Which graphics card/chip and which driver are you using? I have an NVidia GeForce 6150SE nForce 430/integrated/SSE2 graphics chip w/ nvidia-glx 302.17-3, KDE 4.8.4-1, and graphics acceleration enabled ... ;)
HTH
Thomas.
Comment 2 Alexander Wilms 2012-09-02 16:45:52 UTC
I'm using Version 3.6.2.0+ (Build ID: c3148ae) with English UI. The output of lshw -C display is  RS880M [Mobility Radeon HD 4200 Series] and I use the default open source driver.
Comment 3 Mike Kaganski 2012-10-08 02:44:45 UTC
Reproducible with LO 3.6.1.2 under Windows 7 x64
Comment 4 Rainer Bielefeld Retired 2012-12-03 06:32:52 UTC
It seems that Bug 52585 has been created as a clone of this one accidently? I can't see any difference. So INVALID!

@reporter:
Please feel free to reopen this Bug if you find evidence that we have an independent issue here.