*OLD-THREAD - SEE NEW* [Unofficial] Deluge 2.0.x installer
Re: [Unofficial] Deluge 2.0.x installer.
Installed latest with lib 1.2.4.0 and everything appears to work fine.
Re: [Unofficial] Deluge 2.0.x installer.
Thanks alot mate appreciate the feedback from affected user
I'll then based on this, remove libtorrent 1.2.3 next time I rebuild, which will be one of these days. Thanks again.
Edit: Sorry idiocrazy, got confused slightly there and presumed you where one of the three reporting the tracker-issue previously, but just went back 10 pages and I believe you wasn't, so sorry for confusion and I of course appreciate the feedback regardless
I'll then not ditch libtorrent 1.2.3 just yet and will wait on feedback from affected users, or if more people confirm issue fixed on libtorrent github.

Edit: Sorry idiocrazy, got confused slightly there and presumed you where one of the three reporting the tracker-issue previously, but just went back 10 pages and I believe you wasn't, so sorry for confusion and I of course appreciate the feedback regardless

I'll then not ditch libtorrent 1.2.3 just yet and will wait on feedback from affected users, or if more people confirm issue fixed on libtorrent github.
Re: [Unofficial] Deluge 2.0.x installer.
Libtorrent now bumped to version 1.2.5 release, in git commit log of RC_1_2 branch, though not yet updated elsewhere, and even though my installer already is up-to-date, then as usual I rebuilt anyway to get the "libtorrent 1.2.5" showing under deluge's 'Help > About' menu.
I decided to ditch the extra libtorrent 1.2.3, so now as usual only latest 1.2.x and 1.1.x available, as no new issue-reports lately on libtorrent github, or here, but if someone still has that tracker-issue, then let me know and I will re-add it again.
I decided to ditch the extra libtorrent 1.2.3, so now as usual only latest 1.2.x and 1.1.x available, as no new issue-reports lately on libtorrent github, or here, but if someone still has that tracker-issue, then let me know and I will re-add it again.
Re: [Unofficial] Deluge 2.0.x installer.
I'm having an issue where my uploads / downloads are at 0kb/s. When I first installed deluge 2.03 using your installer over my existing install, it was working fine. But after restarting my computer, I'm not transferring data in either direction.
I've tried adding all the individual .EXE files in the Deluge folder to my firewall exceptions, and I've tried connecting to different VPN servers, all to no avail.
Notably, my "Active Port" under Incoming displays as "0" despite my having a port specified. Specifying a new port or setting it to random doesn't affect this.
Edit: After attempting to open the old client, my torrents have now disappeared from both versions of the client. Thankfully, there was an archived state and I was able to restore it, but I'm not sure what caused the issue and how to prevent it from happening again. Still unable to send or receive data with v2.03
I've tried adding all the individual .EXE files in the Deluge folder to my firewall exceptions, and I've tried connecting to different VPN servers, all to no avail.
Notably, my "Active Port" under Incoming displays as "0" despite my having a port specified. Specifying a new port or setting it to random doesn't affect this.
Edit: After attempting to open the old client, my torrents have now disappeared from both versions of the client. Thankfully, there was an archived state and I was able to restore it, but I'm not sure what caused the issue and how to prevent it from happening again. Still unable to send or receive data with v2.03
Re: [Unofficial] Deluge 2.0.x installer.
Sorry to hear it.
First, I apologize, I thought I had specified it better on first page with the download-link, but see now I haven't, and will change that. Using direct upgrades is supported for this installer, but not for installing over the old deluge1, only deluge2. Running both isn't neither supported, but I don't understand why the torrents got removed I must admit. There can be issues with getting torrents from deluge1 into deluge2 automatically, unless using the dev-installer, but as worked first, then don't know why not next time and also gone from both clients, so strange and I honestly don't know.
To remove the old deluge you can just delete it's folder(or going into it's folder under "%programfiles%(x86)" and run the deluge-uninst.exe there, as the uninstall entry under windows add/remove programs has been overwritten by my installer and points now to new deluge and not old).
I must admit I don't understand or know why worked firstly, but not after a reboot, but maybe the issue with libtorrent 1.2.3+ isn't fixed fully yet, as I once read one stating such on libtorrent bug-tracker(though stated it was fixed later) i.e. that his connection was not working at all, and not only tracker issues.
Could you please try using libtorrent 1.2.3 and see if that fixes it, and if so I'll add it back into installers again as optional choice.
Download libtorrent.pyd from underneath link and overwrite the other libtorrent.pyd under '$InstDir\Lib\site-packages\libtorrent.pyd'.
http://s000.tinyupload.com/index.php?fi ... 5895785446
If not that, then I honestly don't know, and you need running with debug-logging so we can see atleast what the error is, hopefully and then you need submit bug-ticket to deluge bug-tracker if so(if deluge error).
Again, i'm sorry for the "direct upgrading" issue, though as said, I don't understand how could delete your torrents, but always have a backup of your deluge profile folder, or atleast state, as I wrote in first post too.
Edit: Damn I didn't have that written anymore neither! Sorry again. I some time ago pruned that post to just the basics and most important, as have a tendency to blab on about pedantics, but was too aggressive there I see
I'll add that again too.
First, I apologize, I thought I had specified it better on first page with the download-link, but see now I haven't, and will change that. Using direct upgrades is supported for this installer, but not for installing over the old deluge1, only deluge2. Running both isn't neither supported, but I don't understand why the torrents got removed I must admit. There can be issues with getting torrents from deluge1 into deluge2 automatically, unless using the dev-installer, but as worked first, then don't know why not next time and also gone from both clients, so strange and I honestly don't know.
To remove the old deluge you can just delete it's folder(or going into it's folder under "%programfiles%(x86)" and run the deluge-uninst.exe there, as the uninstall entry under windows add/remove programs has been overwritten by my installer and points now to new deluge and not old).
I must admit I don't understand or know why worked firstly, but not after a reboot, but maybe the issue with libtorrent 1.2.3+ isn't fixed fully yet, as I once read one stating such on libtorrent bug-tracker(though stated it was fixed later) i.e. that his connection was not working at all, and not only tracker issues.
Could you please try using libtorrent 1.2.3 and see if that fixes it, and if so I'll add it back into installers again as optional choice.
Download libtorrent.pyd from underneath link and overwrite the other libtorrent.pyd under '$InstDir\Lib\site-packages\libtorrent.pyd'.
http://s000.tinyupload.com/index.php?fi ... 5895785446
If not that, then I honestly don't know, and you need running with debug-logging so we can see atleast what the error is, hopefully and then you need submit bug-ticket to deluge bug-tracker if so(if deluge error).
Again, i'm sorry for the "direct upgrading" issue, though as said, I don't understand how could delete your torrents, but always have a backup of your deluge profile folder, or atleast state, as I wrote in first post too.
Edit: Damn I didn't have that written anymore neither! Sorry again. I some time ago pruned that post to just the basics and most important, as have a tendency to blab on about pedantics, but was too aggressive there I see

Re: [Unofficial] Deluge 2.0.x installer.
Hi, is it possible for your build to render the font anti-aliasing in greyscale instead of RBG? Or for me to add an argument one or more of the config files?
Anti-aliasing in rgb looks pretty bad with dark themes, when I use Gnome in Manjaro I always switch from RGB to greyscale.
Anti-aliasing in rgb looks pretty bad with dark themes, when I use Gnome in Manjaro I always switch from RGB to greyscale.
Re: [Unofficial] Deluge 2.0.x installer.
Sorry, I cannot help with such, as have no idea honestly. A quick search didn't show some config option to change that, from the gtk config-file settings.ini under $InstDir/gvsbuild/release/etc/gtk-3.0, thats from memory as not on my computer, but you can maybe improve things with other options - I've just copy/pasted an example so don't know if looks good/better, so experiment yourself:
I don't know either if there's a setting to be used for this in windows? I mean change antialising method used.
Edit: I don't have time now, but there's options for changing rgb to greyscale font antialising in windows, so look up on a search if there's built in methods for that, either a setting or regweak etc, and if not, I found quickly this article about open-source third-party portable win10 app that does it, among other stuff to, but I don't know if gtk3 apps will use those settings though, but worth a try: https://www.ghacks.net/2019/11/02/bette ... indows-10/
Code: Select all
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle=hintfull
gtk-xft-rgba=rgb
gtk-font-name=Segoe UI 9
Edit: I don't have time now, but there's options for changing rgb to greyscale font antialising in windows, so look up on a search if there's built in methods for that, either a setting or regweak etc, and if not, I found quickly this article about open-source third-party portable win10 app that does it, among other stuff to, but I don't know if gtk3 apps will use those settings though, but worth a try: https://www.ghacks.net/2019/11/02/bette ... indows-10/
Re: [Unofficial] Deluge 2.0.x installer.
No worries, it's not a big issue, and other gtk ports like gedit for windows have issues with font rendering I found out this evening when investigation and learing more about gtk.
Gtk uses freefont and xft commands like I guess is hard to have working when porting over an application to a different OS.
Works for the gEdit port in Windows 10 which is good, but the title bar have no antialiasing or hinting whatsoever, so only the font in the main window is rendered with hinting and antialiasing.
Regaring Better ClearType Tuner 1.2, well like you thought, it doesnt affect gtk applications like deluge 2.
Out of curiosity I tried it, but from the source at Github. The conclusion is that Windows 10 is on point with ClearType! Especially with some DPI-scaling. Gnome-shell in linux does it very well too but not as good.
Thanks for you time and keep up the good work!!
Gtk uses freefont and xft commands like
Code: Select all
gtk-xft-rgba=none
Code: Select all
gtk-xft-rgba=none
Regaring Better ClearType Tuner 1.2, well like you thought, it doesnt affect gtk applications like deluge 2.
Out of curiosity I tried it, but from the source at Github. The conclusion is that Windows 10 is on point with ClearType! Especially with some DPI-scaling. Gnome-shell in linux does it very well too but not as good.
Thanks for you time and keep up the good work!!

Re: [Unofficial] Deluge 2.0.x installer.
@mhertz Overwriting with the libtorrent file you linked did in fact get my torrents downloading again, thank you!
When you say "back up your profiles", do you just mean make a copy of the entire %Appdata%\Roaming\deluge folder?
When you say "back up your profiles", do you just mean make a copy of the entire %Appdata%\Roaming\deluge folder?
Re: [Unofficial] Deluge 2.0.x installer.
Thanks for the feedback too, and you're very welcome 
Yes that's what I meant, though for most it's probably enough to backup the states folder in there to always get your torrents back in case of problems, but might as well take the whole folder as then all your settings, plugins and plugin settings etc also are backed up.
@all, so now I got confirmation of still something going on for some with libtorrent 1.2.3+ unfortunetly, courtesy of Wump(thanks), so I'll rebuild again with the added libtorrent 1.2.3 again as optional choise, and I'll just edit this page when building batch file stops in 5 minutes time.
@KrazyLurt, Thanks mate, appreciated, though sorry it didn't worked out unfortunately but thanks for posting your findings for others benefit
Edit: Finished bulding now, select libtorrent 1.2.3 or libtorrent 1.1.x instead of default libtorrent 1.2.x if having issues with connectivity. It should only be an issue for some, and those affected should either use a VPN or a multi-homed connection e.g. IPv4/IPv6 or otherwise multi-homed, as said I never experienced it though, neither with VPN and I have two different subscriptions(lifetimes gotten cheap, first missed port-forwarding so jumped on another later when came that had) or regular connection.
Edit2: just wanted to add again that dispite appearence the libtorrent and theme checkboxes actually are radiobuttons, so e.g if having issues with default libtorrent 1.2.x, then you cannot untick it, as you need a libtorrent installed(and theme) and then all would be unticked until/if you select another, which wouldn't make sence to me, hence this distinction in my scripting of this, so you instead need to tick another libtorrent, while the 1.2.x still is ticked, and thus then will untick 1.2.x automatically. I doubt anyone would have had issues with this and would be found out quickly by experimentation atleast, but just in case, I elaborated upon it more. If not done like this, then both it doesn't make sence to allow you untick all libtorrents, but also I would have needed added extra logic in the scripting for checking if you try select OK with all libtorrents unticked, or themes, and display error dialog and let you try again, instead of installing deluge without a libtorrent at all which wouldn't be able to start even.

Yes that's what I meant, though for most it's probably enough to backup the states folder in there to always get your torrents back in case of problems, but might as well take the whole folder as then all your settings, plugins and plugin settings etc also are backed up.
@all, so now I got confirmation of still something going on for some with libtorrent 1.2.3+ unfortunetly, courtesy of Wump(thanks), so I'll rebuild again with the added libtorrent 1.2.3 again as optional choise, and I'll just edit this page when building batch file stops in 5 minutes time.
@KrazyLurt, Thanks mate, appreciated, though sorry it didn't worked out unfortunately but thanks for posting your findings for others benefit

Edit: Finished bulding now, select libtorrent 1.2.3 or libtorrent 1.1.x instead of default libtorrent 1.2.x if having issues with connectivity. It should only be an issue for some, and those affected should either use a VPN or a multi-homed connection e.g. IPv4/IPv6 or otherwise multi-homed, as said I never experienced it though, neither with VPN and I have two different subscriptions(lifetimes gotten cheap, first missed port-forwarding so jumped on another later when came that had) or regular connection.
Edit2: just wanted to add again that dispite appearence the libtorrent and theme checkboxes actually are radiobuttons, so e.g if having issues with default libtorrent 1.2.x, then you cannot untick it, as you need a libtorrent installed(and theme) and then all would be unticked until/if you select another, which wouldn't make sence to me, hence this distinction in my scripting of this, so you instead need to tick another libtorrent, while the 1.2.x still is ticked, and thus then will untick 1.2.x automatically. I doubt anyone would have had issues with this and would be found out quickly by experimentation atleast, but just in case, I elaborated upon it more. If not done like this, then both it doesn't make sence to allow you untick all libtorrents, but also I would have needed added extra logic in the scripting for checking if you try select OK with all libtorrents unticked, or themes, and display error dialog and let you try again, instead of installing deluge without a libtorrent at all which wouldn't be able to start even.