1

I just wanted to download something using a Torrent file. I already had qBittorrent installed and dragged the file to it, then I chose the download directory and hit download. After that the program shut down and now I can’t start it anymore. I already uninstalled it and reinstalled it, but I still can’t run it.

Does anyone know how I can fix a bug like this? Where can I find the logs for qBittorrent?

If you open up qbittorent using the terminal it will show you what it’s doing in real time including the reason it’s crashing.

try that first

Gonna try that!

With which command do I open up qbittorrent using the terminal?

Open a terminal, type qbittorrent, press enter.

Ok, I found out that you just type the name of the program you want to run. That’s easy enough.

When I just type “qbittorrent” nothing happens, and I get a “~” as the only return.

I then tried sudo qbittorrent and qbittorrent opend up! But when i then closed it and tryed to open it via the menue on the bottom left it still didn`t work. The return i got when running “Sudo qbittorrent” was:

kf.statusnotifieritem: KDE platform plugin is loaded but SNI unavailable
^CCatching signal: SIGINT
Exiting cleanly

6

Try the Appimage. I just had a issue with a dependency for qBittorrent being updated, but qBittorrent from the various repos not being updated to work with it. It would start then shut down immediately. I went to their forums and installing the Appimage was their suggestion and I haven’t had an issue since.

7

That is a bad idea.
No GUI application should be run with root/sudo.

This would seem to indicate some other problem with your repo/package configuration though.

Because of course that not how dependencies should work for supported packages from the repos.

Maybe some foreign package - which is of course the users responsibility - and even then that would just mean rebuilding them.

I just checked again and qbittorrent works fine.

@Faloters

While you can work around dependency problems by using third party containerized applications .. you might want to investigate why official packaging would seemingly not work for you. For example - fully up to date (not partial)?

sudo pacman -Syu

8

I’m with @cscs no this. Dude again the dependency was updated but they didn’t update qBittorrent. Not uncommon. As fir qBittorrent working fine now only means they most likely finally updated it.

9

FYI the actual fix for the crash on launch on 5.2.0 is to go to ~/.config/qBittorrent and remove the lockfile in there. Apparently the new version doesn’t like having a lockfile from the old version present. Had nothing to do with deps for me.

ref: 5.1.4 lockfile presence causes 5.2.0 to abort with Another qBittorrent instance is already running. · Issue #24164 · qbittorrent/qBittorrent · GitHub

11

Actually what I posted is also correct so if your fix is real then there were two different problems.

12

Yeah, apologies, I did realise afterward that there were probably multiple things happening. The qbittorrent package on arch repos is stable now though so the appimage shouldn’t be needed anymore (at least it isn’t for me).