Bug 601020 - [abrt] crash in calibre-0.6.55-1.fc13: split.py:385:split_to_size:SplitError: Could not find reasonable point at which to split: temp_calibre_txt_input_to_html.html Sub-tree size: 538 KB
Summary: [abrt] crash in calibre-0.6.55-1.fc13: split.py:385:split_to_size:SplitError:...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: calibre
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1c381c19
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-07 02:31 UTC by David Nalley
Modified: 2010-06-07 02:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-07 02:47:40 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (2.01 KB, text/plain)
2010-06-07 02:31 UTC, David Nalley 		no flags Details
View All

Description David Nalley 2010-06-07 02:31:38 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: python /usr/bin/calibre-parallel
component: calibre
executable: /usr/bin/calibre-parallel
kernel: 2.6.33.5-112.fc13.i686.PAE
package: calibre-0.6.55-1.fc13
reason: split.py:385:split_to_size:SplitError: Could not find reasonable point at which to split: temp_calibre_txt_input_to_html.html Sub-tree size: 538 KB
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Select txt file to convert to epub. 
2. Press convert
3. Get alert. 

Note I am using python-cssutils-0.9.7-0.b2.fc13.noarch from koji, but don't think this specifically calls it. 
I converted 4 txt files to epub - only one failed. It was larger than 0.5MB, the others were not, that's the only material difference I see off hand.
Comment 1 David Nalley 2010-06-07 02:31:40 UTC 
Created attachment 421699 [details]
File: backtrace
Comment 2 David Nalley 2010-06-07 02:47:40 UTC 
http://bugs.calibre-ebook.com/ticket/2818

Upstream claims this isn't a bug, and has it listed as won't fix.
Note You need to log in before you can comment on or make changes to this bug.