*OLD-THREAD - SEE NEW* [Unofficial] Deluge 2.0.x installer

[Paralel]

Thanks again, mhertz, for all your hard work. I hope the people that maintain deluge will strongly consider endorsing your installer as the official installer for Windows. I have no doubt it would make many deluge users happy.

[mhertz]

You're of course very welcome mate and thanks again for your kind words, appreciated! Also, thanks for registering the forum and letting me know about the openssl version issue. Take care

[idiocracy]

Is it recommended to uninstall previous version first?

Installed it, but keep getting an error about thin client import error, and it just closes when i click "no". If i click yes, then almost all options are disabled, like "add torrent" is greyed out. I uninstalled old version first.

[mhertz]

I'm sorry to hear that??? I have tested the installer in two different win10 VMs installed from latest microsoft ISO(build 1903 may2019), and I also tested on physical win7 machine of a family-member. Also I just now made a new completely clean win10 install in a new VM(using latest win10 ISO), and it works fine there also, so i'm sorry but I really am baffled about this report?

I'm guessing you're talking about the alternative installer with latest libtorrent v1.2.1, as you stated before your trackers where all https, so needing that version then.

To troubleshoot this, then could you please obtain a debug-log:

Copy the two lines posted here further down. Press win+r, type "cmd" and press return. Press ctrl+v followed by return.

When you have experienced the deluge-error then close deluge and the command-prompt window.

Code: Select all

cd "%programfiles%\Deluge2\gvsbuild\release\bin"
"%programfiles%\Deluge2\Scripts\deluge.exe" -L debug -l %userprofile%\deluge.log

Paste lines with "Error" preceding, or the whole log, back here, thanks. The log is stored in: 'C:\Users\<username>\deluge.log'.

[idiocracy]

I'm sorry to hear that??? I have tested the installer in two different win10 VMs installed from latest...

Appeared to be an issue with roaming/deluge, deleting that and it worked.
What happened was that the daemon connect popped up and and required it to connect, you could close it but if you did nothing in the UI would be functional.

Btw, that plugin that you updated for me, it did not work. Using argument -L info -l "xxx\xxx\xxx\deluge\deluge.log" to enable log for the plugin.

Code: Select all

03:36:39 [ERROR   ][deluge.pluginmanagerbase          :154 ] Unable to instantiate plugin 'AddTorrentCheck' from 'c:\\users\\volta\\appdata\\roaming\\deluge\\plugins\\addtorrentcheck-0.2-py3.6.egg'!
03:36:39 [ERROR   ][deluge.pluginmanagerbase          :1343] No module named 'webui'
Traceback (most recent call last):
  File "c:\program files\deluge2\lib\site-packages\deluge\pluginmanagerbase.py", line 148, in enable_plugin
    instance = cls(plugin_name.replace('-', '_'))
  File "c:\users\volta\appdata\roaming\deluge\plugins\addtorrentcheck-0.2-py3.6.egg\addtorrentcheck\__init__.py", line 56, in __init__
    from webui import WebUI as _plugin_cls
ModuleNotFoundError: No module named 'webui'
03:36:39 [ERROR   ][deluge.core.eventmanager          :43  ] Event handler TorrentAddedEvent failed in <bound method Core.post_torrent_add of <addtorrentcheck.core.Core object at 0x0000021A4DBA0E10>> with exception 'TorrentManager' object has no attribute 'session_started'
03:36:39 [ERROR   ][deluge.core.eventmanager          :43  ] Event handler TorrentAddedEvent failed in <bound method Core.post_torrent_add of <addtorrentcheck.core.Core object at 0x0000021A4DBA0E10>> with exception 'TorrentManager' object has no attribute 'session_started'

This is an example of what it looks like.

Code: Select all

[INFO    ] 01:50:17 core:60 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd)(6.42300009727) : xxxxxxxxxxx: Error: unregistered torrent
[INFO    ] 01:50:22 core:68 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd) : Updating Tracker
[INFO    ] 01:50:23 core:60 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd)(12.4260001183) : xxxxxxxxxxx: Error: unregistered torrent
[INFO    ] 01:50:28 core:68 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd) : Updating Tracker
[INFO    ] 01:50:29 core:60 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd)(18.4290001392) : xxxxxxxxxxx: Error: unregistered torrent
[INFO    ] 01:50:34 core:68 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd) : Updating Tracker
[INFO    ] 01:50:35 core:60 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd)(24.4290001392) : xxxxxxxxxxx: Announce Sent
[INFO    ] 01:50:40 core:68 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd) : Updating Tracker
[INFO    ] 01:50:41 core:60 [AddTrackerCheck](09d34a8b91b52563928f0d3f8116a9ed0dc38ccd)(30.4290001392) : xxxxxxxxxxx: Announce OK

[mhertz]

That's a bummer, i'm sorry to hear my fix didn't make the plugin functional afterall! Originally, the plugin couldn't be enabled at all, and then I made a change that made it to be correctly enabled, as simply renaming wasen't enough and needed a small code-change, and then after that change, then the log stated the plugin is enabled and running, in the beginning of starting deluge. That's why I stated at the time that I had fixed it to be initially enabled and no errors, but couldn't test if it was working in practise because I have no torrents unregistered when using public torrents.

I now again downloaded two public torrents to check, an archlinux and a debian ISO, and no error shown from the plugin, but I also didn't get any messages from it after the initial "plugin enabled" message, because never triggered the unregistered torrent criteria.

I don't know if I would be able to update the plugin correctly honestly, and without access to proper "testcases"(torrents triggering unregistered message), then I would for sure not be able to, as woud be working blindly.

Sorry

[idiocracy]

That's a bummer, i'm sorry to hear my fix didn't make the plugin functional afterall! Originally, the plugin...

Actually you can test it, because it'll run on every torrent added no matter if you get "unregistered" or not. In that case it will look like this. But you are correct that you can't test the actual 5 sec delay for "unregistered", but that's secondary as the issue right now is the plugin not working at all.

Code: Select all

[INFO    ] 19:51:29 core:74 [AddTrackerCheck](2b10c996fea3973c65a298365915f223a69909b6) : Adding New Torrent
[INFO    ] 19:51:29 core:60 [AddTrackerCheck](2b10c996fea3973c65a298365915f223a69909b6)(0.442000150681) : 
[INFO    ] 19:51:34 core:68 [AddTrackerCheck](2b10c996fea3973c65a298365915f223a69909b6) : Updating Tracker
[INFO    ] 19:51:34 torrentmanager:540 Torrent torrent_directory_name added by user: 
[INFO    ] 19:51:35 core:60 [AddTrackerCheck](2b10c996fea3973c65a298365915f223a69909b6)(7.09800004959) : 
[INFO    ] 19:51:40 core:68 [AddTrackerCheck](2b10c996fea3973c65a298365915f223a69909b6) : Updating Tracker
[INFO    ] 19:51:44 core:60 [AddTrackerCheck](2b10c996fea3973c65a298365915f223a69909b6)(16.0069999695) : trackerURL: Announce OK

So basically you'd just add any torrent, public or not and look for that in the log.

Secondary request. Could you export a "torrentmanager.pyc" where this part is changed from default into this? If it's the same in deluge 2.

Code: Select all

        # Save the state and resume data every ~3 minutes.
        self.save_state_timer.start(1200, False)
        self.save_resume_data_timer.start(1190, False)

Sorry if i'm asking too much of you.

[mhertz]

Hmm, I was thinking that too, but in three runs I never got any message from plugin other than it was found and enabled, that's it. I use "debug" logging because it is the "highest" logging-form, and gets all messages, no matter if info, warning, error or whatever. I did now try a 4'th time just in case with selecting "info" logging like you, but still no messages from plugin like you state and the messages shown I allready got in previous debug-runs.

Puzzling indeed???

[idiocracy]

So if you're aren't getting the message when adding a random torrent, then the plugin is not running. Why i do not know, i simply don't have enough knowledge about deluge 2 and python 3.
But i am guessing it might have something to do with "No module named 'webui", some changes in deluge 2 perhaps?

[mhertz]

Hmm, I guess you're right...

As said, originally, it couldn't be enabled and the log stated unable to ectivate plugin because no module named ".core" and I fixed that and then the error was not shown anymore and now instead shows:

Code: Select all

18:06:57 [DEBUG   ][deluge.ui.gtk3.pluginmanager      :68  ] Core has these plugins enabled: ('AddTorrentCheck',)

However, as you said, it doesn't work then, if not getting any messages later.

However, what I just don't understand is two things:

1. Why I get no error, like you had in log then???
2. How the f*** can we both have differing results with same versions???

Wait, are you using the first installer posted, or the second i.e. libtorrent 1.1.13 or 1.2.2. I seem to remember getting more debug-messages last time I checked it, a week ago or something, about the plugin being loaded correctly, but I used another libtorrent version then than now, but still, I got no errors back then either. I'm talking about libtorrent 1.1.13 vs now using libtorrent 1.2.2.

Anyway, I have to go, will look at it later.