I’m being silly, I didn’t notice the weird path, while taking a glance at the error message I assumed it was pointing towards my user’s home folder.
Any ideas why it points to that path? I don’t remember it having this issue previously.
Also, tried creating the path, but it still quits in the same way, same error messages on the systemctl service.
That is news to me, which is quite strange considering that there were no updates to qBittorrent since last starting it.
Okay, restarted the service, made sure everything under /home/qbittorrent is owned by the said user, and the service appears as “Active” now.
But when starting qBittorrent (starting it graphically through the DE BTW), I still get the same error… qBittorrent quits after 1-2 min of loading, the window closes, and I get this to stdout in a terminal:
$ dmesg -l err,crit,alert,emerg
[ 0.017241] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.018766] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.020217] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.021667] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 4.660779] exynos-adc 12d10000.adc: IRQ index 1 not found
[ 4.782068] OF: graph: no port node found in /soc/hdmi@14530000
[ 4.785787] dwc3 12000000.dwc3: Failed to get clk 'ref': -2
[ 4.794161] dwc3 12400000.dwc3: Failed to get clk 'ref': -2
[ 7.269463] cgroup2: Unknown parameter 'memory_recursiveprot'
[ 8.551945] proc: Bad value for 'hidepid'
[ 8.946492] proc: Bad value for 'hidepid'
[ 10.265112] sd 0:0:0:0: [sda] No Caching mode page found
[ 10.265138] sd 0:0:0:0: [sda] Assuming drive cache: write through
Seems to be only stuff from the beginning of the boot process, and nothing that would seem relevant to qBittorrent
$ sudo journalctl -u qbittorrent
-- Journal begins at Sun 2023-01-15 23:00:49 EET, ends at Sun 2023-01-15 23:42:08 EET. --
Jan 15 23:00:55 Server systemd[1]: Started qBittorrent (DietPi).
I’m guessing it would be worth asking on their bug tracker directly, but given that this is quite an old version of qBittorrent, not quite sure if they would be willing to look into it much.
You could try to remove Qbit completely and try a new install. At least I’m not able to replicate the behaviour. On my 2 test systems, Qbit is working fine without issues.
From what I know, dietpi-software only installs qbittorrent-nox, right?
To me that’s not useful, since I need the full GUI as the web interface doesn’t really cut it.
Tried the nox version, doesn’t seem to load any of my torrents up.
EDIT: After some more digging, I managed to get it to run (albeit not in the best way) after clearing out the configuration file of qBittorrent. This of course wipes all settings and such, but at least it runs. Saving the settings and starting qBittorrent again causes it to close/crash again.
I’ve had similar problems with it on a different distro on my SBC with a newer version, so I’m guessing this is a very pesky bug in qBittorrent that won’t be sorted too soon. I created a bug report to them with that, but it didn’t go too far.
So I’m guessing to solve this issue, I would need to use a different torrent client, but transferring all the torrents from one client to the other would be a PITA.