abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: python /usr/bin/pdfmanipulate crop -o ProgrammingGroundUp-1-0-cropped.pdf -b bounding ProgrammingGroundUp-1-0-booksize.pdf component: calibre executable: /usr/bin/pdfmanipulate kernel: 2.6.32.11-99.fc12.x86_64 package: calibre-0.6.42-1.fc12 reason: crop.py:105:crop_pdf:TypeError: __init__() got an unexpected keyword argument 'title' release: Fedora release 12 (Constantine) comment ----- The book I was using can be downloaded at http://savannah.nongnu.org/files/?group=pgubook How to reproduce ----- 1. Have Ghostscript analyze pdf bounding box: $ gs -dSAFER -dNOPAUSE -dBATCH -sDEVICE=bbox ProgrammingGroundUp-1-0-booksize.pdf 2> bounding 2. Use pdfmanipulate to crop the pages using the 'bounding' output from above command: $ pdfmanipulate crop -o ProgrammingGroundUp-1-0-cropped.pdf -b bounding ProgrammingGroundUp-1-0-booksize.pdf
Created attachment 406225 [details] File: backtrace
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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?
calibre-0.6.55-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/calibre-0.6.55-1.fc12
calibre-0.6.55-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update calibre'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/calibre-0.6.55-1.fc12
Package: calibre-0.6.42-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. pdfmanipulate crop -o outfile.pdf infile.pdf 2. 3.
calibre-0.6.55-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.