1.0.0_RC9 (0.9.09) Released

[johnnyg]

port 25 is SMTP and port 995 is POP3S; it sounds like you've got a program checking for emails.
deluge sends anonymous stats and checks for newer versions over HTTP (port 80), so I don't see how this could be deluge.

[AnomynousPierson]

... messages via port 25/995 - in some random intervals, but rather short? (1-6 minutes)
I've got blocked on my network several times, for several hours (in total that would be a 2-4 days) .....
Cheers, Paziek.

port 25 is SMTP and port 995 is POP3S; it sounds like you've got a program checking for emails.
deluge sends anonymous stats and checks for newer versions over HTTP (port 80), so I don't see how this could be deluge.

What kind of horrid network admin kills your internet access if you check your email?
Something tells me your computer might be involuntarily SPAMing. Hard to say.

In any case, as johnnyg pointed out, deluge isn't going to use those ports unless you specifically configure it to.

[paziek]

Yeah, those are SMTP/POP3 ports, but I use google mail, and it uses different ports, so thus couldn't have been my e-mail client.
And as I said - this started since isntallation of new Deluge, so it was obvious suspect.. can I have some kind of worm spaming from my PC? Do they even do this kind of stuff for Linux? ;O

[markybob]

Yeah, those are SMTP/POP3 ports, but I use google mail, and it uses different ports, so thus couldn't have been my e-mail client.
And as I said - this started since isntallation of new Deluge, so it was obvious suspect.. can I have some kind of worm spaming from my PC? Do they even do this kind of stuff for Linux? ;O

this is not a deluge problem and totally off topic. please go to your distribution's irc channel or forum instead

[andar]

I guess there is the possibility of peers using those ports as their listen ports. Deluge would then try to connect to the port on the peer and this may trigger your alert?

I didn't really read too closely the exact problem, but I thought this might be applicable.

[DanielHolm]

I was stunned when I saw the new look of Deluge. Its beautiful! Keep up the remarkable good work!

[loki]

Windows Vista x64, RC9 x64

It finally works! Though it appears is not actually 64 bit, but just installed into the 64 bit folder, I'm not one to ask questions as long as it works.
The install is actually up to 134Mb again.
Open folder/open file is working again.
I noticed something when downloading a file today... peers is showing ipv6 addresses! Don't know if it's good or bad... Looks like some show up multiple times, and it doesn't get any info from them. Should I post a screen?

[Nevtus]

First of all, great work so far. Deluge is coming along nicely. I've switched from Azureus to Deluge at RC8 and now RC9 as my main client.

I've encountered a really annoying problem though. Whenever I start Deluge a lot of the active torrents (but not all) that I was previously seeding/downloading get wrongly listed as Paused or Checking. However they still seem to be working fine, it's just that the GUI does not show it. I have to Pause the Paused/Checking torrents that aren't really Paused or Checking, then restart them to get everything back to normal. I have a lot of torrents loaded so I think this may be a reason for this. It's probably the only major bug that I've noticed from my short time messing around with Deluge.

[andar]

First of all, great work so far. Deluge is coming along nicely. I've switched from Azureus to Deluge at RC8 and now RC9 as my main client.

I've encountered a really annoying problem though. Whenever I start Deluge a lot of the active torrents (but not all) that I was previously seeding/downloading get wrongly listed as Paused or Checking. However they still seem to be working fine, it's just that the GUI does not show it. I have to Pause the Paused/Checking torrents that aren't really Paused or Checking, then restart them to get everything back to normal. I have a lot of torrents loaded so I think this may be a reason for this. It's probably the only major bug that I've noticed from my short time messing around with Deluge.

This could be a problem with the SignalReceiver on the UI end. Next time you encounter this issue, can you check the deluged.log and see if it's failing to emit signals to the client?

[loki]

Separate note, looks like the uninstaller finally deleted all files and the main folder (a plus) but takes like 3x longer than usual, and longer than most other programs (not a plus).