#263 closed bug (Invalid)
can't connect to daemon
| Reported by: | danii | Owned by: | andar |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | GTK UI | Version: | 0.6.0svn |
| Keywords: | Cc: |
Description
Deluge 0.6.0.0r3203
with clean config connect to daemon in gtk ui fails with:
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/deluge/ui/gtkui/gtkui.py", line 182, in _on_new_core
component.start()
File "/usr/lib/python2.4/site-packages/deluge/component.py", line 194, in start
_ComponentRegistry.start()
File "/usr/lib/python2.4/site-packages/deluge/component.py", line 114, in start
self.start_component(component)
File "/usr/lib/python2.4/site-packages/deluge/component.py", line 126, in start_component
self.components[name].start()
File "/usr/lib/python2.4/site-packages/deluge/ui/gtkui/addtorrentdialog.py", line 132, in start
self.update_core_config()
File "/usr/lib/python2.4/site-packages/deluge/ui/gtkui/addtorrentdialog.py", line 170, in update_core_config
self.set_default_options()
File "/usr/lib/python2.4/site-packages/deluge/ui/gtkui/addtorrentdialog.py", line 380, in set_default_options
self.glade.get_widget("chk_private").set_active(
TypeError: an integer is required
Change History (5)
comment:1 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 18 years ago
| Priority: | major → minor |
|---|---|
| Resolution: | invalid |
| Status: | closed → reopened |
ui and daemon are the same revision, I've upgraded to [3205], the problem persists but only when you don't have ~/.config/deluge, with the old config deluge runs, but as you said torrents.state got broken with [3203], so there are no torrents loaded guess this is only an issue with new or clean installations but it should be fixed
comment:3 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
It works just fine with a clean config. Please remember that remote connections to the daemon are not permitted by default.
comment:4 by , 18 years ago
My bad.. I didn't notice the exception you were talking about. It has been fixed in [3206]. Thanks.



It looks like your server and client are out of sync version wise. Please make sure both are using the latest svn.