Comment 20 for bug 227186

> pdffonts on wrong.pdf:
> name type emb sub uni object ID
> ------------ --------- --- --- --- ---------
> [none] Type 3 yes no no 4 0
> [none] Type 3 yes no no 5 0

Note the Type3 fonts. That means that you ended up with metafont-
rendered bitmap fonts rather than type1 fonts. Specifically the
ec fonts which are typically found at:

    /usr/share/texmf-dist/fonts/source/jknappen/ec/

You may prefer to get the LatinModern fonts, outline fonts which cover
the subset of ec text-font glyphs which LaTeX uses. (The math fonts,
when using lm, are the same CM Type1 fonts your good.pdf example would
have used, had it had any math.)

That said, it is indeed a bug that evince cannot correctly handle Type3
bitmap fonts. And probably means that it also cannot handle Type3 vector
fonts.

Whether the bug is in evince, poppler, cairo is a good question.

Cairo has had some recent changes which may be relevant. Since you point
at launchpad, I presum you use Ubuntu; you, therefore, are probably using
rather old versions of poppler and cairo....