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

[rav]

Hi rav, I appreciate that, thanks mate, and you're very welcome

Hi, it's an unexpected return

Thank you very much for your time and work.

I only tried with the second one, Nordic-2. After leaving Deluge I installed it normally, the default directory being the right one. Then I opened Deluge, there was no change. I now have a data directory, and inside settings.ini, the value is on Nordic.

So, I don't understand why I don't see the new theme?

[mhertz]

I'm sorry, I should obviously have asked you if you where using a new'ish build of my installer, but rereading your post, you already stated it was something you've used for a while, so should've paid better attention, or atleast asked you first, as stated. The issue is that I recently changed top-folder name for the gtk3 and such files, from 'gvsbuild\release' to simply 'data'.

Anyways, you said you tried the second one, so I guess you're after that one(without GTK_CSD=0), which also is the only one I can make you currently, before knowing if you are using a python 3.7.x or python 3.8.x based version, as they have differences in the code-line of one of the files I need replacing, and your installed version was made in both python versions, but if not needed then just disregard.

Here's the exe, which was named nordic-2.exe before, but now just nordic.exe: http://s000.tinyupload.com/index.php?fi ... 8667562375

Also, alternatively, if you rather want a zip and do it manually, then here's the theme in Nordic folder zipped up: http://s000.tinyupload.com/index.php?fi ... 8850089130

The exe of course is automatic, and if using that, then disregard the rest of this post's instructions, as don't apply.

For the zip, then needs extracted to: 'INSTALL-DIR\gvsbuild\release\share\themes\Nordic'(so there's a 'gtk-3.0' folder right under the Nordic folder there).

Lastly, editing is needed on this file: 'INSTALL-DIR\gvsbuild\release\etc\gtk-3.0\settings.ini', from 'gtk-theme-name=mantis' to instead 'gtk-theme-name=Nordic'.

Hope I didn't miss anything this time

[rav]

Sorry for my inaccuracies and technical incompetence, I wouldn't have been able to tell you if I'm on a python 3.7.x or python 3.8.x based version, but now the theme works perfectly

Again thank you so much for your work and your time.

https://i.imgur.com/86UJh4i.jpg

[mhertz]

Thanks alot mate, appreciate that and you're most welcome of course, and was my fault, not yours, but nice of you to say.

That looks nice btw I'm thinking about including that theme actually, though I do have to many checkboxes as is already(had to use special win32 api call to raise its dialog, so not needing scroll down to see all, as NSIS regular commands only went so far, though googled the code to use, as not that clever myself honestly, like most stuff with these installers) so thanks also for bringing it to my attention as didn't knew it, and if nothing else then people reading your posts/pics can add it themselves.

@all, new openssl 1.1.1g released today with security fix added(DOS attack), so will rebuild installers with it, but will not be able to do that before tomorrow, and will update this post with an edit to state its done. Also updates libtorrent 1.2.x while add it, but of the three added commits since 1.2.6, then only one relevant to deluge usage, and not really important, but regardless(IPv6 address change detection). Also, there's some commits added to deluge develop branch, one of them was already included in both installers here(disable annoying gettext warning on console/log), but several other commits added, though not very important ones, but nonetheless really nice to see development picking up again: https://git.deluge-torrent.org/deluge/log/?h=develop

Edit: Done.

[matthew.monacelli]

Hello. I am new here and got through setting up the deluge service on my server just to find out that there isn't a Windows client available (officially). Is the executable download on the first page of what I need to install? Are there any prerequisites? Once installed, I tried executing the deluge.exe in the scripts folder but nothing happens. Any assistance getting running would be much appreciated!

On a side note, is it more recommended to build from source myself? Thanks again.

[mhertz]

Hi Matthew and welcome onboard(deluge forum)

If you want to try this unofficial installer, then yes, link on first page, where there's two to choose between i.e latest stable or latest dev deluge 2.0.x.

There's no prerequisites, except recommended backup old deluge profile if having such, uninstall old deluge1 if having such, and install one of these installers. This is also written on first page btw, and is always kept up-to-date, so not having to go through mostly my long ramblings and documentations about what's going on internally.

I don't understand what you mean with "Once installed, I tried executing the deluge.exe in the scripts folder but nothing happens" ? There's no scripts folder in my installers. Do you refer to manual source build/install, which will provide such a scenario? In that case, then you're missing something, e.g gtk3, msvc runtimes or libtorrent py bindings, and/or sometimes need delete old session.state from deluge profile folder, if having such(old deluge bug).

Yes it would be more recommended to build from source id say/think, instead of using/trusting 3rd party unofficial installers. This is just something to try out if wanted, that's all Recommended would be official installer, or build from source id say.

[fmar]

Hi mhertz,

the plugin renaming wasn't that big of an issue, just a bit annoying. Having made backups before upgrading it just took me a while to figure out what was wrong. I also consider your installer kind of a beta version - no offense meant - it's fine for me if something isn't working right out of the box.

...
About libtorrent 123+, do you refer to the tracker error issue regarding your VPN, or something bigger, like no connection at all? If the latter, then I for sure need keep that 1.2.3 version in, as was speculating if should remove it possibly. If the former, then I made a ticket on libtorrent's github about it, and got explained it's normal and no issue and a deluge error to show this as an actual error for said tracker in question as just simply lo failing connect, obviously, but main connection connects fine(so error can be fully ignored). I've submitted ticket also of this deluge issue, to deluge bugtracker afterwards getting that reply from Arvid.

I don't remember it in every detail, but with libtorrent 1.2.6 I was getting no connection to the tracker. I checked the process details with Process Explorer and noticed that Deluge tried to open IPv6 connection, although I had the protocol disabled in Windows and the router. With libtorrent 1.2.3 those IPv6 connections wouldn't even appear. I was able to activate and deactive the VPN and the tracker status would just update. It looked like libtorrent was trying to connect to an interface that wasn't there.

Could you post your bug report for libtorrent? I'd like to give it a detailled test and see what's what.

Is there any quick way of exchanging the libtorrent version if installed? Like chaning certain files to change from libtorrent 1.2.6 to libtorrent 1.2.3. Would you know how to do that? I could then test if it was the VPN or just the Python upgrade (and necessary plugin renaming).

[mhertz]

The plugin renaming is a general deluge issue which the official installers always had whenever updating its backend python version, so just wanted to clarify for people reading this that it's not something that I introduced. I didn't have to update python of-course, but there where fixes that both affected stability and performance, plus I prefer using newest stable of everything possible. I did mention the issue on first page too, but understand not everyone re-reads that of-course, after the first time read, but I continually update it(114 times as of now, lol - I believe though I'm slightly OCD too )

Yes, considering these installers beta is accurate, I'd agree, and no offense taken the least I appreciate the feedback also.

Here's libtorrent bug report: https://github.com/arvidn/libtorrent/issues/4529
And following that, deluge's: https://dev.deluge-torrent.org/ticket/3384

Libtorrent 1.2.3+ changed the way they announce to trackers and bind to interfaces, to be multi-homed I believe(tries all interfaces found which supports incoming connections, which wasent like that previously). In those versions you often see a tracker showing as error, and if checking the tracker tab at the bottom, then states as status: "The system cannot open the device or file specified ". It sometimes goes out of that error state some time later and then returns again later. Checking debug logs show some announces succeed and others don't, and as lo is one of the interfaces checked, then that will obviously fail, as no outgoing internet acces possible for lo of course. This is therefore I included 1.2.3 for people either annoyed of that error showing, or don't know this and thinks it's an actual error(like myself initially too), though I mentioned it too on first page when found out. It sounds like your issue is different though, but would be nice if you could test it again, thanks.

Btw, I added a shot at end of post showing issue with trackers in deluge with libtorrent 1.2.3+, and here where using VPN and libtorrent 1.2.6. Hmm, come to think of it, i'm now coming to question if deluge actually is doing something wrong or not with showing that error. I mean, as Arvid said, it shouldn't list tracker as in error, if only one of the announces fail while others doesn't, but does deluge do that here in GTKUI? I'm not used to GTKUI, and so don't know if it means the tracker is in error "fully", or only one announce was in error and others not(which would be correct way, if even listing the error at all, i'm not fully sure if even should do that, but atleast should signal that it's still working regardless, which i'm in doubt about if already does)? Anyway, I have submitted a bug-report as said to deluge bug-tracker, and if wrong, then it will just be closed without further fixing needed of-course.

Anyway, you can manually change libtorrent's out, by replacing/renaming back and fourth. The relevant file for this is 'INSTALL-DIR/Lib/site-packages/libtorrent.pyd. If you ever get an issue starting deluge after changing libtorrent version, then it's an old deluge bug which can be fixed by deleting session.state in your deluge profile-dir.

Edit: Will update with download link shortly, of zipped-up archive of the three provided libtorrent's from installers, as wrote above not on computer.

Edit2: http://s000.tinyupload.com/index.php?fi ... 0891994268

[mhertz]

A few more commits(3 total) to deluge develop branch today too(nice! ), though not that important, but check yourself the commit log if curious, and also a new commit to libtorrent might as well include while add it about fixing handshake-timeout for peers.

Deluge develop branch commit-log:
https://git.deluge-torrent.org/deluge/log/?h=develop

Libtorrent RC_1_2 branch commit-log:
https://github.com/arvidn/libtorrent/commits/RC_1_2

Just like with libtorrent, then i'm not gonna make update notes here whenever updating deluge's develop build installer, as seem like is picking up now, of-course unless something important needing to be mentioned, just like with libtorrent, so again, please monitor commit logs above and compare to installer last modified date of installer link, if curious that is, so i'm not spamming this thread more than already

[fmar]

@mhertz

Thank you for the thorough and extensive reply, very much appreciated. And thank you for the neat libtorrent ZIP!

The plugin renaming is a general deluge issue ...

No worries. I wrote the post about my upgrading issues, looked on your updated first post and slapped my forehead

...libtorrent, VPN & tracker status

I did test the VPN connection with libtorrent 1.2.3 and 1.2.6 and had no issues this time. So I assume it was related to my updating issues with the label plugin (Python 3.7 to 3.8).
Both libtorrent versions connected fine and I could see the client being connected to the tracker on the corresponding web site.

But the one thing I noticed was the huge amount of tracker status errors with libtorrent 1.2.6.
I had the same issue with 1.2.5, the errors resolved itself and came back continuosly. The tracker itself showed that my client was connected though and was able to down- and uploading.
The tracker status in Deluge reported either a connection error or a "file not found/path not found" error. That is probably what you wrote about in your bug reports you linked. This is probably just a GUI error in Deluge displaying an error message because it's getting a tracker response for multiple interfaces. I added a comment in your bug report and won't spam this thread anymore

PS: The IPv6 connections that I wrote about in my last post were unconnected, so not relevant at all.