Bug 549261 - [abrt] calibre-0.6.26-1.fc12 - No Xref table in PDF
Summary: [abrt] calibre-0.6.26-1.fc12 - No Xref table in PDF
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: calibre
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8d0e65b0
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-21 04:33 UTC by Bill C. Riemers
Modified: 2010-12-04 01:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 01:24:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (700 bytes, text/plain)
2009-12-21 04:33 UTC, Bill C. Riemers
no flags Details

Description Bill C. Riemers 2009-12-21 04:33:21 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Attempted to convert the pdf for mindwarp to epub
2.
3.

Comment: calibre seems to trigger the reporting tool VERY frequently.  In most cases, such as this one, no error message is presented to the user, and the opperation appears to complete successfully.

backtrace
-----
Summary: TB8d0e65b0 __init__.py:130:set_metadata_:ValueError: No XRef table was found in the PDF file.

Traceback (most recent call last):
  File "/usr/bin/calibre-parallel", line 18, in <module>
    sys.exit(main())
  File "/usr/lib/calibre/calibre/utils/ipc/worker.py", line 89, in main
    result = func(*args, **kwargs)
  File "/usr/lib/calibre/calibre/utils/podofo/__init__.py", line 130, in set_metadata_
    p.open(path)
ValueError: No XRef table was found in the PDF file.

Local variables in innermost frame:
p: <podofo.PDFDoc object at 0xb77a6800>
path: /tmp/calibre_0.6.26_U7V6vm_podofo.pdf
title: Doctor Who Mindwarp
bkp: calibre (0.6.26) [http://calibre-ebook.com]
authors: [u'Unknown']

cmdline: python /usr/bin/calibre-parallel 
component: calibre
executable: /usr/bin/calibre-parallel
kernel: 2.6.31.6-166.fc12.i686.PAE
package: calibre-0.6.26-1.fc12
uuid: 8d0e65b0

Comment 1 Bill C. Riemers 2009-12-21 04:33:23 UTC
Created attachment 379553 [details]
File: backtrace

Comment 2 Zak 2010-03-28 07:09:45 UTC

How to reproduce
-----
1. 
2.
3.


Comment
-----
Tried sending a document with unicode title to the Iliad ebook reader.

Comment 3 Ionuț Arțăriși 2010-03-28 09:14:35 UTC
Hi, Zak

Did you get the same error as Bill above? That doesn't seem to be caused by unicode titles. 

Was did bug reported from abrt? I can't see a backtrace.

Also, what version of calibre are you using?

Comment 4 Ionuț Arțăriși 2010-04-13 13:04:31 UTC

How to reproduce
-----
1. Add http://www.socialsecurity.gov/online/ssa-545.pdf to the library
2. Try sending it to the ereader
3. file arrives to the ereader and is readable, but calibre emits a traceback


Comment
-----
Yay, I reproduced it!

Comment 5 Ionuț Arțăriși 2010-04-13 13:10:12 UTC
And here's the traceback that's a bit different from the original, but abrt chose not to send:

__init__.py:130:set_metadata_:ValueError: A object was expected but not found.

Traceback (most recent call last):
  File "/usr/bin/calibre-parallel", line 19, in <module>
    sys.exit(main())
  File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 98, in main
    result = func(*args, **kwargs)
  File "/usr/lib64/calibre/calibre/utils/podofo/__init__.py", line 130, in set_metadata_
    p.open(path)
ValueError: A object was expected but not found.

Local variables in innermost frame:
p: <podofo.PDFDoc object at 0x7f799a357678>
path: '/tmp/calibre_0.6.42_1TgIi__podofo.pdf'
title: u'Plan to Achieve Self-Support'
bkp: None
authors: [u'SSA']

Comment 6 Fedora Admin XMLRPC Client 2010-05-13 04:25:12 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Kevin Fenzi 2010-05-23 20:44:40 UTC
Greetings.

I have created a test build of the latest calibre version for Fedora 12.

Can you please update from:             
http://koji.fedoraproject.org/koji/taskinfo?taskID=2204259

And see if you can reproduce this bug?

Comment 8 Kevin Fenzi 2010-06-22 01:59:50 UTC
The above update is now in f12 updates. Can you 'yum update' and see if you can reproduce this issue with the current version?

Comment 9 Bug Zapper 2010-11-04 02:53:21 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Bug Zapper 2010-12-04 01:24:55 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.