reopening tickets

[shirish]

Before I start, please look at http://forum.deluge-torrent.org/viewtop ... p=520#p520

the ticket I had opened before http://dev.deluge-torrent.org/ticket/354 markybob talked me & said its most probably due to gutsy being unstable.
Hence I closed it, later on when quite a people complained he did it right & now everybody benefits. http://forum.deluge-torrent.org/viewtop ... p=791#p791 a user named phanboy even opened a ticket about it http://dev.deluge-torrent.org/ticket/428 which is the same issue I had. Do notice the time difference also.
Similarly I am now facing http://dev.deluge-torrent.org/ticket/377 which I had closed under the same presumption. Even giving all the info. that I can he still closed it, I just don't understand what is wanted. And again I had closed the ticket voluntarily but its 2 months now but still the issue is for me.

Esp. when the 0.5.3 release is supposed to be Bug fixes and stability release in time for hopeful inclusion into Gutsy

Any help/guidance on this will be much appreciated. If anybody needs any info. on any software/ machine specs. or anything which might get the issue resolved or atleast the cause known, I would be more than willing to supply it.

[markybob]

closed it, I just don't understand what is wanted. And again I had closed the ticket voluntarily but its 2 months now but still the issue is for me.

if it bothers you, then dont use an alpha OS with alpha tools. use a stable OS and you wont have problems.

[shirish]

closed it, I just don't understand what is wanted. And again I had closed the ticket voluntarily but its 2 months now but still the issue is for me.

if it bothers you, then dont use an alpha OS with alpha tools. use a stable OS and you wont have problems.

my dear brother, while that is of course the option, do you have other gutsy users as well who do not have this issue? If that is the case then its ok. I don't know then why do you guys write that Bug fixes and stability release in time for hopeful inclusion into Gutsy under roadmap. For if I'm having the issue then there is a possibility/probability that others will have as well.

Update:- Andar opened up the ticket & asked me what filesystem I'm using. I use ext 3 (sorry didn't remember to log in, hopefully trac 0.11 comes soon so I'm always logged in through cookies and your web server is able to upgrade to that) & all the data in the same partition i.e. /home/shirish but in different sub-directories till the categorize plugin doesn't come up.
Also each update, I do remember to do make clean I don't do

Code: Select all

 rm -rf ~/.config/deluge

as often otherwise I just wouldn't know how much ratio I have done. [OT] I try to keep 1:1 ratio & not all tracker sites keep individual torrent scores. [/OT] . This time I followed all the instructions & removed all the files & started from scratch. Where I do feel the issue remains though is with big torrents (something in the range of 4.5 + GIB & above one of which I'm downloading while the other one is seeding. I've put both the big ones (5 GiB ones) at the top while all the smaller ones ~700 MiB are down the line. So after all are checked, would be shutting down the client & restarting them and reporting what happens.

[shirish]

Closed it down properly.

Code: Select all

shirish@ubuntu:~$ deluge
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
Pickling state...
Scanning plugin dir /usr/share/deluge/plugins
Loading module DesiredRatio
Initialising plugin DesiredRatio
Loading module TorrentCreator
Initialising plugin TorrentCreator
Loading module FirstLast
Initialising plugin FirstLast
Loading module TorrentSearch
Initialising plugin TorrentSearch
Loading module Scheduler
Initialising plugin Scheduler
Loading module TorrentNotification
Initialising plugin TorrentNotification
Loading module BlocklistImport
Initialising plugin BlocklistImport
Loading module RSS
Initialising plugin RSS
Loading module NetworkGraph
Initialising plugin NetworkGraph
Loading module NetworkHealth
Initialising plugin NetworkHealth
Applying preferences
Starting DHT...
Showing window
Loading blocklist plugin ...
Fetching /home/shirish/pipfilter.dat.gz
importing with gzmule
GZMuleReader loading /home/shirish/.config/deluge/blocklist.cache
MuleReader loading
TextBase loading
Starting import
Import finished
Loading TorrentNotification plugin...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Pickling state...
Applying preferences
Applying preferences
Applying preferences
Applying preferences
Stopping DHT...
Pickling state...
Pickling state...
Saving prefs...
Pickling state...
Saving fastresume data...
Quitting the core...
core: removing torrents...
core: removing settings...
core: shutting down session...
core shut down.

Reopened it, its checking the big files one after other & irony is the one its checking is the one which I have fully & seeding. Here is a screenshot of the same :-


Shot at 2007-07-17

As one can see, the first 3 files are green means its checking while the other ones are blue (IIRC blue ones are ones which are for seeding & already checked) . Both the 1st 2 are 4.5 GiB ones while the next one is about 700 MiB ones, I have not given the whole list as there are 17 odd files in the list. All the rest show blue. Just for comparision in utorrent has something like 150 odd files at any point in time.

Would give updates as & when something more happens, if boost libraries get updated, python get updated or anything else that might effect the thing.

As again any info. needed please lemme know. This is with svn 1023 :-

Code: Select all

shirish@ubuntu:~$ svn info deluge
Path: deluge
URL: http://deluge-torrent.org/svn/trunk
Repository Root: http://deluge-torrent.org/svn
Repository UUID: b3ab561c-7021-0410-825b-ae720ed029d9
Revision: 1023
Node Kind: directory
Schedule: normal
Last Changed Author: zachtib
Last Changed Rev: 1023
Last Changed Date: 2007-07-18 04:05:16 +0530 (Wed, 18 Jul 2007)

[irfan]

off topic

shirish@:
Why you have GTK style progressbars in torrents list? looks awesome.

[shirish]

off topic

shirish@:
Why you have GTK style progressbars in torrents list? looks awesome.

irfan I have no idea from where they come, maybe with gutsy or something else. I am using xfce desktop so it might due to that. The gtk style progressbar which you say is also in firefox/firefox-granparadiso.

[shirish]

first of all thanx eternalswd for trying to do stuff with fastresume . http://dev.deluge-torrent.org/changeset/1034 . Good attempt & it did improve the things perhaps but not a lot. Now I get the big one which is downloading without checking but one of the smaller files next to it gets checked. I use the blocklist importer & tried it both ways, once with & once without the plugin, no change but still a good effort nonetheless I can live with a 2 minute delay rather than 5-7 minute which that checking used to take. So good for now, perhaps that can be looked up later when deluge is bit more mature

[plisk]

Shirish: do you still have issues with fast resume ? Here is one idea to try - could you run from here http://213.186.33.37/gentoo-distfiles/d ... 09.tar.bz2 client_test.cpp found in libtorrent examples/ dir and see if it handles fastresume files correctly ? And question - what filesystem do you use ?