Deluge Forum

Posted: **Sun May 17, 2009 2:52 am**

Spent the last few hours after I just upgraded my Debian 5.0 to the new testing branch of 'Squeeze' - everything's back up and running bar Deluge.

After numerous tedious hours of trial and error, goggling search, and alot of hair pulling - I come here to ask for some assistance if possible.

after the move to Squeeze, full system upgrade and installation of Deluge 1.1.6+dfsg-2 (aptitude install deluge), will just NOT start under ethier root or normal - I continually receive the following error:

Code: Select all

/usr/lib/pymodules/python2.5/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
1.1.6
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/queuedtorrents.py:60: Warning: invalid (NULL) pointer instance
  "glade/queuedtorrents.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/queuedtorrents.py:60: Warning: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
  "glade/queuedtorrents.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/queuedtorrents.py:60: GtkWarning: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  "glade/queuedtorrents.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/queuedtorrents.py:60: Warning: g_object_get: assertion `G_IS_OBJECT (object)' failed
  "glade/queuedtorrents.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/queuedtorrents.py:76: GtkWarning: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  gtk.TreeViewColumn(_("Torrent"), gtk.CellRendererText(), text=0))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/queuedtorrents.py:76: Warning: g_object_get: assertion `G_IS_OBJECT (object)' failed
  gtk.TreeViewColumn(_("Torrent"), gtk.CellRendererText(), text=0))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: Warning: invalid (NULL) pointer instance
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: Warning: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: Warning: g_object_get: assertion `G_IS_OBJECT (object)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: gdk_display_get_window_at_pointer: assertion `GDK_IS_DISPLAY (display)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: gdk_pango_context_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: PangoWarning: pango_context_set_font_description: assertion `context != NULL' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: PangoWarning: pango_context_set_base_dir: assertion `context != NULL' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: PangoWarning: pango_context_set_language: assertion `context != NULL' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: PangoWarning: pango_layout_new: assertion `context != NULL' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: PangoWarning: pango_layout_set_attributes: assertion `layout != NULL' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: PangoWarning: pango_layout_set_text: assertion `layout != NULL' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: PangoWarning: pango_layout_get_unknown_glyphs_count: assertion `PANGO_IS_LAYOUT (layout)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: gtk_icon_size_lookup_for_settings: assertion `GTK_IS_SETTINGS (settings)' failed
  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: Invalid icon size 1

  "glade/main_window.glade"))
/usr/lib/pymodules/python2.5/deluge/ui/gtkui/mainwindow.py:63: GtkWarning: gtk_icon_theme_load_icon: assertion `GTK_IS_ICON_THEME (icon_theme)' failed
  "glade/main_window.glade"))
Segmentation fault

Yes, I HAVE tried the export Display suggestion that has been floating around - no luck though. Ideas

?

Thanks!

Posted: **Tue May 19, 2009 4:58 pm**

It looks like it's trying to open the display but can't.. Are you running this on a headless system or something?

Posted: **Wed May 20, 2009 11:30 pm**

Yes it is indeed on a headless server, however the latest on Unstable/Squeeze Debian repos is 1.1.6+2 and it was tagged as latest - must I compile from source with 1.1.7?

Posted: **Thu May 21, 2009 3:23 am**

I suspect you're trying to run deluge instead of deluged.
http://dev.deluge-torrent.org/wiki/Faq# ... tthedaemon

Posted: **Thu May 21, 2009 4:29 am**

Thanks for clearing that up.

Been reading posts at: http://apocryph.org/2008/11/30/setting_ ... ws_client/
and in the FAQ.

However I still am extremly confused about setting up this Headless server the way I want. I don't want to use a WebGUI if I don't have to. What I bascially want to do is setup Deluge on my server, have it watching a folder for things to download, then automatically start them up. Is there no way the console can be run in a Screen on Debian so I can view it as one would do with rTorrent etc? Or only through WebGUI?

Posted: **Thu May 21, 2009 5:31 am**

TehCrab wrote: Is there no way the console can be run in a Screen on Debian so I can view it as one would do with rTorrent etc? Or only through WebGUI?

Run the deluge daemon, then connect to it with:
deluge -u console
(That's the console ui, should be what you want)

Posted: **Thu May 21, 2009 5:39 am**

[ERROR ] 07:38:28 ui:84 No module named console.main
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.5/deluge/ui/ui.py", line 73, in __init__
from deluge.ui.console.main import ConsoleUI
ImportError: No module named console.main
[ERROR ] 07:38:28 ui:85 There was an error whilst launching the request UI: console
[ERROR ] 07:38:28 ui:86 Look at the traceback above for more information.

Posted: **Thu May 21, 2009 5:45 am**

apt-get install deluge-console

Posted: **Thu May 21, 2009 6:46 am**

Thanks, that work. But am lost as to what to do to setup whatever is required on my server. Got a Screen open with deluged and deluge -u console started, thats it thought haha.

Was reading on this post that I need to setup my deamon - within the forum there seem to be 2 seperate listed ways to achieve this:

1.Many of the commands are not working, for example: dd:5:respawn:su - dtor -c "/usr/bin/deluged -d -p 58846 &> /var/log/deluge/deluged.log" - I'm using Debian if that helps ><
2. The second method is through the use of; etc/defaults/deluge-daemon and /etc/init.d/deluge-daemon

From the above, which is the most optimal way? As per the first ones, the commands are not working...

Posted: **Thu May 21, 2009 1:42 pm**

Well, deluged is the deluge daemon, so you already have it running.
1. Appears to be an attempt to open the deluge daemon on the tor network. (not a good thing to do, IMO)
2. This is a method to launch deluged automatically on startup.

Really, what you have to do is configure the options of your daemon. I would recommend launching the gtkui or webui to configure your options.(i.e. queue setting, watch folder, network settings) You do not however need to leave any interfaces running once you have it set up properly.

Deluge Forum

Deluge startup troubles

Deluge startup troubles

Re: Deluge startup troubles

Re: Deluge startup troubles

Re: Deluge startup troubles

Re: Deluge startup troubles

Re: Deluge startup troubles

Re: Deluge startup troubles

Re: Deluge startup troubles

Re: Deluge startup troubles

Re: Deluge startup troubles