libreport version: 2.0.7 abrt_version: 2.0.6 cmdline: python /usr/lib/python2.7/site-packages/impressive.py -t Crossfade,FadeOutFadein,SlideDown,SlideLeft,SlideRight,SlideUp,SqueezeDown,SqueezeLeft,SqueezeRight,SqueezeUp /media/REPOS/d-preart-operacijski-sustav-linux.pdf comment: Run impressive on LuaTeX-generated PDF event_log: 2011-11-09-19:01:03> Smolt profile successfully saved executable: /usr/lib/python2.7/site-packages/impressive.py kernel: 3.1.0-7.fc16.i686 reason: impressive.py:1435:get_href:AttributeError: PDFref instance has no attribute '__getitem__' time: Wed 09 Nov 2011 06:50:27 PM CET uid: 1000 username: vedranm smolt_data: Text file, 2650 bytes backtrace: :impressive.py:1435:get_href:AttributeError: PDFref instance has no attribute '__getitem__' : :Traceback (most recent call last): : File "/usr/lib/python2.7/site-packages/impressive.py", line 2016, in RenderThread : ParsePDF(pdf) : File "/usr/lib/python2.7/site-packages/impressive.py", line 1536, in ParsePDF : for page, annots in pdf.GetHyperlinks().iteritems(): : File "/usr/lib/python2.7/site-packages/impressive.py", line 1449, in GetHyperlinks : a = filter(None, map(self.get_href, self.annots[page])) : File "/usr/lib/python2.7/site-packages/impressive.py", line 1435, in get_href : action = node['A']['S'] :AttributeError: PDFref instance has no attribute '__getitem__' : :Local variables in innermost frame: :dest: None :node: {'A': PDFref(60), 'F': 4, 'Border': [0, 0, 0], 'Subtype': 'Link', 'Type': 'Annot', 'Rect': [137.009, 304.156, 233.624, 333.881]} :self: <__main__.PDFParser instance at 0xa3726ec> :obj: 70
Created attachment 532628 [details] File: smolt_data
Package: impressive-0.10.3-6.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- Doing a PDF presentation, probably clicking on a PDF link
Contacting upstream. Vedran: Is this reproducible? Can you share the pdf (maybe privately)?
That's a specialty in the PDF file: It uses a reference in a place where Impressive doesn't expect one. Having a copy of such a broken PDF file would be very useful while fixing the bug, is there any chance I can get one?
Created attachment 536746 [details] PDF that triggers the issue
Sure, it's not private. It was made by ConTeXt and LuaTeX; if it's a bug on their side, I'm pretty sure they would be willing to hear it.
I'm pretty certain that it's not a bug on ConTeXt's or LuaTeX's side. In PDF, references are allowed (almost) everywhere, it's just that Impressive's parser doesn't deal properly with them in some places. It should fixed in upstream SVN now.
impressive-0.10.3-7.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/impressive-0.10.3-7.fc16
impressive-0.10.3-7.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/impressive-0.10.3-7.fc15
impressive-0.10.3-7.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/impressive-0.10.3-7.fc14
impressive-0.10.3-7.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/impressive-0.10.3-7.el6
Package impressive-0.10.3-7.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing impressive-0.10.3-7.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2011-5102/impressive-0.10.3-7.el6 then log in and leave karma (feedback).
impressive-0.10.3-7.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
impressive-0.10.3-7.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
impressive-0.10.3-7.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
impressive-0.10.3-7.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.