Page 24 of 24
can't enable ltConfig, "ModuleNotFoundError: No module named 'core'"
Posted: Mon Sep 02, 2024 3:25 am
by ludog
Deluge download speed is very slow for me, ~100K/s, when my internet speed test shows ~50Mb/s. I'm trying to install ltConfig to improve this. I cloned the
github repo, and ran `python setup.py bdist_egg`, which created an egg file. Then opened Deluge and went to add new plugin and selected this egg file. But when I try to click the 'enable' icon beside ltConfig, nothing happens, and I see on the terminal where I launched Deluge, the error
Code: Select all
File "/usr/lib/python3/dist-packages/deluge/pluginmanagerbase.py", line 148, in enable_plugin
instance = cls(plugin_name.replace('-', '_'))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/louis/.config/deluge/plugins/ltConfig-0.3.1-py3.12.egg/ltconfig/__init__.py", line 46, in __init__
from core import Core as _plugin_cls
ModuleNotFoundError: No module named 'core'
Versions I'm using:
Code: Select all
$ deluge --version
deluge 2.1.2.dev0
libtorrent: 2.0.10.0
Python: 3.12.3
OS: Linux Ubuntu 24.04 noble
Re: can't enable ltConfig, "ModuleNotFoundError: No module named 'core'"
Posted: Mon Sep 02, 2024 7:45 am
by mhertz
That means deluge 1.x plugin.
The default branch(master) of ltconfig is for deluge 1.x. Clone/build the 2.x branch, so add '-b 2.x' to the git clone command-line.
However, don't need build it, unless wanted, as a release available on the github page. Normally often need rename the python version to match, but there's no python version in that release, so works out of the box even.
Hope helps.
Re: [Plugin] ltConfig v2.0.0
Posted: Sat Oct 26, 2024 9:20 am
by ambipro
I've created a thread explaining some of the main options that I've found effective at improving performance.
viewtopic.php?t=56921
Re: [Plugin] ltConfig v2.0.0
Posted: Wed Jan 01, 2025 8:11 am
by bebound
Is this plugin compatible with this docker image: lscr.io/linuxserver/deluge:latest ?
I tried installing it in the web UI, but an error occurred. Manually placing it in the plugin folder had no effect.
Code: Select all
deluge | 07:52:57 [ERROR ][deluge.ui.web.json_api :1672] 'NoneType' object has no attribute 'call'
deluge | Traceback (most recent call last):
deluge | File "/usr/lib/python3.12/site-packages/deluge/ui/web/json_api.py", line 157, in _handle_request
deluge | result = self._exec_local(method, params, request)
deluge | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
deluge | File "/usr/lib/python3.12/site-packages/deluge/ui/web/json_api.py", line 119, in _exec_local
deluge | return meth(*params)
deluge | ^^^^^^^^^^^^^
deluge | File "/usr/lib/python3.12/site-packages/deluge/ui/web/json_api.py", line 950, in upload_plugin
deluge | d = client.core.upload_plugin(filename, plugin_data)
deluge | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
deluge | File "/usr/lib/python3.12/site-packages/deluge/ui/client.py", line 548, in __call__
deluge | return self.daemon.call(self.base, *args, **kwargs)
deluge | ^^^^^^^^^^^^^^^^
deluge | AttributeError: 'NoneType' object has no attribute 'call'
Re: [Plugin] ltConfig v2.0.0
Posted: Wed Jan 01, 2025 8:19 am
by ambipro
Yes, it works with that image. You'll need to place it in the plugins directory and enable it.
If you are using the thin client, you'll also need it in your local plugins directory to interact with it.
The error you show seems to indicate uploading the plugin over the webui isn't working, but once again if you just put it in your plugins directory it will be listed in plugins and you can enable it.
Re: [Plugin] ltConfig v2.0.0
Posted: Wed Jan 01, 2025 2:21 pm
by bebound
ambipro wrote: ↑Wed Jan 01, 2025 8:19 am
Yes, it works with that image. You'll need to place it in the plugins directory and enable it.
If you are using the thin client, you'll also need it in your local plugins directory to interact with it.
The error you show seems to indicate uploading the plugin over the webui isn't working, but once again if you just put it in your plugins directory it will be listed in plugins and you can enable it.
Thanks. Putting the egg file to `/config/plugins/` works.