Arch Linux

should be fixed with xbmc-13.2-4

still getting errors after update

22:10:10 T:139816785536768 ERROR: CCurlFile::FillBuffer - Failed: Timeout was reached(28)
22:10:10 T:139816785536768 ERROR: CCurlFile::CReadState::Connect, didn't get any data from stream.
22:10:12 T:139816785536768 ERROR: CCurlFile::FillBuffer - Failed: Timeout was reached(28)
22:10:12 T:139816785536768 ERROR: CCurlFile::CReadState::Connect, didn't get any data from stream.
22:10:13 T:139815748105984 ERROR: CCurlFile::FillBuffer - Failed: Timeout was reached(28)
22:10:13 T:139815748105984 ERROR: CCurlFile::CReadState::Connect, didn't get any data from stream.

strange, it was just running fine here, did a small test with the movie db and got my information

Just re-tested again this morning following the xbmc package update and issue still remains. I have same curl errors in xbmc log as above. Rolled back to curl 7.37 and working once more.

Confirm, downloading in xbmc doesn't work with curl-7.38.0-1. Downgrading to curl-7.37.1-1 fixes this issue.

also unable to use the official xbmc repos or get rss feed output

CurlFile::Open(0x7f7aa8f65c40) http://feeds.xbmc.org/updated_xbmc_addons
19:37:24 T:140164797458176 ERROR: CCurlFile::FillBuffer - Failed: Timeout

but if I click the url from the log it loads fine, either for repos or feeds

http://trac.xbmc.org/ticket/15441

Same issue. Subscribing to get updates.

The ticket I opened against xbmc has been closed, "Comment: report to curl"

Fine: https://sourceforge.net/p/curl/bugs/1426/

For me disabling ipv6 in advancedsettings made it work fine with themoviedb

@graysky: why am I not surprised? XBMC upstream has never been receptive, going all the way back to the spat between XBMP and YAMP. People complain about systemd's devs, but XBMC is probably worse.

@Ike - Yes, this too worked for me but not consistently. As a test, I rebuilt my database and found that many entries refused to download prompting me to skip and abort. Downgrading to xbmc 13.2-3 and curl 3.37.1-1 causes a database rebuild to work consistently.

it doesn't work for me even with disable ipv6. Rss, download of addons, video addons like youtube still don't work. I will test more to see if i made a mistake

EDIT: Still broken with ipv6 disable for me

Actually, this did not work consistently for me either. I will edit my previous comment to avoid confusion.

ok have to dig further then

I found the bad commit and replied to the sourceforge bug:

Hello,
Like graysky I am an Arch Linux & XBMC user with the same issue.
Like him as well, I do not know what XBMC tries to do with libcurl... but I have bisected curl to find the 'bad' commit.
This is what I found:
cacdc27f52ba7b0bf08aa57886bfbd18bc82ebfb is the first bad commit
commit cacdc27f52ba7b0bf08aa57886bfbd18bc82ebfb
Author: Daniel Stenberg daniel@haxx.se
Date: Mon Aug 25 11:34:14 2014 +0200
low-speed-limit: avoid timeout flood

Introducing Curl_expire_latest(). To be used when we the code flow only
wants to get called at a later time that is "no later than X" so that
something can be checked (and another timeout be added).

The low-speed logic for example could easily be made to set very many
expire timeouts if it would be called faster or sooner than what it had
set its own timer and this goes for a few other timers too that aren't
explictiy checked for timer expiration in the code.

If there's no condition the code that says if(time-passed >= TIME), then
Curl_expire_latest() is preferred to Curl_expire().

If there exists such a condition, it is on the other hand important that
Curl_expire() is used and not the other.

Bug: http://curl.haxx.se/mail/lib-2014-06/0235.html
Reported-by: Florian Weimer
Now just looking at the name of "Curl_expire_latest()" and the fact that XBMC logs complain about expiring, I would assume this is the correct place to look at.
(Now I don't know what is 'wrong' here, XBMC or curl...)
Please ask if you need more information.
John

same here 32bit build - rollback curl solves issue for me

Daniel Stenberg the maintainer of libcurl has fixed that regression. Please cherry-pick the patch Daniel links here: https://sourceforge.net/p/curl/bugs/1426/?limit=10&page=1#092a and update the libcurl package.

I can also confirm the patch into curl + a rebuild of xbmc against it fixes this problem.

There's really no need to recompile xbmc. It's the same soname and the same header. Rebuilding is just contributing to heating your house.

curl-7.38.0-2 in [testing] has this backport.