Page 2 of 2

Re: Deluge 1.3.0 cannot load some torrents

Posted: Tue Feb 08, 2011 10:01 pm
by Cas
That is the not the right libtorrent, there are two different ones and you need libtorrent-rasterbar for Deluge.

Re: Deluge 1.3.0 cannot load some torrents

Posted: Wed Feb 09, 2011 2:16 am
by pblue388
It seems quite complicated to build libtorrent-rasterbar as it cannot be installed by yum.

Is there any simple way to install it? It seems that prior version of Deluge does not need this. I hope Deluge can be more user friendly - that is, after installation, we can run it.

Re: Deluge 1.3.0 cannot load some torrents

Posted: Wed Feb 09, 2011 7:55 am
by Cas
Sorry I really can't help any further.

I suggest you speak to the Fedora Deluge package maintainer and ask them about a newer build of libtorrent-rasterbar.

Re: Deluge 1.3.0 cannot load some torrents

Posted: Wed Feb 09, 2011 8:08 am
by pblue388
Thanks and maybe this is out of my expection to spend the time on it.

Maybe I will wait for the release of Fedora 15 to see if the same problem can be solved. It seems that Deluge is not actively involved in working closely with Fedora but more with Ubuntu.

I will try to see if Transmission can do the job better.

Re: Deluge 1.3.0 cannot load some torrents

Posted: Wed Feb 09, 2011 8:16 am
by Cas
Deluge does not favour any distro. The deluge developers simply provide the source code and it is up to the package maintainers to create the application for each distros.

That is why I am asking you to speak to the person that builds the Fedora package.

Re: Deluge 1.3.0 cannot load some torrents

Posted: Wed Feb 09, 2011 8:28 am
by pblue388
I see but this request is not supposed to do by an ordinary user. I am just an ordinary user simply want to use the software and did not expect to do so much to use it.

I believe it should be Deluge team's responsibility to cooperate with the distribution team to make it more user friendly. If Deluge needs that lib, it should incorporate into it instead of assuming the user can have the capability to add it. I as an oridinary user can only use "yum" to install software as yum will take care of all the dependencies. May the team can work better with the yum team to have yum update the necessary lib each time yum is installing deluge.

Re: Deluge 1.3.0 cannot load some torrents

Posted: Wed Feb 09, 2011 8:56 am
by Cas
For 99% of the users of Fedora, Deluge works fine.

Deluge uses libtorrent-rasterbar, it is named rb-libtorrent on Fedora but it will be installed. I was simply asking if you could use a newer version.

The fact that your disto package maintainers have not built the latest versions of either Deluge 1.3.1 or rb-libtorrent 0.15.5 (or even 0.14.12) is not our responsibility. The source code is available here and here respectively.


https://admin.fedoraproject.org/pkgdb/a ... libtorrent
https://admin.fedoraproject.org/pkgdb/acls/name/deluge

Re: Deluge 1.3.0 cannot load some torrents

Posted: Wed Feb 09, 2011 10:15 am
by pblue388
Tried to installed rb_libtorrent but the latest version available for Fedora 14 is only 0.14.11.

The scenario is the same.

Error message are as below and I am not sure if there is more clues for you:

# deluged
# deluge-web &

[1] 2058
# [ERROR ] 18:03:26 json_api:223 Error calling method `web.get_host_status`
[ERROR ] 18:03:26 json_api:224 'NoneType' object is not iterable
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 215, in _handle_request
result = self._exec_local(method, params, request)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 182, in _exec_local
return meth(*params)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 716, in get_host_status
(host_id, host, port, user, password) = self.get_host(host_id)
TypeError: 'NoneType' object is not iterable
[ERROR ] 18:03:26 json_api:223 Error calling method `web.get_host_status`
[ERROR ] 18:03:26 json_api:224 'NoneType' object is not iterable
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 215, in _handle_request
result = self._exec_local(method, params, request)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 182, in _exec_local
return meth(*params)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 716, in get_host_status
(host_id, host, port, user, password) = self.get_host(host_id)
TypeError: 'NoneType' object is not iterable
[ERROR ] 18:03:26 json_api:223 Error calling method `web.get_host_status`
[ERROR ] 18:03:26 json_api:224 'NoneType' object is not iterable
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 215, in _handle_request
result = self._exec_local(method, params, request)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 182, in _exec_local
return meth(*params)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 716, in get_host_status
(host_id, host, port, user, password) = self.get_host(host_id)
TypeError: 'NoneType' object is not iterable
[ERROR ] 18:03:26 json_api:223 Error calling method `web.get_host_status`
[ERROR ] 18:03:26 json_api:224 'NoneType' object is not iterable
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 215, in _handle_request
result = self._exec_local(method, params, request)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 182, in _exec_local
return meth(*params)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 716, in get_host_status
(host_id, host, port, user, password) = self.get_host(host_id)
TypeError: 'NoneType' object is not iterable

# [ERROR ] 18:04:38 json_api:265 'utf8' codec can't decode byte 0xb5 in position 1: invalid start byte
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 287, in render
d = self._on_json_request(request)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 259, in _on_json_request
return self._send_response(request, response)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 270, in _send_response
response = json.dumps(response)
File "/usr/lib/python2.7/json/__init__.py", line 231, in dumps
return _default_encoder.encode(obj)
File "/usr/lib/python2.7/json/encoder.py", line 201, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib/python2.7/json/encoder.py", line 264, in iterencode
return _iterencode(o, 0)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb5 in position 1: invalid start byte
[ERROR ] 18:05:25 json_api:265 'utf8' codec can't decode byte 0xb5 in position 1: invalid start byte
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 287, in render
d = self._on_json_request(request)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 259, in _on_json_request
return self._send_response(request, response)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 270, in _send_response
response = json.dumps(response)
File "/usr/lib/python2.7/json/__init__.py", line 231, in dumps
return _default_encoder.encode(obj)
File "/usr/lib/python2.7/json/encoder.py", line 201, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib/python2.7/json/encoder.py", line 264, in iterencode
return _iterencode(o, 0)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb5 in position 1: invalid start byte

Re: Deluge 1.3.0 cannot load some torrents

Posted: Mon Feb 14, 2011 11:10 am
by johnnyg
If you uninstall deluge (and libtorrent) and then build deluge from source, deluge will automatically download and build the latest libtorrent.
Just follow the guide for building from source: http://dev.deluge-torrent.org/wiki/Installing/Source
All of the depends should be available on yum (make sure you also grab the dependencies for libtorrent).

Re: Deluge 1.3.0 cannot load some torrents

Posted: Tue Feb 22, 2011 4:59 am
by pblue388
Thanks for the info.

Actually I used Transmission instead which is more user friendly without so many technical issues to follow.