on your pi, run python -c "import libtorrent; print libtorrent.version". do you have another version of libtorrent currently installed? are you running the thin client or webUI setup in that article? deluge and libtorrent can also have compatibility issues between versions, are you running the same versions of deluge and libtorrent on both devices?

deluge-common 1.3.13+git2016113 all bittorrent client written in Python/PyGTK (common filesdeluge-console 1.3.13+git2016113 all bittorrent client written in Python/PyGTK (console ui)deluge-web 1.3.13+git2016113 all bittorrent client written in Python/PyGTK (web ui)deluged 1.3.13+git2016113 all bittorrent client written in Python/PyGTK (daemon)

, but your dpkg --list told me the libtorrent version anyway. i would check libtorrent version on the client machines to make sure it's the same one. i've run thin clients with mixed deluge versions like that, but not mixed libtorrent versions. note that iirc mixing deluge or libtorrent versions is not officially recommended. when you run deluged and get the above error, is deluged still running? you can check with htop or the ps command. How did your setup work before the crash? what kind of a crash do you mean? welcome to linux by the way. raspberry pi is fun.

So at this time it's installed fine right? Best is now to go on with the service creation and it's dedicated user https://dev.deluge-torrent.org/wiki/Use ... ce/systemd for automatic startup and isolation (and don't forget the auth modification of course, all in the wiki)

About your issue do you see the deluged process running (ps command or top)?The Deluge config is per user (/.config/deluge) so if you haven't configured anything yet try with without the sudo under your logged user.If the sudo is needed do "sudo bash" to logon as root and start the daemon/deluge-console.Starting Deluged with the log output will be helpfull too (described during the systemd service creation you can pickup the line there)

I just made a test with a new profile (.config/deluge renamed). Just typing "deluged" is enough to have it reachable by deluge-consoleTry to remove the profile of your user and just do these steps. the process is well present in top and ps commandif it crash at startup launch it with a log file (where you user have permission to write). Something like "deluged -l daemon.log -L debug"(adapt path)

I installed deluge on a brand new model 3 B+ model using your tips and it worked and runs flawlessly. Cloning the SD card, putting it in my old Pi model 1 (512 Mb) still doesn't work but I'm happy for now.