Bug 284533

Summary: Broken anti-aliasing when reloading document
Product: [Applications] okular Reporter: Martin von Gagern <Martin.vGagern>
Component: generalAssignee: Okular developers <okular-devel>
Severity: normal    
Priority: NOR    
Version: 0.13.2   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: PDF used for screenshots
Good rendering upon application startup
Bad rendering after reload

Description Martin von Gagern 2011-10-20 09:52:53 UTC
Created attachment 64726 [details]
PDF used for screenshots

Version:           0.13.2 (using KDE 4.7.2) 
OS:                Linux

When opening the attached file, it displays all right. But when reloading the document, either using the File/Reload menu item, its shortcut, or because the file changed on disk, then the lines will appear a lot thicker and more rugged. It appears as though upon reloading, every pixel that was touched during anti-aliasing was painted at full opacity, or something like that.

Reproducible: Didn't try

Steps to Reproduce:
1. Open the attached document, generated by asymptote.
2. Reload the document using File/Reload

Actual Results:  
* Lines appear a lot thicker
* Pixels are either black or white, no more gray
* At 100% zoom, the inner circles appear almost as one

Expected Results:  
Image should look exactly as it looked upon initial loading of the document

My system has poppler 0.18.0 installed.

I'll be happy to try out any patch you might suggest.
Comment 1 Martin von Gagern 2011-10-20 09:54:46 UTC
Created attachment 64727 [details]
Good rendering upon application startup

That's what the document looks like the first time I load it.
Comment 2 Martin von Gagern 2011-10-20 09:55:25 UTC
Created attachment 64728 [details]
Bad rendering after reload

And that's what it looks like after I reload the document.
Comment 3 Martin von Gagern 2011-10-20 09:57:40 UTC
(In reply to comment #0)
> Reproducible: Didn't try

Got that filled out incorrectly: in fact I can reproduce this bug perfectly well.
Comment 4 Albert Astals Cid 2011-10-20 10:14:37 UTC

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