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

There's unfixed crashing issues reported for several users of yarss2 with deluge, however your error in log resembles another error gotten with libtorrent 1.2.9 specifically, which hence look like you use(plus is the one on Debian bullseye if not mistaken), so try upgrade if possible to 1.2.10 or ne...

If wanted for testing then I rebuilt the execute plugin to emit it's 'debug' logging lines as instead 'info' level, so catched in default delugevpn log - you just drop it into '<deluge-profile-dir'>/plugins' and restart deluge, as I made it take precedense over default included version(don't have to...

I tested that atleast it does work in deluge 2.0.5 -also tested it too worked from your delugevpn docker specifically, so not a general issue encountered atleast. Normally the log should show error happened and exit-code, defined from plugin to show in 'warning' log-level I see, and the default exam...