deluge crashed with ImportError in find_class()

Crashes here too.

I confirm crash on startup:

akira@aktabar:~$ deluge
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG value: 1
Applying preferences
Starting DHT...
/var/lib/python-support/python2.5/deluge/core.py:723: DeprecationWarning: integer argument expected, got float
  PREF_FUNCTIONS[pref](self.get_pref(pref))
Traceback (most recent call last):
  File "/usr/bin/deluge", line 93, in <module>
    start_deluge()
  File "/usr/bin/deluge", line 67, in start_deluge
    interface = deluge.interface.DelugeGTK()
  File "/var/lib/python-support/python2.5/deluge/interface.py", line 57, in __init__
    '%s %s'%(common.PROGRAM_NAME, common.PROGRAM_VERSION), common.CONFIG_DIR)
  File "/var/lib/python-support/python2.5/deluge/core.py", line 223, in __init__
    self.state = pickle.load(pkl_file)
  File "/usr/lib/python2.5/pickle.py", line 1370, in load
    return Unpickler(file).load()
  File "/usr/lib/python2.5/pickle.py", line 858, in load
    dispatch[key](self)
  File "/usr/lib/python2.5/pickle.py", line 1069, in load_inst
    klass = self.find_class(module, name)
  File "/usr/lib/python2.5/pickle.py", line 1124, in find_class
    __import__(module)
ImportError: No module named deluge
akira@aktabar:~$

Thank you for your bug report.
In order to fix this, we could provide users a dialog box which suggest to remove existing confdir before starting deluge.
Do you think this can be enough?

That would fix the crash, but it's a really ugly fix, and is likely to annoy users. Ideally we'd convince upstream to import old configs rather than crashing on them.

Well, I believe "Zachtib" must be a well known person within the Ubuntu community.

http://forum.deluge-torrent.org

Maybe some devs stays out from the reality.

Regards
plun

I can confirm bug also in Gusty Gibson. I have same error as zdnko.

Fix:
rm -R ~/.config/deluge

that is not a very elegant fix, you end up losing the current status of your torrents that are being seeded. This is a major hassle to reconnect all of your torrents you had running in the client. Why does deluge crash, is it not possible to parse the old config files and extract only the info relevant to the new version? Would deluge not create a new config file when exiting the first time after an upgrade?

This is one of the most reported Deluge bugs according to launchpad, I ended up here because of this same bug. I think something needs to be done to resolve this issue, something different then rm -R ~/.config/deluge

deluge-torrent (0.5.4.1-1ubuntu1) gutsy; urgency=low

  * Merge from Debian unstable (LP: #132093, #128418).
    (LP: #121836) fixed in 0.5.3 upstream.
    Remaining Ubuntu changes:
    - debian/control:
      + Update maintainer field.
  * debian/patches/001-Disable_update_notification.dpatch:
    - Disable the new version notification. We have apt for that.

deluge-torrent (0.5.4.1-1) unstable; urgency=low

  * New upstream release (Closes: #436839, #437205).
  * Drop 000-Fix_CFLAGS_handling patch, fixed upstream.
  * Add 000-Fix_browser.py_path patch to fix broswer launch failure (Closes: #435464).
  * Menu: move to Applications/Network/File Transfer.
  * Drop deprecated 'Encoding' entry in desktop file.

deluge-torrent (0.5.3-1) unstable; urgency=low

  * New upstream release.
    - Torrent urls supported on the command-line (Closes: #416013).
  * Update 000-Fix_CFLAGS_handling patch.
  * Break loops with '|| exit 1' in debian/rules.
  * Rewrite icons handling. Now all sizes are generated with imagemagick.
  * Fed up with upstream website changes... Drop debian/watch.

deluge-torrent (0.5.2-1) unstable; urgency=low

  * New upstream release (Closes: #431929, #416014, #429880).

 -- Christopher James Halse Rogers (RAOF) <email address hidden> Mon, 13 Aug 2007 11:00:53 +1000