I reproduce this bug: some black squares overlap textual content. I
cannot provide you the document. This is a bill containing private
information from a water provider.
I have the same result using evince, gimp, nautilus, xournal.
I have no problem using xpdf, emacs, ghostscript.
result of
Control: severity -1 grave
Control: found -1 0.18.4-6
Moving to grave, since I cannot even read the PDF (PDF are generated
by a bank application, which makes those PDF pretty much useless with
evince).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
On 2014-04-07 11:09, Mathieu Malaterre wrote:
Control: severity -1 grave
Control: found -1 0.18.4-6
This found contraddicts what the reporter says in message #15, so
either you are trying with a different document or the reporter is not
providing correct information.
Moving to grave, since I
Control: reassign -1 evince
Control: found -1 3.4.0-3.1
Control: severity -1 important
On Mon, Apr 7, 2014 at 5:37 PM, Pino Toscano p...@debian.org wrote:
On 2014-04-07 11:09, Mathieu Malaterre wrote:
Control: severity -1 grave
Control: found -1 0.18.4-6
This found contraddicts what the
On 2014-04-07 18:00, Mathieu Malaterre wrote:
Control: reassign -1 evince
Control: found -1 3.4.0-3.1
Control: severity -1 important
On Mon, Apr 7, 2014 at 5:37 PM, Pino Toscano p...@debian.org wrote:
On 2014-04-07 11:09, Mathieu Malaterre wrote:
Control: severity -1 grave
Control: found -1
I am not seeing the issue using xpdf BTW. So *if* this issue is within
poppler, this is not within the original xpdf codebase.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
The initial bug seems to be fixed as of evince 3.4.0-3.1 / libpoppler19
0.18.4-6 in a system running Debian Jessie.
At least, the files are now displayed properly, both directly in evince
and looking at the thumbnails in nautilus.
When launching evince from the command line, I still get the
I have continued debugging the problem. It appears it is really linked
to loading the LCL1Medium type1 font which is embedded into the file (it
is object 32 in the file I transformed with qpdf).
The analysis of the font starts correctly (parsing header
%!PS-AdobeFont-1.0: LCL1Medium, ignoring a
8 matches
Mail list logo