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

[echelon]

@Jerrk
I am using blackish theme called Mojave


Probably useful to use it as your base by changing the *.css

Uploaded in here :

Code: Select all

https://mega.nz/#!ccNQFYLb!XX6xrPfk0s4B_ntX_4ZsLjsipNCRGLwcVktdRE_LWvM

Extract it to C:\Program Files\Deluge2\gvsbuild\release\share\themes .
And edit/create the C:\Program Files\Deluge2\gvsbuild\release\etc\gtk-3.0\settings.ini into :

Code: Select all

[Settings]
gtk-theme-name = Mojave

# Not necessary for Mantis, but nice
# for playing around with other themes
gtk-application-prefer-dark-theme=true

# OLD #
# gtk-theme-name=win32

There are many of gtk3 themes that you can find in https://www.gnome-look.org/browse/cat/135/order/latest/

To use it from website above is easy create the following directory structure inside the C:\Program Files\Deluge2\gvsbuild\release\share\themes folder :

Code: Select all

Theme_Name
-------------------gtk-3.0

So inside the theme_name folder you need to put "gtk-3.0" sub-folder then put all of the required files and folder inside the gtk-3.0 sub-folder. And don't forget to edit C:\Program Files\Deluge2\gvsbuild\release\etc\gtk-3.0\settings.ini.
Just in-case you didn't know and for others knowledge.

[mhertz]

Arvid still isn't sure about the tracker issue, and cannot reproduce it neither, but suspects there can be an issue for certain network setups, so he just submitted a patch for testing, as a pull-request under new testing branch get_gateway, which I just built.

If anyone having this issue could please test this build out and report back, then I will foreward it to Arvid and add to installers. Thanks in advance.

Libtorrent RC_1_2+0e2edd7:
http://s000.tinyupload.com/index.php?fi ... 2701255903

Extract and overwrite libtorrent.pyd in '<INSTALL-DIR>\Lib\site-packages' folder. If getting an error when starting deluge again, then delete session.state in deluge config folder under '%appdata%\deluge'.

[mhertz]

I've added another checkbox(well, radio-button to be exact) for libtorrent 1.2.3, so now 3 libtorrents to choose between, but the default is still latest libtorrent 1.2.x as before. I'll keep that libtorrent 1.2.3 extra checkbox untill problems resolved for the affected people.

My reasoning for above mentioned change, was that there's a couple other bugreports against libtorrent 1.2.4 in addition to the tracker issue i.e. getting dramatically fewer connections/speed, and no dht connections. I thought about changing libtorrent 1.2.x in installer to 1.2.3 because of these issues, but I then thought that as I cannot reproduce, and arvid neither, and other people also not experiencing this would probably prefer getting latest stable libtorrent instead of older previous version, then I instead decided to just temporarilly add that extra optional checkbox for affected people.

[stki]

I've found a mistake in stats. Values shown doesnt correspond to labels.

stats.JPG (12.9 KiB) Viewed 6936 times

[mhertz]

Thanks, yeah I believe that's the bug fixed in git-develop so if using my dev-installer then it should be fixed, and if using stable 2.0.3 then I previously posted a prepatched file with backported fix for manual replacement.

Anyway, I previously already have backported another bug-fix from git-develop into 2.0.3, including the other fixes, so might as well also backport this, so I just did that and updated my build-script to apply additional patch, and rebuilt/uploaded deluge 2.0.3.

@all, arvid would appreciate if people would test the patch he submitted for testing, and report back if affected with the tracker-issue, and which I also built and uploaded few posts above, though however two have reported it didn't work for them unfortunetly, though one uses VPN. I cannot give feedback to arvid, as not affected, and feel little silly reporting errors of others without anything to back it up i.e. no debug-logs, and not being able to answer questions about if using VPN, if only dht and udp trackers or also http, or testing new patch etc.

[mhertz]

Just wanted to add about the libtorrent 1.2.x tracker issue, that it's still unfixed, and the patch proposed, which I built and provided, probably isn't a fix, as confirmed by 2 persons, and here's latest info summerized:

Rwasef1830:

I'm seeing this issue as well with a self-compiled qBittorrent 4.2.1 with RC_1_2 branch, running on a SeedHost shared slot. qBittorrent doesn't produce any logs. No VPN in use. But the host server seems to be using Docker and also is running an OpenVPN server and has multiple IPv4 and IPv6 addresses configured.

Arvid:

is there any chance you could post the error messages you see when contacting the trackers?
I suspect the failure is related to the exotic network setup. I would like to understand more about it.

Rwasef1830:

Please check your mail for a message from me.

Arvid:

I've received logs from @rwasef1830 which strongly suggests the problem being that libtorrent fail to enumerate the routing table. It's empty.

I don't think I will land #4331 I think that was a red herring.

I intend a two-pronged approach:

add a special case when listening to a single specific IP, and just make that avoid all complicated routing table logic. This should fix the issue for most people, or make it possible to work-around by specifying the IP to listen on.

include more debugging in enum_if to diagnose exactly what the system calls return and try to understand how the current code enumerating the routing table is broken. This will support more future edge cases when you're actually multi-homed.

(#4331 mentioned by Arvid above, to properly being a red herring, is the patch previously submitted for testing)

[pwhodges]

I have just installed the test liborrent, with no immediate problem.

To summarise:
My network setup is: Deluge running straightforwardly through router firewall; no VPN. IPv6 as well as IPv4, though.
Problem libtorrent had all torrents in error for a time, but they then reduced somewhat erratically to near zero; older libtorrent - no problem; test libtorrent - no problem on restart, none seen yet.
So as well as the version of libtorrent, the problem really only arose after a complete rebuild of Deluge, replacing v1 - though I don't really see how that could affect it.

Hmm. There's not really anything helpful there, is there!

Paul

[mhertz]

New patch posted for testing by Arvid, for the libtorrent 1.2.4 issue, so I built RC_1_2 branch including this patch, so please test if affected, and report back either here or directly on libtorrent's github, thanks.

http://s000.tinyupload.com/index.php?fi ... 6072127227

There where some irrelevant for us commits added to RC_1_2 branch and a few not important ones also, but anyways I rebuilt libtorrent 1.2.x and installers to include it. Doesn't contain experimental patch above, as in seperate testing branch.

[Jerrk]

Does the columns also mess up for others, like i set it one way and then after restarting deluge it'll resize the columns and maybe reorganize some of them?

I also have this issue, I have all my columns set to my desired width and then when i restart the client their width gets all scrambled up.

I'm using deluge in Thin Client mode if that matters

It seems to consistently be at least these columns:
Size
ETA
Download Folder
Tracker
Label

Here is a comparison between having the widths correct and then immediately after a restart. i marked the changed width in red for more clarity





Are these settings stored in a .conf somewhere that can just edit perhaps?

Really annoying having to change the width after every start, so hopefully we can figure out a fix

[mhertz]

I couldn't reproduce on my end, after restarting many times in thinclient-mode. I did however sometimes after rebotting windows(VM), then it reset columns, but I believe is related to a bug with if you have localisation enabled in windows other than US, then sometimes it shows translated entries, and other times not, as when it didn't remember, it was when translation failed. One of the files I added to deluge main dir, cannot remember name now sorry, could be deleted to stop translations altogether though.

I believe the columns enabled and probably placement is saved in deluge profile folder under gtk3ui folder or something(VM not open right now) and in a file named torrentview.state, where you can see the names of enabled columns and then weird characters besides/before, so it's probably a binary file or otherwise special non-regular text-file. Possibly you could try to write-protect the file after it's set up propperly, though don't know if will help, as I suggested this to another user here, which had issues with connection-manager forgetting hosts, which I also couldn't reproduce, and the user stated it worked for some time(write-protecting file), but after some more time it failed again.

I don't know which file it is in, though should be simple to find out, but I would guess you could directly hardcode the fields also if wanted, in the python relevant source file, which is one of the nice things of dealing with apps in interpretted non-compiled languages like this imho.