Page 1 of 2

0.5.7-1 not starting

Posted: Wed Nov 28, 2007 12:28 pm
by tys
I recently upgraded to deluge 0.5.7-1, Debian Sid. Starting deluge, I get following error message:

Code: Select all

Traceback (most recent call last):
  File "/usr/bin/deluge", line 46, in ?
    import deluge.interface
  File "/var/lib/python-support/python2.4/deluge/interface.py", line 37, in ?
    pygtk.require('2.0')
  File "/usr/lib/python2.4/site-packages/pygtk.py", line 61, in require
    assert not sys.modules.has_key('gtk'), \
AssertionError: pygtk.require() must be called before importing gtk
Moving the deluge config folder ~/config/.deluge and moving the plugins folder does not have any effect.

Re: 0.5.7-1 not starting

Posted: Wed Nov 28, 2007 3:20 pm
by Ruslan
me too :(

Code: Select all

$ deluge
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
Raising error: No such unique_ID.
Traceback (most recent call last):
  File "/usr/bin/deluge", line 136, in <module>
    start_deluge()
  File "/usr/bin/deluge", line 117, in start_deluge
    interface = deluge.interface.DelugeGTK()
  File "/var/lib/python-support/python2.5/deluge/interface.py", line 54, in __init__
    common.CONFIG_DIR)
  File "/var/lib/python-support/python2.5/deluge/core.py", line 276, in __init__
    self.sync(True)
  File "/var/lib/python-support/python2.5/deluge/core.py", line 877, in sync
    self.apply_prefs_per_torrent(unique_ID)
  File "/var/lib/python-support/python2.5/deluge/core.py", line 985, in apply_prefs_per_torrent
    self.get_pref("max_connections_per_torrent"))
  File "/var/lib/python-support/python2.5/deluge/core.py", line 1054, in set_max_connections_per_torrent
    max_connections)
deluge.core.DelugeError: 'No such unique_ID.'

Re: 0.5.7-1 not starting

Posted: Wed Nov 28, 2007 9:17 pm
by male
I have just upgraded Deluge to the latest version... terminal shows me:

Code: Select all

adam@Adam:~$ deluge
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
Pickling state...
Scanning plugin dir /usr/share/deluge/plugins
Segmentation fault (core dumped)
adam@Adam:~$ 
Edit: Oh yeah... I'm using Ubuntu 7.10 i386.

Edit #2: Erm, looks like everything is fine now... Deluge starts normal... I don't get it O_O anyway, thx for this release, gj ;)

Re: 0.5.7-1 not starting

Posted: Fri Nov 30, 2007 11:00 pm
by hgb
Hi Ruslan,
Ruslan wrote:me too :(

Code: Select all

[...]
Raising error: No such unique_ID.
[...]
  File "/var/lib/python-support/python2.5/deluge/core.py", line 1054, in set_max_connections_per_torrent
    max_connections)
deluge.core.DelugeError: 'No such unique_ID.'
1. you got a completely different error
2. AFAIK Python 2.5 still has some issues; try Python 2.4 instead

Have fun
-- hgb

Re: 0.5.7-1 not starting

Posted: Sat Dec 01, 2007 4:56 am
by Ruslan
how do I do this?

Re: 0.5.7-1 not starting

Posted: Sat Dec 01, 2007 6:45 pm
by Ux64
I got this too.

After adding a few torrents Deluge UI hanged. I couldn't pause / resume etc torrents or add new ones.

I closed UI and after that Deluge won't start anymore.

Code: Select all

Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
Raising error: No such unique_ID.
Traceback (most recent call last):
  File "/usr/bin/deluge", line 136, in <module>
    start_deluge()
  File "/usr/bin/deluge", line 117, in start_deluge
    interface = deluge.interface.DelugeGTK()
  File "/var/lib/python-support/python2.5/deluge/interface.py", line 54, in __init__
    common.CONFIG_DIR)
  File "/var/lib/python-support/python2.5/deluge/core.py", line 276, in __init__
    self.sync(True)
  File "/var/lib/python-support/python2.5/deluge/core.py", line 877, in sync
    self.apply_prefs_per_torrent(unique_ID)
  File "/var/lib/python-support/python2.5/deluge/core.py", line 985, in apply_prefs_per_torrent
    self.get_pref("max_connections_per_torrent"))
  File "/var/lib/python-support/python2.5/deluge/core.py", line 1054, in set_max_connections_per_torrent
    max_connections)
deluge.core.DelugeError: 'No such unique_ID.'
Deleting state file fixes problem, but adding files again, will reproduce it.

Re: 0.5.7-1 not starting

Posted: Sat Dec 01, 2007 8:33 pm
by awkward
Tys - I've found that adding the same torrent file twice caused Deluge to stop responding. And on restart has the error messages you and Ruslan had.

Same here, deleting the state file and starting again makes it work. Does mean that I have to add all the torrents again, this time making sure not to add any twice.

Re: 0.5.7-1 not starting

Posted: Sat Dec 01, 2007 8:53 pm
by Ruslan
have not been able to solve the problem: (

Re: 0.5.7-1 not starting

Posted: Sun Dec 02, 2007 11:37 pm
by hgb
Ruslan wrote:have not been able to solve the problem: (
Then you should provide more information about your system and what exactly you did to get that error. Without any help from your side, nobody will be able to help you ...

BTW: Did you try to install Python 2.4?

Regards
-- hgb

Re: 0.5.7-1 not starting

Posted: Tue Dec 04, 2007 7:03 am
by zeon
I think my type of error is right for this top
after crashing deluge gave me this:

Code: Select all

no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
Pickling state...
Scanning plugin dir /usr/share/deluge/plugins
Initialising plugin ExtraStats
Initialising plugin DesiredRatio
Initialising plugin SpeedLimiter
Initialising plugin NetworkGraph
Initialising plugin FlexRSS
Initialising plugin TorrentPeers
Initialising plugin TorrentSearch
Initialising plugin NetworkHealth
Initialising plugin WebUi
Initialising plugin TorrentCreator
Initialising plugin EventLogging
Initialising plugin BlocklistImport
Initialising plugin MoveTorrent
Initialising plugin TorrentFiles
Initialising plugin TorrentNotification
Initialising plugin WebSeed
Initialising plugin Scheduler
Applying preferences
Starting DHT...
No DHT file to resume
terminate called after throwing an instance of 'asio::system_error'
  what():  Address already in use
Aborted (core dumped)
what to do to fix this?