id summary reporter owner description type status priority milestone component version resolution keywords cc 1163 config:405 Unable to open config file simonbcn "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'')" bug closed major 1.3 Core 1.2.1 Invalid