Hide Forgot
Description of problem: Since the last update from 0.7.38 to 0.7.44, the convert process stopped working. Version-Release number of selected component (if applicable): 0.7.44 How reproducible: Every time I'm trying to convert a single book Steps to Reproduce: 1.Highlight a book 2.Press the conversion button 3. Actual results: The CPU usage skyrockets to 100%, the program remains unresponsive Expected results: The conversion dialogue to open Additional info: My guess: they've bumped the python compatibility version to 2.7, while it's still 2.6.4 in f13. May be this is the problem...
The command line utility ebook-convert works just fine, so the problem could be with the dialogue window itself.
With 0.7.45, calibre requires a newer sip to build than is available in f13/f14, so thats why I haven't updated my repo further. ;( I have 0.7.45 there now, can you try that one? I'll otherwise see if I can track this down...
Sorry, same results with the new one also. Can I get a backtrace of it somehow? Tried to run it with 'calibre-debug -g', but had no reasonable debug info out of it...
Well, you can attach to it with gdb and see if it can tell you something, or perhaps easier, kill -11 pidofcalibre and abrt might pick up the crash and get a trace.
I'm having a similar problem when trying to convert from any format into .mobi. As soon as I select .mobi for output, it freezes. If I have .mobi selected as my default output source, calibre freezes as soon as I select a book and choose convert, before the conversion page even opens.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.