Re: Deluge Windows Builds
Posted: Thu May 19, 2022 5:12 pm
I cannot guarenti that it's yarss2 related, but just highly suspect so. There's several posts/threads around the net about this, and several having comtacted me with such deluge crashes, and so after reading up on it and asking affected if they had yarss2, then they did and e.g. one without any yarss2 errors in logs could consistently reproduce running fine for days without yarss2 and enabling yarss2 would crash deluge within max 24 hours, ussually much less than that. I've never could reproduce myself though, as stated.
A yarss2 bugtracker ticket and google-search-link:
https://bitbucket.org/bendikro/deluge-y ... luge-often
https://www.google.dk/search?q=deluge%20yarss2%20crash
The error you posted from GTK actually sounds related(some gtk errors aren't), with one thread explaining crashing in his python(2) and gtk3 app with said error, and some tips for code-fixes, but sorry it's way over my head to try fix unfortunetly and would need actually talented people in this, for looking into.
The yarss2 you used gotten from forum, I suspect is mine, and was just posted because a user had ssl verification errors and since I couldn't fix that, or even knew why happened(dll's was in place), then I suggested all I could do was to disable ssl verification if wanted, and so I made upon request, if remember right at least. Not the best workaround in the world obviously, and also what that warning you mentioned was about, but better than nothing I thought, well if accepting the security risk of-course.
Anyway, I just tested in a win10 VM that the two x64 builds of doadin does include the needed dll's, and testing with adding a yarss2 feed with a https url of 'https://expired.badssl.com' obviously didn't return any downloads, but did state that ssl verification failed as had expired certificate, showing me that the ssl dll's is found and compatible, so I don't understand why you get such message meaning they are not found or not compatible. I didn't test the x32 builds though.
I didn't wanted to answer for doadin before, and as you say hopefully he will give his input if needed, but he expressed here before that he's not interessted in making a confusing situation of which is official and which isn't(for when official release comes) - better explained than by me here
I honestly can't remember now and to lazy to go back and check now, but I don't think the names are wrong. It's deluge with lt1.2.x and with lt2.x, and a dev-build-number in the extracted installer-names - sorry if i'm wrong here. Nowhere is listed deluge-2.0.5 I atleast am pretty certain about(lt2.0.5 is libtorrent 2.0.5).
Last, good thinking on the minimize theory/test you explained, could be - infact now you say that, then I seem remember another user tried that too, but failed after some hours sadly he reported to me, but you could be lucky of-course.
Good luck mate, sorry cannot really help you any better.
A yarss2 bugtracker ticket and google-search-link:
https://bitbucket.org/bendikro/deluge-y ... luge-often
https://www.google.dk/search?q=deluge%20yarss2%20crash
The error you posted from GTK actually sounds related(some gtk errors aren't), with one thread explaining crashing in his python(2) and gtk3 app with said error, and some tips for code-fixes, but sorry it's way over my head to try fix unfortunetly and would need actually talented people in this, for looking into.
The yarss2 you used gotten from forum, I suspect is mine, and was just posted because a user had ssl verification errors and since I couldn't fix that, or even knew why happened(dll's was in place), then I suggested all I could do was to disable ssl verification if wanted, and so I made upon request, if remember right at least. Not the best workaround in the world obviously, and also what that warning you mentioned was about, but better than nothing I thought, well if accepting the security risk of-course.
Anyway, I just tested in a win10 VM that the two x64 builds of doadin does include the needed dll's, and testing with adding a yarss2 feed with a https url of 'https://expired.badssl.com' obviously didn't return any downloads, but did state that ssl verification failed as had expired certificate, showing me that the ssl dll's is found and compatible, so I don't understand why you get such message meaning they are not found or not compatible. I didn't test the x32 builds though.
I didn't wanted to answer for doadin before, and as you say hopefully he will give his input if needed, but he expressed here before that he's not interessted in making a confusing situation of which is official and which isn't(for when official release comes) - better explained than by me here
I honestly can't remember now and to lazy to go back and check now, but I don't think the names are wrong. It's deluge with lt1.2.x and with lt2.x, and a dev-build-number in the extracted installer-names - sorry if i'm wrong here. Nowhere is listed deluge-2.0.5 I atleast am pretty certain about(lt2.0.5 is libtorrent 2.0.5).
Last, good thinking on the minimize theory/test you explained, could be - infact now you say that, then I seem remember another user tried that too, but failed after some hours sadly he reported to me, but you could be lucky of-course.
Good luck mate, sorry cannot really help you any better.