ubuntu recently upgraded the versions of poppler/evince that i am running. this caused some serious regressions with respect to evince's pdf rendering on several documents. i'm on breezy, but i thought i should report this right away so that it's easier to find the change that caused this to happen. the new versions are: libpoppler0 0.3.1-1, libpoppler0-glib 0.3.1-1, evince 0.3.0-2 (ubuntu package versions) jrb says "desrt: it's prolly a splash-> cairo thing. File it against poppler at freedesktop.org" two files that show regressions can be found here: http://manic.desrt.ca/cdp03 http://manic.desrt.ca/ee487 for ee487, there is a strange rectangle-inside-rectangle effect in the top left quadrant of each page (this wasn't there before). thumbnailing for ee487 also fails sometimes (ie: the thumbnails do not match the displayed content) for cdp03, gigantic parts of lots of pages are missing (again, this is a regression) cheers.
Created attachment 2668 [details] a screenshot here's a screenshot of ee487. you can see the rectangle effect in the top-left corner and the fact that page 4 doesn't match its thumbnail (this is fairly random -- last night it was page 2 that didn't match, and there was actually some visible junk on the thumbnail). something i should have mentioned also: rendering speed has decreased considerably on these two documents.
Update: cdp03 seems to be fine now. ee487 thumbnails properly (in the sense that the thumbnails are equal to small versions of the displayed content) but the displayed content is still incorrect (has the strange rectangle effect).
Ok, I'm closing this as a dupe of bug #4330, since the rectangle effect is caused by the way gradients are implemented by poppler. *** This bug has been marked as a duplicate of 4330 ***
fwiw, i don't think this is a dup of 4330 because I just checked with the latest evince/poppler and it looks fine now (ie: the problem reported here is fixed in the latest version). but either way, closed. cheers.
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.