After upgrading to which version?
micah
On Sat, 16 Apr 2005, Luke Reeves wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I still have the same problem after upgrading to the uploaded version.
>
> Luke
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.0 (GNU/Linux)
> C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Micah. The problem persists after upgrading to the bittornado
0.3.11-2 version.
Luke
Micah Anderson wrote:
> After upgrading to which version?
>
> micah
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I still have the same problem after upgrading to the uploaded version.
Luke
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCYcpzEkTpono0swERAqJyAJ0dDV
I'm seeing the same thing. btlaunchmanycurses dies the moment it opens
it's first .torrent.
I've tried several variations. Multiple torrents in the directory. A
single torrent in the directory.
A partially downloaded torrent, a completely new torret. They all cause
a crash.
If btlaunchmanycurs
Package: bittornado
Version: 0.3.11-1
Severity: important
When using btlaunchmanycurses to download files in a directory containing 3
torrent files, I now get a stack trace where none occured before:
EXCEPTION:
Traceback (most recent call last):
File "/usr/lib/python2.3/site-packages/BitTornad
5 matches
Mail list logo