I ran Deluge with logging set to debug and I noticed the Deluge-bin thing appears to be some kind of bug in the parsing of arguments... This: ${EXEC} "${PYTHON}" "${bundle_macos}/${name}-bin" --config="${XDG_CONFIG_HOME}" --logfile="${HOME}/Library/Logs/org.deluge-...

My changes are in a fork of the deluge repository, not the macports repository; I actually had to change quite a few things, including making a bash script to make the app that more or less works (not 100% though¡, I think). Essentially, I used macports to get the dependencies (some of which I also ...

I wonder what is up with that deluge-bin torrent thing. Maybe it's a side-effect from my trying to be clever and migrate deluge 1.3 settings?

@Hector, not really sure about that; and I haven't seen that behavior at least. Doesn't the log give any relevant information?

I have now submitted a PR with several macOS fixes (including shortcuts not being properly mapped) and a new script that should easily make a .app bundle out of a macports install (because Homebrew is the plague, seriously) For now, you can give my .app a spin here: https://www.dropbox.com/s/zy0y4u...

I have now submitted a PR with several macOS fixes (including shortcuts not being properly mapped) and a new script that should easily make a .app bundle out of a macports install (because Homebrew is the plague, seriously) For now, you can give my .app a spin here: https://www.dropbox.com/s/zy0y4u4...