GNOME Bugzilla – Bug 129400
Hangs with freetype > 2.1.5
Last modified: 2004-12-22 21:47:04 UTC
I always have this problem: 1. Click a link to a pdf file in a browser. 2. Choose open instead of save. 3. Gpdf opens the file (downloaded to /tmp) and either shows nothing and hangs or shows a small empty page and hangs. 4. After that I get the same behaviour on whatever pdf file I try to open. The hangs ("not responding", so no crashes) stop after a reboot. I'm using gpdf 0.111 from the latest dropline gnome on slack 9. Any ideas?
I made a screenshot for your viewing pleasure: http://users.pandora.be/svanimpe/Screenshot.png What I did here was just open gpdf, then select a recent file to open. As soon as I click it, the program hangs (doens't even seem to draw the menubars anymore). Same thing happens if I open a file that's not in the recent file list. After this, I can't do more than just try to close the window and wait for the "not responding" dialog to show.
Did you recently update freetype to 2.1.7?
freetype 2.1.7 is indeed part of the current dropline gnome and iirc, it's a quite recent update as well is that's what causing the problem, and if so, is there an easy solution, next to waiting for another version?
Well, easy solution is downgrading freetype :-( I don't even have a fix in CVS yet, I only started investigating this bug last weekend. GPdf extracts fonts from pdf files in a buggy way, it seems. Older freetypes didn't have a problem with that (so I never noticed), the newer ones have new PostScript parsers which is more strict.
Another question. Was the file generated by pdftex?
I can't tell you for sure, but I think most of them were (since our professors use latex for their course notes, and those are the files I download most) I did not generate any myself, that I can tell you
OK, it's a bug in freetype 2.1.7. It doesn't process the eexec keyword correctly. Cf. the ``problems with IPE'' thread here: http://www.freetype.org/pipermail/freetype/2003-December/thread.html This patch from freetype cvs fixes it for me: http://cvs.freetype.org/cgi-bin/viewcvs.cgi/freetype2/src/type1/t1load.c.diff?r1=text&tr1=1.88&r2=text&tr2=1.89&diff_format=h danielllano@terra.es/emcsqr: this was the ``freetype problem'' that I mentioned on IRC
*** Bug 135512 has been marked as a duplicate of this bug. ***
*** Bug 137263 has been marked as a duplicate of this bug. ***
*** Bug 137264 has been marked as a duplicate of this bug. ***
*** Bug 137926 has been marked as a duplicate of this bug. ***
thanks for reminding me of this one, I seem to have a similar problem again this time it's with a file I don't think is generated by pdftex, since it appears to be a scan of the suse user guide I'm using dropline gnome 2.6 (includes X.org), freetype version is 2.1.7 again
another thing I just noticed: gnome-pdf-viewer was still in the process list (though i "force quit"ed it quite some ago) and was causing bad x performance: glxgears gave me 75FPS, after I killed gnome-pdf-viewer I got over 500FPS
If it's a scanned document, it's most probably a different bug. Can you file it as a new bugzilla bug, please? And attach the file, if possible. Force quit doesn't work as one might expect for apps like gpdf, eog, ... that use bonobo controls. It kills only the part that created the window, not the part that does most of the work (i.e. gnome-pdf-viewer, eog-image-viewer). So they continue to suck up processor power until you kill them manually...
*** Bug 138704 has been marked as a duplicate of this bug. ***
*** Bug 140504 has been marked as a duplicate of this bug. ***
*** Bug 139893 has been marked as a duplicate of this bug. ***
(Debian Sarge) when I use gnome-pdf 0.131 and freetype 2.1.7 I dont have the Problem described in BUG 139893 http://bugzilla.gnome.org/show_bug.cgi?id=139893 [try to open http://www.math.uni-bonn.de/people/luetz/vv.pdf in gpdf] So it seems like BUG 139893 is not a dublicate of this one, but anyway the new version of gpdf resolves it Best Wishes Philipp Strack
I still have this problem with gpdf 0.132 and freetype 2.1.7 (using vv.pdf in comment above)
Any ideas when this will be fixed in freetype versions used by distros ? This is a reeeeaaally annoying problem making it impossible for me (and probably most other users) to view most documents, for over 8 months now. Another one that doesn't work: http://wetenschappen.ugent.be/ldo/we53/uurroosters/kandidatureninformatica.pdf
Hi everybody, I opened the document [http://wetenschappen.ugent.be/ldo/we53/uurroosters/kandidatureninformatica.pdf] without any Problem with gpdf Verison 0.131 and freetype 2.1.7 maybe the Debian version of freetype is patched what Distro are you using
that would be the latest Arch Linux (which I must say has more problems than most distros I've used) I have gpdf 0.132 and freetype 2.1.7 (freetype 1.3.1 is installed as well, not that I know why, it was a dependency for something)
philip: debian's freetype uses the patch from comment 7 (since June). steven: freetype 2.1.8 and 2.1.9 have been released. Without this problem as far as I know. Please file bugs with Arch Linux to upgrade to newer freetype (or include the patch).