After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 321828 - does not render -> full CPU usage
does not render -> full CPU usage
Status: RESOLVED DUPLICATE of bug 314847
Product: evince
Classification: Core
Component: general
0.4.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-11-18 20:13 UTC by Willi Mann
Modified: 2006-02-22 01:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Willi Mann 2005-11-18 20:13:00 UTC 
Distribution/Version: debian - evince_0.4.0-1

Just open

http://www.we.fh-osnabrueck.de/fbwe/vorlesung/edv2/skript4.pdf

with evince. Note that gpdf doesn't show any content either, but at least it
doesn't burn my CPU.
Comment 1 Willi Mann 2005-11-18 20:14:03 UTC 
BTW: xpdf, kpdf both work (display content without any delays)
Comment 2 Julian Lamb 2005-12-07 03:26:54 UTC 
This file seems to open ok for me with poppler 0.4.1.  What version of poppler
are you using (check the "Help-->About" menu on Evince)?
Comment 3 Willi Mann 2005-12-07 09:28:09 UTC 
poppler 0.4.2 (cairo)
$ LANG=C dpkg -l *poppler* | grep ^ii
ii  libpoppler0c2      0.4.2-1        PDF rendering library
ii  libpoppler0c2-glib 0.4.2-1        PDF rendering library (GLib-based shared lib
Comment 4 Willi Mann 2005-12-07 09:32:05 UTC 
An additional note: it seems, that evince does render it, but it needed 2
minutes for just the first page, and that in a something that seems like a very
raw form. I did not test further pages, the sound of my laptop with full cpu
usage is not very nice. :-)
Comment 5 Priit Laes (IRC: plaes) 2006-02-19 14:08:42 UTC 
Confirming with evince 0.5.0 with Cairo-enabled poppler 0.5.0.
Could be a dup of bug #331374
Comment 6 Nickolay V. Shmyrev 2006-02-22 01:05:43 UTC 
Thanks for reporting this, it looks like latex interoperation problem, let's discuss it in a single place.

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