1.0.0_RC9 (0.9.09) Released

[allouh]

i'm stil using deluge rc7 because rc8 didnt work with me( i think other users reported its problem, no GUI interface...etc), anyway the problem here isnt this.
priorize first and last piece isnt working with this RC. and this is significantly important for me as to many others.
i had to wait untill 60-70% of the download untill i can check the file,and this happend mainly with large files.
i am using hex editor to check files not depending on the players.

[dgaust]

Last night went to sleep, when I woke up my computer was barely responsive. After checking, System Monitor is reporting that Deluge is using 607.9MB's of RAM.

I have 24 torrents loaded. Of those only 22 are paused, and two are downloading/uploading. I had never had this problem. Is this a problem in the RC? Deluge becoming so memory hungry?

I'm gonna restart it and see if I can monitor the memory usage of it.

I've had RC08 installed for a while, and after an hour so of use the PC would become unresponsive. Quitting Deluge would bring it back to normalcy. However, if I the re-opened Deluge I would be missing huge chunks of the downloads (in some cases torrents would drop 50-60%).... Those bugs seem to have be reported in Trac though

[abubin]

Last night went to sleep, when I woke up my computer was barely responsive. After checking, System Monitor is reporting that Deluge is using 607.9MB's of RAM.

I have 24 torrents loaded. Of those only 22 are paused, and two are downloading/uploading. I had never had this problem. Is this a problem in the RC? Deluge becoming so memory hungry?

I'm gonna restart it and see if I can monitor the memory usage of it.

I've had RC08 installed for a while, and after an hour so of use the PC would become unresponsive. Quitting Deluge would bring it back to normalcy. However, if I the re-opened Deluge I would be missing huge chunks of the downloads (in some cases torrents would drop 50-60%).... Those bugs seem to have be reported in Trac though

hmm..the problem with missing chunks when re-checking torrent is not solved yet?

[Nanobot]

Last night went to sleep, when I woke up my computer was barely responsive. After checking, System Monitor is reporting that Deluge is using 607.9MB's of RAM.

I have 24 torrents loaded. Of those only 22 are paused, and two are downloading/uploading. I had never had this problem. Is this a problem in the RC? Deluge becoming so memory hungry?

I'm gonna restart it and see if I can monitor the memory usage of it.

I've had RC08 installed for a while, and after an hour so of use the PC would become unresponsive. Quitting Deluge would bring it back to normalcy. However, if I the re-opened Deluge I would be missing huge chunks of the downloads (in some cases torrents would drop 50-60%).... Those bugs seem to have be reported in Trac though

hmm..the problem with missing chunks when re-checking torrent is not solved yet?

Well, I know that when Deluge crashed for me recently, I lost about four hours' worth of data. From what I understand, this was a related issue that was also supposed to have been fixed in 0.9.08 by saving the data every few minutes. (This large torrent went from about 10% before the crash to 0.3% immediately after the crash.)

[dgaust]

hmm..the problem with missing chunks when re-checking torrent is not solved yet?

I don't think so... this wasn't from a crash, I closed down Deluge and the Daemon properly. When I re-opened there was large chunks of torrents missing. Doing a re-check of the files didn't not fix it.

[negge]

I think I've found a bug. I'm running a Deluge daemon on my home server and access it via Deluge from my desktop computer. Today I had to unplug the LAN cable from my desktop, and when I re-attached it (and restarted my computer), Deluge had lost track of the torrent numbers. Now my torrents are in a completely different order than what they used to be. A little bit annoying when you have 20+ torrents running.

A quick question:

I'm running 0.9.07 at the moment. How do I upgrade to the newer version? Do I just have to dpkg -r the old package and install the new one? After reading about all the trouble Windows users have had upgrading versions I've become a bit paranoid when it comes to upgrading.

[loki]

Were they seeding torrents or downloading torrents? I believe downloading torrents are supposed to keep their original order, but seeding torrents don't follow the same rules... they manage their own queuing order or something...

And yes, dpkg -r should work fine.

[negge]

Were they seeding torrents or downloading torrents? I believe downloading torrents are supposed to keep their original order, but seeding torrents don't follow the same rules... they manage their own queuing order or something...

And yes, dpkg -r should work fine.

They were all seeding. I don't see why they wouldn't retain their original order even though they were in seeding state, most people want their list to look the same after they close and re-open their client. I'm gonna wait for the final release to be out before I upgrade, 0.9.07 has been working fine for me so far. Now we just need all the old plugins back! Atlest the torrent creator plugin so I don't have to open up Transmission everytime I want to make a torrent...

[timmy8765]

Sorry about double posting.

BUG:
I just removed 0.5.9.3 from my XP box along with the deluge folder in my user directory. I installed 1.0-RC8 fresh and when launching deluge I get a blank white window that doesn't respond at all.

I thought maybe having python2.5 installed was causing problems so I removed python2.5 and deluge then installed fresh again. Sadly, the issue remains.

I too am unable to get the latest release candidate to run on my XP machine. First I simply upgraded the installation, then when that didn't work, I completely uninstalled, then installed the newest version, only to still have troubles.

I had this problem as well. it seems to be a problem passing some arguments to the function that writes the log file for deluged. here is the stack trace that is printed in my log:

Code: Select all

Traceback (most recent call last):
  File "C:\Program Files\Deluge\scripts\deluged-script.py", line 8, in <module>
    load_entry_point('deluge==0.9.08', 'console_scripts', 'deluged')()
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\main.py", line 169, in start_daemon
    Daemon(options, args)
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\core\daemon.py", line 52, in __init__
    self.core = Core(options.port).run()
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\core\core.py", line 297, in run
    component.start()
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\component.py", line 194, in start
    _ComponentRegistry.start()
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\component.py", line 114, in start
    self.start_component(component)
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\component.py", line 127, in start_component
    self.components[name]._start()
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\component.py", line 59, in _start
    if self._update():
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\component.py", line 87, in _update
    self.update()
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\core\alertmanager.py", line 59, in update
    self.handle_alerts()
  File "c:\Program Files\deluge\lib\site-packages\deluge-0.9.08-py2.5-win32.egg\deluge\core\alertmanager.py", line 97, in handle_alerts
    log.debug("%s: %s", alert_type, alert.message())
RuntimeError: bad lexical cast: source type value could not be interpreted as target

commenting out line 97 in alertmanager.py got it working for me, but this is just a workaround.

[paziek]

Is new (1.0) Deluge sending some 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) since isntallation of new Deluge.
For now I have bloked those ports on my firewall (iptables), but still - this is disturbing.
I've had disabled sending of annonymous feedback in Deluge since isntallation, so I was hoping that there won't be going on anything that would get me blocked from internet.

I'm no Linux guru and I've got no idea on how to check if Deluge is really sending those e-mails, and not sth else, but I gess that some1 else will be able to give more input on that.


Cheers, Paziek.