Custom Query (2449 matches)

deluged in server with init script.

When it starts the init script, in log file appears this warning several times:

[WARNING ] config:405 Unable to open config file: /xxx/.config/deluge/label.conf

But that config file exist.

And, sometimes, when I stop the deluged (with init script), it shows, in log file:

[WARNING ] config:405 Unable to open config file: /xxx/.config/deluge/core.conf

But that config file exist too.

All these are only warnings, incorrect, but only warnings. Deluged starts. But the real problem is that today, I rebooted the machine but deluged didn't start, I saw the log file:

[ERROR ] config:405 Unable to open config file: /xxx/.config/deluge/core.conf

I didn't change anything and I executed:

sudo /etc/init.d/deluge-daemon start

And deluged started well this time!

Well, I think it's necessary to review the code, don't you think?

(Sorry for my bad english. I'm spanish)

After upgrading to 1.2.1 the menu bar is no longer visible. Actually is there because if I press ALT-F the submenus appear. See screenshot.

I have a Ubuntu 9.10 client/server setup with Deluge 1.2.1

I enabled email notification using the remote GTK client and it works fine when I have it running in the background. If I suspend my laptop, torrents that complete while it sleeps do not send any notification email.