Package: rtorrent
Version: 0.6.4-1
Severity: normal

After upgrading my kernel from 2.6.18 to 2.6.19, downloads with rtorrent 
fail hash check on completion (all downloads). The following message is 
then reported by rtorrent:

Inactive: Hash check on download completion found bad chunks, consider 
using "safe_sync".

Using safe_sync doesn't fix the issue. The download results are 
inconsistent - some files get further than others. Forcing a hash check, 
rtorrent will complete the download, then the final hash check succeeds.

This happened as soon as I  changed from kernel 2.6.18 to 2.6.19. I 
believe there's a bug filed against libtorrent9 which speaks about a
similar issue, but it's with kernel 2.6.18 with backported patches from
2.6.19.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19-smp-gw
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages rtorrent depends on:
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries
ii  libcomerr2                   1.39-1      common error description library
ii  libcurl3                     7.15.5-1    Multi-protocol file transfer libra
ii  libgcc1                      1:4.1.1-13  GCC support library
ii  libidn11                     0.6.5-1     GNU libidn library, implementation
ii  libkrb53                     1.4.4-2     MIT Kerberos runtime libraries
ii  libncurses5                  5.5-3       Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a           2.0.17-2    type-safe Signal Framework for C++
ii  libssl0.9.8                  0.9.8c-1    SSL shared libraries
ii  libstdc++6                   4.1.1-13    The GNU Standard C++ Library v3
ii  libtorrent9                  0.10.4-1    a C++ BitTorrent library
ii  zlib1g                       1:1.2.3-13  compression library - runtime

rtorrent recommends no packages.

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to