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 yars...

You need deluge 2.x on your PC too.

If on windows then check stickied topics for community provided installers - I'd recommend doadin's dev builds.

Just quickly about my posted deluge build(not to derail this thread), then rename the 'py-3.9' part away from plugin filename and will load. This shouldn't be necesarry anymore, but for some reason still is with this specific plugin(my build is py3.10 based if remember correct, and do know it worked...

Thanks for confirming and reporting

@all, I applied the fix for Jerrk's uncovered/reported issue(autolabeling bug of label-based download-location), to previously posted latest bdutro fork with the 2 pending PRs by Serene-Arc and sammys applied(for inverse-regex autolabeling support, and fixing an autolabeling bug with the magnet hand...

I'm guessing this isn't intentional. Autolabels does work for changing download location if e.g. defined for matching files in torrent etc, and so is only label-based rules that can fail. It does however work when defining move completed after finished. The reason for former is an additional Torrent...

This should fix it: Notifications-0.5.egg . Drop into your deluge-profile's 'plugins' subdir, and it will take precedence over the included version. For context, smtplib.SMTP.sendmail() expects ascii char string or bytes for message input, and encodes former to bytes through ascii codec, hence error...

Thanks for the kind words mate, appreciated, and sorry for the 'deluged --version' command, which I thought listed libtorrent version too, but was wrong, but you knew how to test regardless yourself I see.

Take care

Im sorry, I should have asked(Debian after all is "the universal operating system"), but anyway yes that's the reason it wouldn't install I believe(it's only available for arm in aarch64). When I tested that lbry-libtorrent in an Ubuntu VM a little time ago, then it was run automatically i...

Hmm, that's strange... I checked bulls-eye using py3,9, and pypi have libtorrent 1.2.15 for py3.10 downwards to py3.7, so don't understand why fails. I just checked in an ubuntu VM, to see if needed quotes(because of the asterisk/glob), but worked fine without - you can try stipulate 'libtorrent==1....