Red Hat Bugzilla – Bug 615602
xkcd recipe non-functional in 0.7.8-1
Last modified: 2011-01-22 15:32:32 EST
Description of problem:
xkcd recipe fails with
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 22: ordinal not in range(128)
Version-Release number of selected component (if applicable):
because of Bug 598079 I have these two scratch builds installed.
Steps to Reproduce:
1. update to the scratch builds from https://bugzilla.redhat.com/show_bug.cgi?id=598079#c12
2. attempt to use the built-in xkcd recipe
ERROR: Conversion Error
xkcd EPUB created
Created attachment 432574 [details]
full error output from calibre
Looking at this, it may be there is nothing to convert?
Is there any other feed you can test?
"Skipping article Blogging (Mon, 17 May, 2010 00:00) from feed xkcd as it is too old." seems to be the newest skipped article.
http://xkcd.com/archive/ has 26 newer ones at this moment.
Can't seem to reproduce this on F12, or 13 at the moment.
What I have done is gone into:
Fetch News > Schedule News > English (added all non user\pw\ ones) to schedule)
Then clicked "download now"
And all opened when highlighted, view clicked.
Can you guide me through the steps you took?
In response to Comment #4
I do this;
Fetch News > Schedule News > search 'xkcd'
when search completed, trigger download.
Your steps should have given you xkcd too as it is under English.
Can you verify you did grab xkcd and can you verify that your target format was epub (I suspect the latter might make a difference)
Doing it as #5 did get the same crash.
If you need xkcd at the moment try adding:
as a custom news service.
Just tested and it didn't crash,
will check upstream for similar.
Thank for the help Patrick.
This is purely a Fedora Bug, upstream install does *not* have this bug
(Tested on F13)
Similar upstream bugs were previously closed "worksforme"
Bug also exists on F12.
Rawhide version of this bug:
xkcd feed is ok in itself,
tested in Liferea.
Right. The problem here is that one of the xkcd titles is UTF8, and the debug output where it says it's not taking something because it's so old can't understand the UTF8 title and blows up.
I don't know why yet the upstream version doesn't show this. It could be a customization they have in their local cssutils. I can look at reporting it upstream or trying to make a patch.
I see this too. My feeds for Open Left, LWN, and The Nation fail as well, with similar looking errors.
http://xkcd.com/archive/ fails also.
My local repo at http://www.scrye.com/~kevin/fedora/calibre/ has 0.7.10 if you want to try that and confirm that it's still not working there?
Confirmed, still not working.
Can confirm as well that
does not fix the problem
As of F-14, this works.
Excellent. That means the one in my repos fixes it for f13 as well hopefully.
Can anyone confirm?
(In reply to comment #16)
> Excellent. That means the one in my repos fixes it for f13 as well hopefully.
> Can anyone confirm?
Confirmed with 7.29 on F13 guest
I can also confirm that on F14 with
the bug is fixed.
ok. Now to see if I can get a f13/f14 update out. Thanks for the testing.
calibre-0.7.38-3.fc14,python-cssutils-0.9.7-1.fc14 has been submitted as an update for Fedora 14.
calibre-0.7.38-3.fc13,python-cssutils-0.9.7-1.fc13 has been submitted as an update for Fedora 13.
calibre-0.7.38-3.fc13, python-cssutils-0.9.7-1.fc13 has been pushed to the Fedora 13 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 python-cssutils'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/calibre-0.7.38-3.fc13,python-cssutils-0.9.7-1.fc13
calibre-0.7.38-3.fc13, python-cssutils-0.9.7-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
calibre-0.7.38-3.fc14, python-cssutils-0.9.7-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.