v0.4 RC1 debs available

[zachtib]

Ok, the first RC debs of 0.4 are available here: http://deluge-torrent.org/trac/wiki/Downloads
EDIT: RC2 is now up

Just a quick writeup, because I have to run...

We didn't manage to get everything that we wanted done in 0.4. Two of our primary goals, sending torrents to an already running instance of Deluge and rewriting the code for the GTK tables in the interface proved to be too much work for this branch. Both of them required very significant changes to Deluge's entire code. So, rather than implement them in hack-ish ways, we're going to take the time to do it right, which is what 0.5 is going to be all about. During the 0.5 branch, we're practically going to start from scratch, not that we're throwing our old code away just yet, but I'm going to take the time to implement many of our features more naturally, the way they should have been done originally.

Gotta run. Download and try it out. Non-ubuntu users: I'm not going to bother making tarballs of an RC, check out SVN revision 414 (the latest) and that will be exactly the same files that would be in a tarball. (tarballs WILL be provided for 0.4 final)

[Choad]

downloaded it, and it is nice. working well :)

[xstaticxgpx]

im getting a

Seeders: 47004122087424 (0)

Peers: -47004122087424 (0)

i had this problem before when i used a new version of python-libtorrent and a lower version of deluge. Even though I downloaded the experimental version of both

[Choad]

W-[21:10:09] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.
W-[21:11:10] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.
W-[21:13:11] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.
W-[21:17:12] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.
W-[21:25:13] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.


hmmmm

look at attached.... u dont have to leave firestarter running do you? you just open it, fiddle with settings, then close it. i assume this because the firewall is built in to the kernel, it cant possibly rely on 3rd part programs running.... but i could be wrong

[Choad]

share ratio at 540%

this sucks

i now have 3 seeds, and it says health: ok

but terrible download speed. why?

[XVampireX]

Same problem as you :(
also won't connect to something that connects just fine and downloads super fast on mainline client and bittornado. That sucks.

[kripkenstein]

W-[21:10:09] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.
W-[21:11:10] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.
W-[21:13:11] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.
W-[21:17:12] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.
W-[21:25:13] No incoming connections: you may be behind a firewall or router. Perhaps you need to forward the relevant ports.


hmmmm

look at attached.... u dont have to leave firestarter running do you? you just open it, fiddle with settings, then close it. i assume this because the firewall is built in to the kernel, it cant possibly rely on 3rd part programs running.... but i could be wrong

Did you test the port ("Test Port" button in the preferences)?

[kripkenstein]

Regarding slow download speeds:

1. This might be an encryption issue, which the (latest) mainline supports, as do Azureus, utorrent, etc. If the torrent has lots of clients using encryption, then Deluge might be slow, because it still doesn't support that feature.

2. In general libtorrent (Deluge's backend) seems to take more time to 'start up'. I am not sure why. But in many cases it seems to reach a good speed eventually.

EDIT:

3. Also, check that your upload speed isn't set too high. Try lower values and see if that helps.

[Choad]

@ did i test the port

yep, "OK"

edit: i hate this forum! you press quick reply to this post and it doesnt auto check "quote message in reply"

[Choad]

on the plus side, it actually works in the xfce tray now, and when resizing the lower pane, the tabs dont "lag" like they used to. (if anyone understands what i mean by that lol)

[jamesford]

ït LOOKS very good, it doesent work very well tho. very impressed with the improvements and the plugins and everything except the fact it doesent work

i would still like to request that u do something about the name, size, seeders and so on columns, so that its possible to give them a fixed size. i truly hate horisontal scrollbars

[buildid]

iam running blackbox , dunno if it is my system or not but after a while , de gui is frozen ( completly grey) the libtorrent is stil working.

dunno what is happening . this happens within 10 minutes ..

Richard

[kripkenstein]

iam running blackbox , dunno if it is my system or not but after a while , de gui is frozen ( completly grey) the libtorrent is stil working.

dunno what is happening . this happens within 10 minutes ..

Richard

When you run it from the command line, do you get any errors?

[xstaticxgpx]

im getting a

Seeders: 47004122087424 (0)

Peers: -47004122087424 (0)

i had this problem before when i used a new version of python-libtorrent and a lower version of deluge. Even though I downloaded the experimental version of both

any reason this would happen?

[zachtib]

any reason this would happen?

not that I know of... perhaps kripken will have a better idea.




OK, here's RC2 debs, from the downloads page: http://deluge-torrent.org/trac/wiki/Downloads

i'll edit post 1 as well to reflect the change.

I'm on "vacation" right now, which essentially translates into me only having internet access at night, which is why these debs took a few days for me to build. I'll be back to my usual computing habits on monday.

[merlyn]

Hi all,

up until recently I've been using Deluge (stable) and thought that I'd give (unstable) a whirl, as of yesterday.

RC 1 did run but segfaulted in less than a minute of run time.

Sorry for not bringing this to anyones attention earlier.

However, as RC2 is now out I guess that is now a moot point.

I do get the following error when attempting to launch RC2, (installed it just 5 minutes ago.

~$ deluge
Traceback (most recent call last):
File "deluge.py", line 44, in ?
import torrent
ImportError: /usr/lib/python2.4/site-packages/torrent.so: invalid ELF header
~$ I would appreciate advice on either

1) a way to correct this, or
2) a means to provide any additional information to assist with debugging.

Keep up the good work on Deluge folks it's really coming along nicely.

Cheers.

[kripkenstein]

I do get the following error when attempting to launch RC2, (installed it just 5 minutes ago.

~$ deluge
Traceback (most recent call last):
File "deluge.py", line 44, in ?
import torrent
ImportError: /usr/lib/python2.4/site-packages/torrent.so: invalid ELF header
~$

Are you sure you have the right binary? This sort of error might occur if you e.g. install the PowerPC libtorrent on an x86 computer. Which packages exactly did you install, and what hardware do you have?

Also, you might want to just compile libtorrent yourself, if nothing else works.

[merlyn]

Are you sure you have the right binary? This sort of error might occur if you e.g. install the PowerPC libtorrent on an x86 computer. Which packages exactly did you install, and what hardware do you have?

Also, you might want to just compile libtorrent yourself, if nothing else works.

Absolutely, I downloaded the correct files from the deluge site as per the link supplied.

Here are the names of the files downloaded and installed,

deluge_0.3.99.2_all.deb
deluge-plugins_0.3.99.1_all.deb
python-libtorrent_0.3.99.2_i386.deb

Might I reiterate, that until installing either of the 0.4 release candidates deluge was working fine.

With regards to hardware my CPU is an AthlonXP2500+(barton).

I am more than happy to provide additional information, please let me know exactly what you need.

Cheers.

[kripkenstein]

Well, there might be a problem with the .debs then. Hopefully Zach will see this message soon and check.

In the meantime, you can compile the source from SVN, that should work. Let me know if you need help with that.

[zachtib]

Well, there might be a problem with the .debs then. Hopefully Zach will see this message soon and check.

In the meantime, you can compile the source from SVN, that should work. Let me know if you need help with that.

I thought that I built them wrong... lemme try to force the deb to rebuild

[zachtib]

Ok this one _should_ have built properly, but I don't have time to test it right now, so give it a whirl. Again, its available from the downloads page.

EDIT: OK, they seem to work for me

[jamesford]

the new debs work great. great speed as well. still shows a crazy number of seeders and peers but thats just cosmetic.
my only concern is that it seems to be using a fair bit of cpu, more than azureus/java in fact

[zachtib]

the new debs work great. great speed as well. still shows a crazy number of seeders and peers but thats just cosmetic.
my only concern is that it seems to be using a fair bit of cpu, more than azureus/java in fact

yeah, this seems to be related to edgy. Almost everything uses a lot of CPU on edgy for me, and I'm not sure exactly what causes it...

anyways, there is a CPU plugin that monitors Deluge's CPU usage, and if it gets to a dangerous point, it exits Deluge.

[jamesford]

weird, i havent noticed any unusual cpu usage on edgy (64 bit) compared to dapper

[zachtib]

weird, i havent noticed any unusual cpu usage on edgy (64 bit) compared to dapper

really?

some people seem to be getting it really bad, others not at all. Hows the memory usage for Deluge? And does it just stay at a very high CPU usage (>80%)?

[jamesford]

memory usage is pretty low, less than 40 mb for deluge and the python thread combined (i havent really let it run for very long tho, ive just been testing it with some small torrents)
as for high cpu usage, i guess its not really high, 4%, but its still more than azureus! (x2 4400+ cpu running at 45%)

[zachtib]

Ah... sometimes on edgy for me, some apps peg the cpu at 100%, making my laptop's cpu hit 90 degrees Celsius... I thought that's what you were refering too.

[jamesford]

ah ic, no not that bad at all. my cpu temp peaked at 44 degrees C during the heatwave in the summer ;)the amd x2's are supercool

[zachtib]

I have a Pentium M in my laptop, which can run pretty hot if it stays at 1.7GHz... I'm using emifreq to lock it at 600MHz to prevent this from happening

[jamesford]

can we have an option to scan a dir for new .torrent files every x min/sec ?
also the option to delete the .torrent file when pressing the minus icon?

[merlyn]

Hi all,

RC2 is working fine for me now.

I went through the following steps
completely removed non working install of RC2 and associated debs.
reinstalled 0.3, which as before worked fine.
completely removed install of 0.3
reinstalled RC2, which as stated above now works fine.When I experienced the problems that I mentioned earlier, I installed RC2 without removing 0.3 first.

To be honest, I'm not sure if this should be necessary or not. Or perhaps its just a quirk with my setup? I really don't know.

However all is now well.

Thanks to Kripkenstein and Zachtib for responding to my earlier posts and all your hard work on Deluge.

Cheers.

[zachtib]

To be honest, I'm not sure if this should be necessary or not. Or perhaps its just a quirk with my setup? I really don't know.

I accidently hit ctrl-c while compiling, so the first i386 RC2 deb was corrupted. Thats why there is now a 3.99.2-2 deb, which was rebuilt properly

Thanks to Kripkenstein and Zachtib for responding to my earlier posts and all your hard work on Deluge.

no problem, thanks for testing for us