Version-Release number of selected component: calibre-0.9.8-1.fc18 Additional info: cmdline: python2 /usr/bin/calibre-parallel executable: /usr/bin/calibre-parallel kernel: 3.7.6-201.fc18.x86_64 uid: 1000 Truncated backtrace: split.py:410:split_to_size:SplitError: Could not find reasonable point at which to split: index.html Sub-tree size: 603 KB Traceback (most recent call last): File "/usr/bin/calibre-parallel", line 20, in <module> sys.exit(main()) File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 185, in main result = func(*args, **kwargs) File "/usr/lib64/calibre/calibre/gui2/convert/gui_conversion.py", line 31, in gui_convert_override override_input_metadata=True) File "/usr/lib64/calibre/calibre/gui2/convert/gui_conversion.py", line 25, in gui_convert plumber.run() File "/usr/lib64/calibre/calibre/ebooks/conversion/plumber.py", line 1156, in run self.opts, self.log) File "/usr/lib64/calibre/calibre/ebooks/conversion/plugins/epub_output.py", line 184, in convert split(self.oeb, self.opts) File "/usr/lib64/calibre/calibre/ebooks/oeb/transforms/split.py", line 58, in __call__ self.split_item(item) File "/usr/lib64/calibre/calibre/ebooks/oeb/transforms/split.py", line 68, in split_item self.max_flow_size, self.oeb, self.opts) File "/usr/lib64/calibre/calibre/ebooks/oeb/transforms/split.py", line 213, in __init__ self.split_to_size(tree) File "/usr/lib64/calibre/calibre/ebooks/oeb/transforms/split.py", line 417, in split_to_size self.split_to_size(tree) File "/usr/lib64/calibre/calibre/ebooks/oeb/transforms/split.py", line 417, in split_to_size self.split_to_size(tree) File "/usr/lib64/calibre/calibre/ebooks/oeb/transforms/split.py", line 410, in split_to_size raise SplitError(self.item.href, root) SplitError: Could not find reasonable point at which to split: index.html Sub-tree size: 603 KB Local variables in innermost frame: split_point: None tree: <lxml.etree._ElementTree object at 0x594b290> self: <calibre.ebooks.oeb.transforms.split.FlowSplitter object at 0x5945250> root: <Element {http://www.w3.org/1999/xhtml}html at 0x4371050> before: True
Created attachment 698783 [details] File: backtrace
Created attachment 698784 [details] File: core_backtrace
Created attachment 698785 [details] File: environ
What were you doing when this happened? Can you duplicate it?
In the next few days there will be a newer calibre version available in updates-testing. Can you try: 'yum --enablerepo=updates-testing update calibre' and try and duplicate the problem with the new version? Thanks.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.