I'm getting that too. This only happens when the plugin was loaded by the daemon (server) on startup. I'm testing with earlier versions, and it seems this bug has been there for some time.esplinter wrote: EDIT: I have just got this error when enabling/disabling the plugin
Code: Select all
[ERROR ] 02:44:30 rpcserver:303 Exception calling RPC request: 'CorePlugin.YaRSS2' Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 298, in dispatch ret = self.factory.methods[method](*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/core.py", line 510, in enable_plugin self.pluginmanager.enable_plugin(plugin) File "/usr/lib/python2.7/dist-packages/deluge/core/pluginmanager.py", line 82, in enable_plugin super(PluginManager, self).enable_plugin(name) File "/usr/lib/python2.7/dist-packages/deluge/pluginmanagerbase.py", line 151, in enable_plugin component.start([instance.plugin._component_name]) File "/usr/lib/python2.7/dist-packages/deluge/component.py", line 290, in start if self.components[name]._component_depend: KeyError: 'CorePlugin.YaRSS2'
It should work with no errors as long as you don't manually disable the plugin in the GTK Client. Is this correct?
Thanks for reporting this bug, it might not have been found if you hadn't

Edit: After some investigation I believe I can conclude that it's a bug in Deluge 1.3. The problem has to do with how it handles disabling plugins in the core. However, it looks like it has been fixed in master.
So to conclude, there really isn't much you can do about it.