Some time ago I've reported this bug: http://bugzilla.gnome.org/show_bug.cgi?id=324049 for evince, but I've done some more investigations and it seems, that this is a bug of the poppler lib. The attached pdf is rendered differently with the Cairo and the Splash backend: Rendered by the Splash backend the box has black borders and there is a slanting line through one edge of the box. This can be reproduce with the test-poppler-qt tool where it seems that Splash is used: ./qt/test-poppler-qt /tmp/test.pdf If the cairo backend is used: glib/test-poppler-glib file:///tmp/demo.pdf 1 display slice.png Than the box has no border and the single line is missing. The problem is, that the pdf uses a linewidth of 0.0. According to the pdf reference: (version 1.6, section: 4.3.2: "A line width of 0 denotes the thinnest line that can be rendered at device resolution: 1 device pixel wide." a line with width 0 should be visible. This works correctly with the other tested backends (e.g. Splash, Postscript), but not with the cairo backend. In the cairo backend the width is set by cairo_set_line_width. Unfortunately the cairo reference doesn't explain in detail how width = 0.0 should be handled. It seems, that the line is just not drawn.
Created attachment 4286 [details] this file is rendered differently with Cairo backend
Created attachment 4295 [details] [review] this patch fixes the problem I've mailed with the cairo people and they give me the hint, that a line width of 1/300 inch can be used for zero length postscript/pdf lines: http://lists.freedesktop.org/archives/cairo/2006-January/005976.html That's why I suggest to use the attached patch which handles the special case when the line width == 0.0.
Looks like it is caused by missing smask support.
(In reply to comment #3) > Looks like it is caused by missing smask support. ignore the comment above comment, it was meant for a different bug.
Patch comitted, thanks.
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.