You are not logged in.
Hi all,
Just noticed this today; seems easy to replicate, just print a pdf somewhere, or download one, and attempt to open it with nautilus. I don't get a preview of what the file looks like before opening, and upon double-click, evince merely flashes up for a moment and closes. ePDFviewer has a similar effect. Deleting ~/.thumbnails/fail doesn't regenerate a preview either. Also, old pdf files keep their previews and open fine.
I'm going to blame something within the very recent gnome update. Any help with this one?
Apologies if this is somewhere else; I couldn't see anyone mention it, and it seems like an obvious bug :S
Last edited by o1911 (2010-10-07 14:55:24)
Arch x86_64
Offline
I can't replicate this. Give a link to a PDF you can't open. Do you think the problem is with evince ("Document Viewer"), with nautilus, or with your gnome-open settings?
Offline
Apologies, I am a little busy at the moment, so I can't help with fully testing things out at the moment- however, it appears that I get this problem with pdf files created with cairo. With nautilus, if you right-click -> properties -> document it will tell you the 'Creator'. I can help out a bit more in about 12 hours.
Thanks!
Arch x86_64
Offline
Such as ones you get with "print to file" from the GNOME printing menu (Producer/Creator = cairo 1.7.4 in Evince's properties tab)? I'm not having any problems with those, but I'll try again on my other GNOME machine when I get home. Anyone else see this problem?
Offline
I have the same problem. I can't open some pdf files with evince. But I don't think it's a evince problem. I tried with apvlv and both give me segmentation fault. There is a problem with some package that avoid me to open some pdf files? This start to happen, if I notice, after the upgrade of gnome related packages I think.
I can open all my pdf files in my computer and as well some of random pdfs found at internet.
This is one of the the pdf I can't open: http://www.fct.unl.pt/estudante/datas/2 … _final.pdf
I tried on debian squeeze (I have installed on a virtual machine) and I could open. That's why I think this is related somehow with the new gnome packages.
Last edited by ilusi0n (2010-10-06 18:39:33)
Offline
This is one of the the pdf I can't open: http://www.fct.unl.pt/estudante/datas/2 … _final.pdf
I tried on debian squeeze (I have installed on a virtual machine) and I could open. That's why I think this is related somehow with the new gnome packages.
So strange, i can open that pdf without problem:
http://imgur.com/vcSN6.png
And I have full update Arch + Gnome 2.32 system.
Other thing, yesterday and day before yesterday (after great gnome upgrade) evince package has 2 updates. I have: evince 2.32.0-3 and i don't have any problem with pdfs (ie Pubmed Pdfs).
"Yo creo que los muertos son tiernos. ¿Nos besamos?"
Offline
I have no trouble with opening that PDF either. (Evince 2.32.0-3 running on the newly updated GNOME.)
Evince, apvlv and ePDFviewer all rely on the poppler libraries, so it would stand to reason that the problem might lie there. Here are the poppler packages I have installed:
extra/poppler 0.14.0-1
PDF rendering library based on xpdf 3.0
extra/poppler-data 0.4.3-1
Encoding data for the poppler PDF rendering library
extra/poppler-glib 0.14.0-1
Poppler glib bindings
extra/poppler-qt 0.14.0-1
Poppler Qt bindings
local/python-poppler 0.12.1-2
Python bindings for Poppler
Last edited by frabjous (2010-10-07 03:04:32)
Offline
I cannot open the linked pdf. Also, my poppler installation appears to be identical (although I have no python-poppler):
extra/poppler 0.14.0-1 [installed]
PDF rendering library based on xpdf 3.0
extra/poppler-data 0.4.3-1 [installed]
Encoding data for the poppler PDF rendering library
extra/poppler-glib 0.14.0-1 [installed]
Poppler glib bindings
extra/poppler-qt 0.14.0-1 [installed]
Poppler Qt bindings
Arch x86_64
Offline
I cannot open the linked pdf
Really so strange. My packages:
extra/poppler 0.14.0-1 [installed]
PDF rendering library based on xpdf 3.0
extra/poppler-data 0.4.3-1 [installed]
Encoding data for the poppler PDF rendering library
extra/poppler-glib 0.14.0-1 [installed]
Poppler glib bindings
extra/poppler-qt 0.14.0-1 [installed]
Poppler Qt bindings
extra/evince 2.32.0-3 [installed] (gnome-extra)
Simply a document viewer
extra/python-evince 2.32.0-1 [installed]
and all works fine.
"Yo creo que los muertos son tiernos. ¿Nos besamos?"
Offline
I also have your version of evince superchango, not that it helps as other pdf readers also don't work. The problem must lie elsewhere. It's very frustrating booting an ubuntu vm just to look at pdfs!
Arch x86_64
Offline
That's so weird because some can open and other's not. With me with any pdf reader give me always segmentation fault. Any idea why this happens?
Last edited by ilusi0n (2010-10-07 10:23:12)
Offline
Can't believe this has gone on so long without someone asking you to run the app from a terminal and look at the error. If it only affects some pdfs perhaps its related to libpng or libjpg or similar (content which only some pdfs would have, not all).
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Can't believe this has gone on so long without someone asking you to run the app from a terminal and look at the error. If it only affects some pdfs perhaps its related to libpng or libjpg or similar (content which only some pdfs would have, not all).
I run apvlv and evince from terminal. That's why I said it gives me a segmentation fault.
Offline
ngoonee wrote:Can't believe this has gone on so long without someone asking you to run the app from a terminal and look at the error. If it only affects some pdfs perhaps its related to libpng or libjpg or similar (content which only some pdfs would have, not all).
I run apvlv and evince from terminal. That's why I said it gives me a segmentation fault.
Any useful information from the crash?
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Sorry I'm not get used to see the logs and not sure what look for. But I think is this.
Oct 7 11:21:16 localhost kernel: apvlv[6364]: segfault at 0 ip 00007f3137ebdc9a sp 00007fff11e0a958 error 4 in libc-2.12.1.so[7f3137e44000+153000]
Oct 7 11:21:24 localhost kernel: apvlv[6377]: segfault at 0 ip 00007f3a04943c9a sp 00007ffffc23abf8 error 4 in libc-2.12.1.so[7f3a048ca000+153000]
Oct 7 11:22:24 localhost dbus-daemon: [system] Reloaded configuration
Oct 7 11:22:25 localhost kernel: apvlv[6520]: segfault at 0 ip 00007f11e8ce1c9a sp 00007fffbc80b008 error 4 in libc-2.12.1.so[7f11e8c68000+153000]
Oct 7 11:26:04 localhost kernel: evince[6839]: segfault at 0 ip 00007fae9d280c9a sp 00007fae96900518 error 4 in libc-2.12.1.so[7fae9d207000+153000]
Offline
Can't believe this has gone on so long without someone asking you to run the app from a terminal and look at the error. If it only affects some pdfs perhaps its related to libpng or libjpg or similar (content which only some pdfs would have, not all).
I did try from terminal, however evince gives absolutely no output, so that's why I didn't mention it. Sorry, I should have mentioned I did this :S
Arch x86_64
Offline
I discover what was causing the segmentation fault in my case. It had to do with the fonts. I had installed freetype2-infinality from AUR. I removed it and I installed freetype2 from the repositorys. And no more segmentation fault. I can open now the pdf's I couldn't. The ones that can't open the pdf have the same package I had installed? For sure it was that the problem because for me it worked.
Last edited by ilusi0n (2010-10-07 13:10:53)
Offline
Same here. Switching to freetype2-ubuntu-2.4.3-1 from AUR solved the problem.
I posted a comment on the freetype2-infinality page on AUR informing the maintainer.
Offline
Yes, I had freetype2-infinality installed and couldn't open some pdf files. After installing freetype2, all is back to normal.
Giuseppe Borzi' - Registered Linux user #34028
Offline
Awesome, thanks guys. Hopefully whatever is the real cause can be fixed.
Arch x86_64
Offline
Awesome, thanks guys. Hopefully whatever is the real cause can be fixed.
Must be some imcompatibilty. I don't really know. And don't forget to mark as [SOLVED] this thread
Offline
Thanks for reminding me
Arch x86_64
Offline
This needs to be reported upstream to the infinality folk.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
I'm the maintainer of the aur package. Fixing it is beyond my knowledge. Please report the bug to infinality directly and let's hope it gets fixed soon.
Offline
Well, this page crashes with freetype-add-subpixel-hinting-infinality-20101004-2.patch, so I've reverted back to just using the one old Infinality patch for freetype2:
subpixel-hinting-20100903-1.patch
I also prefer:
sed -i -e "s:0x10, 0x40, 0x70, 0x40, 0x10:0x1c, 0x38, 0x55, 0x38, 0x1c:" src/base/ftlcdfil.c
Edit: And with this, the PDF mentioned above opens OK - no crash.
Last edited by brebs (2010-10-08 05:51:36)
Offline