email notification locks deluge ui client

[anonymous]

Enabling the email notification option in Deluge, no matter what authentication options, causes lock ups in Deluge UI, however, the deluged continues to run.

Running it in command line gave this output:

tim@Central:~$ deluge
1.1.9
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "/var/lib/python-support/python2.6/deluge/core/preferencesmanager.py", line 451, in run
    + "&plugins=" + quote_plus(self.config["enabled_plugins"])
  File "/usr/lib/python2.6/urllib.py", line 1228, in quote_plus
    return quote(s, safe)
  File "/usr/lib/python2.6/urllib.py", line 1220, in quote
    res = map(safe_map.__getitem__, s)
KeyError: 'Blocklist'

Killed

However, that information showed before the crash, so it may be irrelevant.

I could be missing packages or something that the app is trying to call.

I will attach a screen shot, and try to debug when I have time.

version 1.1.9 downloaded from the launchpad deluge-team ppa.

[musikgoat]

Can someone delete the first picture.

tim@Central:~$ python -V Python 2.6.2 tim@Central:~$ uname -a Linux Central 2.6.28-13-generic #44-Ubuntu SMP Tue Jun 2 07:55:09 UTC 2009 x86_64 GNU/Linux

[John Garland]

that key error has been fixed in r5416, however it wouldn't be causing deluge to lock. could you please run deluge with debug logging enabled: ​http://dev.deluge-torrent.org/wiki/Faq#HowdoIstartthedaemonwithloggingenabled and paste the log here (or link to it on dpaste/pastebin).

[musikgoat]

I have followed the instructions, however, the log doesn't reference the lock up as deluged continues to run cleanly after the UI locks up.

For reference, the file completed at 20:31:19, where the UI locked up.

Can someone add me as a CC (musikgoat at gmail dot com) so that I can receive notification of posts. Thanks.

[musikgoat]

called deluge -L debug -l logfile.log instead of deluged in the first log

[John Garland]

This was fixed awhile ago. It should be fixed in the 1.2 RCs.