Deluge Windows Builds

Specific support for Deluge on Microsoft Windows OS
MadMungo
New User
New User
Posts: 2
Joined: Wed Apr 27, 2022 12:37 pm

Re: Deluge Windows Builds

Post by MadMungo »

Hello,

Using the latest Windows 10 x64 deluge build, 2.1.0dev90, from this thread and noticed that in the deluge client Settings>Queue I cannot set the "Share Ratio" to 0.00 anymore, it keeps repopulating to 0.50.
I have the following set in my core.conf file
"stop_seed_at_ratio": true,
"stop_seed_ratio": 0.0, < This remains as is.

It is working with 2.04.dev51.
mhertz
Moderator
Moderator
Posts: 1505
Joined: Wed Jan 22, 2014 5:05 am
Location: Denmark

Re: Deluge Windows Builds

Post by mhertz »

It's hardcoded to not go under 0.5 in gtkui yes, as previously, but if changing core.conf and never opening gtkui preferences(which triggers the limit check of gtkui), then works without limit(as no limit otherwise in deluge itself, nor in it's other two ui's). Every time opening gtkui preferences then setting reversed to limit if under(first written to core.conf upon closing if remember correct), so either need reconfigure core.conf with deluge closed(or if running thinclient then could use deluge-console's 'config' command to revert it back while still running), or alternatively change the source of one of the ui gtk.builder files of gtkui to remove limit, to fully overcome.
MadMungo
New User
New User
Posts: 2
Joined: Wed Apr 27, 2022 12:37 pm

Re: Deluge Windows Builds

Post by MadMungo »

Thanks for the info.
I edited Deluge-2.10dev96\deluge\ui\gtk3\glade\preferences_dialog.ui and set adjustment_share_ratio to 0.0 to have control over that setting. Now works as expected.

without editing the ui file and starting deluge it would always set share ratio to 0.5 no matter what core.conf had set when adding torrents, this is without opening gtkui preferences.
mhertz
Moderator
Moderator
Posts: 1505
Joined: Wed Jan 22, 2014 5:05 am
Location: Denmark

Re: Deluge Windows Builds

Post by mhertz »

Thanks for the info.
I edited Deluge-2.10dev96\deluge\ui\gtk3\glade\preferences_dialog.ui and set adjustment_share_ratio to 0.0 to have control over that setting. Now works as expected.
You're very welcome mate :) Sorry for not posting the actual file to edit previously, but good job finding and fixing this.
without editing the ui file and starting deluge it would always set share ratio to 0.5 no matter what core.conf had set when adding torrents, this is without opening gtkui preferences.
With all due respect, it doesn't, so something must be wrong in the way you're testing this. If i'm wrong, then I do apologize in advance, but i'm as close to 100% sure upon this as I possible can be, imho. There have been no changes to code regarding this logic, and I also retested it now upon latest doadin unofficial installer, with same result as always.
  • Backup '%appdata%\deluge' with deluge(and it's daemons if running) closed(e.g. just rename it to Deluge-bak).
  • Delete '%appdata%\deluge'(skip this step if renamed it in previous step).
  • Start deluge.exe and stop again when opened.
  • Edit newly generated '%appdata%\deluge\core.conf'.
  • Start deluge.exe and stop again when opened.
  • Open '%appdata%\deluge\core.conf' and see the 'stop_seed_ratio' setting still is '0.0' - This will continue until opening preferences in gkui(even without actually changing anything there and just pressing cancel, still reverts to 0.5).
  • Delete '%appdata%\deluge' and move your backup folder from step 1 back there to restore(or rename 'Deluge-bak' back to 'Deluge' if had done the rename in step 1).
Btw, as you have already installed and changed deluge, then if wanting test this again, then can just extract the installer with 7-Zip(since supports NSIS installer decompression) and run deluge.exe from it's extracted folder. Little easier for quick testings, and just delete extracted folder again afterwards.

Anyway, you got it working for you regardless, which is the most important thing of-course, and so was just posting to elaborate a little upon this :)
sharmanhall
New User
New User
Posts: 2
Joined: Sun May 01, 2022 8:20 am

Re: Deluge Windows Builds

Post by sharmanhall »

I have some issues with all of the deluge 2.x installers I have used.
Current one I tried was deluge-2.1.0.dev59-win64
  1. I cannot get ItConfig 2.0 to work. The main issue is when I select it and apply Deluge crashes.
sharmanhall
New User
New User
Posts: 2
Joined: Sun May 01, 2022 8:20 am

Re: Deluge Windows Builds

Post by sharmanhall »

Also, there is an issue with the PS1 script wherein I cannot download the NSIM package.

Code: Select all

if ( -not (Test-Path 'C:\DelugeDownloads\nsis-3.08.zip' -PathType Leaf) ) { 
        Write-Host "Downloading NSIS..."
        $WebClient.DownloadFile("https://phoenixnap.dl.sourceforge.net/project/nsis/NSIS%203/3.08/nsis-3.08.zip","C:\DelugeDownloads\nsis-3.08.zip")
    }
I cannot get the URL for NSIS to download:
https://phoenixnap.dl.sourceforge.net/p ... s-3.08.zip

Rather, you may want to use this URL:
https://downloads.sourceforge.net/proje ... s-3.08.zip

Unless there is a particular reason you decided to use "phoenixnap"?
mhertz
Moderator
Moderator
Posts: 1505
Joined: Wed Jan 22, 2014 5:05 am
Location: Denmark

Re: Deluge Windows Builds

Post by mhertz »

sharmanhall wrote: Sun May 01, 2022 8:37 am I have some issues with all of the deluge 2.x installers I have used.
Current one I tried was deluge-2.1.0.dev59-win64
  1. I cannot get ItConfig 2.0 to work. The main issue is when I select it and apply Deluge crashes.
For me it works, and I know several here likewise, so not a general problem atleast - I too tried your exact version to make sure again just now, with same result.

Check if debug-logging catches your issue('deluge.exe -L debug -l "%userprofile%\Desktop\deluge.log"'), or e.g. run deluge-debug.exe from a cmd and copy/paste the error here, if wanted.

Btw, alot of crashing, especially deluge2 seemingly(though not solely), is related to yarss2 plugin as far as i've noticed(well, seen reported I mean, as don't use myself), with also open bug-reports on yarss2 bug-tracker about this, with echo's from affected users.

Last, i'd try with a fresh profile just in case, so e.g. rename '%appdata%\Deluge' to '%appdata%\Deluge-bak' with deluge closed, for a quick test(start/stop deluge to generate new profile-dir, copy ltconfig over from old to new dir and test again).
Post Reply