Can't run stadalone
Re: Can't run stadalone
port is resolved, but it's giving me a tracker error and not downloading. For context, same torrent is downloading fine on Qbittorrent. I closed Qbit, and tried Deluge, it does not work. under the tracker tab, it says tracker status: Error: unspecified system error. This can't be tracker problem as it works fine on qbittorrent. And deluge is not on the list of banned clients on this private tracker.
Re: Can't run stadalone
I found a github issue on this: https://github.com/SynoCommunity/spksrc/issues/5420 . Not very familiar with github, but it looks like it was resolved. Pretty sure it's the same issue with https trackers. Any ideas on how I can resolve this?
Re: Can't run stadalone
I don't currently have any idea personally, and just posting to say that the mentioned github issue is resolved as you suspected, so not related to that aspect atleast. Sorry. (I'll maybe Google your error at a later time, and post back if finding, or thinking, of something.)
Re: Can't run stadalone
Hi there!mhertz wrote: ↑Wed Dec 27, 2023 10:41 am Apologies, first read rest of thread now - little stupid post without answer, but just felt bad at looking like ignoringI'll find out tonight and edit in answer sorry guys.
Edit: Didn't either see page 2, on a roll- though above still applies apparently...
Edit2: Okay I tested on my ubuntu 22.04.3 VM, and got both deluge and qbittorrent running, by installing them from there PPAs and installing the static-built python3-libtorrent from pypi, through afterwards running: 'sudo pip3 install libtorrent==1.2.* -U'. This gives you libtorrent 1.2.19 for deluge and 2.0.9 for qbittorrent. If wanting 2.0.9 for deluge, then run afterwards(first need install 1.2.*, because semantics, unless using '--force'), 'sudo pip3 install libtorrent -U'. Btw, I had previous deluge and qbittorrent installed from last test-scenario I did for another user here, so started by uninstalling qbittorrent and deluge with apt, then running 'sudo apt autoremove' and then making sure all libtorrent-rasterbar's gone(as several) and not interferring with 'sudo apt purge libtorrent-rasterbar*' and 'sudo apt autoremove' for good meassure if anything found from previous command, and then I ran the first instructions I posted. Hope helps.
So, I came across this post today, because I'd been happily using Deluge in parallel with qBitTorrent quite happily unawares that they're not actually compatible with each other, until I was unable to launch Deluge this morning, on my Ubuntu 24.04 host.
I tried to run the pip3 command you recommend, although this then throws an error about it being an externally-managed-environment.
Should I go through the process of setting up the virtual environment as the error suggets? And, if yes, will Deluge be able to find that without adjusting anything else?
I'm sorry if this seems like a foolish question, but I'm pretty unfamiliar with this side of Python.
Edit to add:
Code: Select all
deluge --version
Code: Select all
deluge 2.1.2.dev0
libtorrent: 2.0.11.0
Python: 3.12.3
OS: Linux Ubuntu 24.04 noble
Code: Select all
[ERROR ][deluge.ui.gtk3.gtkui :1672] 'unknown name in settings_pack: ignore_resume_timestamps'
Re: Can't run stadalone
It's because you have a qbittorrent PPA enabled, offering a newer libtorrent than regular so taking precedence, but unfortunately incompatible with deluge(built different, in version 2.0.11 VS 2.0.10). You need remove that ppa, had this issue before with a user here: viewtopic.php?t=56354
Re: Can't run stadalone
Do I need to add the Deluge PPA as well?
I've removed the qbittorrent PPA, and reinstalled Deluge with apt.
I possibly just need to do a restart first though.
I've removed the qbittorrent PPA, and reinstalled Deluge with apt.
I possibly just need to do a restart first though.
Re: Can't run stadalone
No, don't need that. Just check you now have libtorrent 2.0.10 for deluge, and not 2.0.11.
The qbittorrent PPA pulled in libtorrent-rasterbar2.0 and deluge needs libtorrent-rasterbar2.0t64, which as said is v2.0.11 VS 2.0.10 respectively.
You could also remove qbittorrent and install again without it coming from its ppa, if all else fail I.e uninstall deluge and qbittorrent, plus all traces of libtorrent* and python3-libtorrent, just in case, then apt autoremove, then install deluge and qbittorrent, no PPA's for either of these, which would leave you with only one libtorrent I.e libtorrent-rasterbar2.0t64 in v2.0.10, built to work with both, when non-ppa installed.
Actually, the standard PPA's on ubuntu 24.04, will just yield you older versions of deluge/qBittorrent than without. Exception is slightly newer libtorrent for qbittorrent, as seen.
Sorry pretty confusing I know.
The qbittorrent PPA pulled in libtorrent-rasterbar2.0 and deluge needs libtorrent-rasterbar2.0t64, which as said is v2.0.11 VS 2.0.10 respectively.
You could also remove qbittorrent and install again without it coming from its ppa, if all else fail I.e uninstall deluge and qbittorrent, plus all traces of libtorrent* and python3-libtorrent, just in case, then apt autoremove, then install deluge and qbittorrent, no PPA's for either of these, which would leave you with only one libtorrent I.e libtorrent-rasterbar2.0t64 in v2.0.10, built to work with both, when non-ppa installed.
Actually, the standard PPA's on ubuntu 24.04, will just yield you older versions of deluge/qBittorrent than without. Exception is slightly newer libtorrent for qbittorrent, as seen.
Sorry pretty confusing I know.