Custom Query (2447 matches)

Deluge has crashed over 10 times within the last two hours. Every time it happened, my console printed the following data:

no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
no old fastresume to delete
Segmentation fault (core dumped)

This is a pretty serious bug because I can't just leave Deluge on overnight... I'm using Ubuntu Gutsy and, for the first time today, the window manager Xfce (I don't know if this matters for Deluge).

Program version is actually 0.5.8.9, not 0.5.8.8.

Hi,

I think a splitted view as seen in azureus would give much more usability. Upper part for active, paused, stopped downloads Lower part for completed, seeding downloads.

This way one can specify how many active / uploading / downloading torrents there should be without messing around in the torrents order. This is what annoyes me the most.

Perhaps this could be done as an plugin or as an option, so users have the choice. Now, when you click "put finished torrents to the end" they will stop seeding. This is not good at all.

The reason for this request is to simplify code merges.

While adding new features and merging the changes introduced into master from other branches(being worked at the same time). Ofter I've found myself needing to merge glade files. These issues could be simplified if glade files could be "self contained", ie, *one* dialog per glade file.

Was there a reason why this wasn't done in the first place? Are there any major performance penalties?