Opened 8 years ago
Closed 8 years ago
#2942 closed bug (Fixed)
crash connecting while checking
Reported by: | markybob | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | 1.3.14 |
Component: | Unknown | Version: | 1.3.13 |
Keywords: | Cc: |
Description
connect to a host that's checking a torrent and this happens.
[INFO ] 19:02:34 rpcserver:206 Deluge Client connection made from: 127.0.0.1:37992 [ERROR ] 19:02:34 rpcserver:306 Exception calling RPC request: list index out of range Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 301, in dispatch
ret = self.factory.methods[method](*args, kwargs)
File "/usr/lib/python2.7/dist-packages/deluge/core/core.py", line 463, in get_torrents_status
status_dict[torrent_id] = self.get_torrent_status(torrent_id, keys, diff)
File "/usr/lib/python2.7/dist-packages/deluge/core/core.py", line 442, in get_torrent_status
status = self.torrentmanager[torrent_id].get_status(keys, diff)
File "/usr/lib/python2.7/dist-packages/deluge/core/torrent.py", line 797, in get_status
status_dict[key] = fns[key]()
File "/usr/lib/python2.7/dist-packages/deluge/core/torrent.py", line 592, in get_file_progress
ret.append(float(file_progress[i]) / float(fsize))
IndexError: list index out of range [DEBUG ] 19:02:34 core:110 Handled Notification Events: [('TorrentFinishedEvent', 'Emitted when a torrent finishes downloading.')]
after that nothing works. torrent list doesn't get updated, etc. the main problem is when you exit it doesn't save fastresume.
Change History (5)
comment:1 by , 8 years ago
Version: | other (please specify) → 1.3.13 |
---|
comment:2 by , 8 years ago
Milestone: | needs verified → 1.3.14 |
---|---|
Priority: | major → critical |
comment:4 by , 8 years ago
1.1.1 which is the only available version in stretch (which will soon be frozen and released as debian stable).
comment:5 by , 8 years ago
Resolution: | → Fixed |
---|---|
Status: | new → closed |
Fixed in 1.3-stable: [739537f860]
The refactor of develop code has squashed this bug already and was tempted to backport those changes but can't guarantee not introducing new bugs so will simply catch it.
How weird!