Error when running deluge GUI client

[Jazzepi]

When I run deluge to bring up the desktop GUI client I get an error complaining about multiple daemons running. I do not understand this. Before running the command I ran a ps -aux with grep to show all the processes with deluge in the name. As you can see I only have the grep, the web GUI, and the deluged daemon running. Why am I getting an error about having a second daemon running? I have classic mode disabled for the desktop GUI so the system shouldn't be trying to start up another daemon when I launch the desktop GUI.

Any help would be much appreciated. Everything appears to be working properly, I just like to clean up errors like this when possible.

This is the contents of the deluged.pid file.

Code: Select all

5288;58846

Code: Select all

mediacenter@media-center:~$ sudo ps -aux | grep deluge
mediace+   826  0.8  0.4 355992 66248 ?        Ssl  19:21   1:29 /usr/bin/python /usr/bin/deluge-web -l /var/log/deluge/web.log -L warning
mediace+  5288 10.0  0.5 432396 91816 ?        Ssl  20:50   9:18 /usr/bin/python /usr/bin/deluged -d -l /var/log/deluge/daemon.log -L info
mediace+  6572  0.0  0.0  13696  2136 pts/0    S+   22:22   0:00 grep --color=auto deluge

mediacenter@media-center:~$ deluge
/usr/lib/python2.7/dist-packages/deluge/ui/gtkui/listview.py:250: GtkWarning: gtk_tree_model_sort_set_sort_column_id: assertion 'header != NULL' failed
  self.treeview.get_model().set_sort_column_id(column_state.sort, column_state.sort_order)
[ERROR   ] 22:25:17 main:232 There is a deluge daemon running with this config directory!
[ERROR   ] 22:25:17 main:233 You cannot run multiple daemons with the same config directory set.
[ERROR   ] 22:25:17 main:234 If you believe this is an error, you can force a start by deleting /home/mediacenter/.config/deluge/deluged.pid.

[Cas]

Likely you have 'autostart daemon' enabled in connection manager.

[Jazzepi]

That appears to be the issue.

I think either the wording should be changed in the connection manager, or the the ERROR log statement should be omitted. The connection manager says "Automatically start localhost if needed" (emphasis mine) which implies that the system will do some kind of check, and if true, will boot up the daemon. My wild guess is that the check is an attempt to launch another daemon and then the exception from it failing is not being swallowed.

I'd either.

1. Change the wording to "Automatically start localhost".

XOR

2. Surround your call to making the new daemon with some kind of try catch and swallow the exception.

Great program otherwise. And thanks for the help!