I have the scheduler plugin set to the "turn off" category at some times of day. Since upgrading to 2.2, only some of the torrents stop at the scheduled time. I haven't found any pattern behind which torrents stop or not.

Is there a trick that I have missed or is this a bug? At the moment I'm getting around this just by closing the application instead.

I just registered for the forums to report this same problem. This is a big problem for me as I share a really slow DSL connection with family, and I only get to use Bit Torrent during the night because our upload bandwidth is so low and using BT completely frells everyone else's ability to use the internet.

If I can't trust the Bandwidth Scheduler to stop my bit torrent activity at the time I specified, I have to go back to the horror that is turning off bit torrent when I go to bed and cutting my download and seeding time in half! The bandwidth scheduler is 90% of the reason why I stayed with ktorrent after I tried it originally.

We will check it out, it's probably a minor bug.

George wrote:We will check it out, it's probably a minor bug.

I got this bug too!
I set it to come on at midnight and stop at 17:00, it stopped and then restarted again about ten seconds later. Will it be fixed soon? or do you recommend going back to the previous version? Can I go back without losing my partial downloads?

George wrote:We will check it out, it's probably a minor bug.

I got this bug too!
I set it to come on at midnight and stop at 17:00, it stopped and then restarted again about ten seconds later. Will it be fixed soon? or do you recommend going back to the previous version? Can I go back without losing my partial downloads?
im running Ubuntu Dapper
Steve

OK, all problems with the bandwith scheduler should be gone now

George wrote:OK, all problems with the bandwith scheduler should be gone now

No, theyre not!
Its still not stopping at 17:59, its now 18:12 and its still seeding!
Steve

startreksteve wrote:

George wrote:OK, all problems with the bandwith scheduler should be gone now

No, theyre not!
Its still not stopping at 17:59, its now 18:12 and its still seeding!
Steve

Right, and you downloaded, compiled and installed the latest code from our SVN repository ?

Thanks for the fix, it seems to be in the (k)ubuntu/feisty repositories.

EDIT: My bad, the fix is not in there, I haven't tested the svn code (and likely won't), it did stop temporarily, but then restarted.

I got an update this morning through ubuntu - my scheduler has now stopped working, previous to this I had no problem.

Edit - Apologies - yes I'd been updated but Ubuntu hadn't updated me to 2.2.1- didn't look which ver it was - I have done so myself and yes the scheduler is working javascript:emoticon(':wink:')

forestpixie wrote:I got an update this morning through ubuntu - my scheduler has now stopped working, previous to this I had no problem.

Edit - Apologies - yes I'd been updated but Ubuntu hadn't updated me to 2.2.1- didn't look which ver it was - I have done so myself and yes the scheduler is working javascript:emoticon(':wink:')

So is the scheduler working now in the Ubuntu Dapper Repos's?
Steve

[quote="startreksteve"

So is the scheduler working now in the Ubuntu Dapper Repos's?
Steve[/quote]

Couldn't tell you that - I use Fiesty

But the version I was updated to from the Fiesty repos didn't work - had to get the update from here

Just checked the Fiesty repo and it is now showing the same version 2.2.1

Update came in today and the fix seems to work in kubuntu/feisty now and has stayed for several minutes. My thanks to the developers for the fix.

Version is: 2.2.1.-0ubuntu1~feisty1

btharper1221 wrote:Update came in today and the fix seems to work in kubuntu/feisty now and has stayed for several minutes. My thanks to the developers for the fix.

Version is: 2.2.1.-0ubuntu1~feisty1

Yep,
working great in Dapper too..
all sorted!
Great, Cheers!
Steve