Hi, I have really wierd problem with qbittorren appimage. Im on slackware current installed to drive from live mate iso. Whenever I run it by executing ./qbittorrent.appimage it works fine. But any other way, being it desktop launcher, shell script or just clicking on it, there is a weird bug that causes qbittorrent to close whenever I click on "add torrent file" button.

The wierdest thing is that the bug persists even if i put something like "xterm ./qbittorrent.appimage" in a shell script and then execute it, even tho a terminal window literalily appears and qbittorrent is visibly running from this terminal window. But executing "xterm ./qbittorrent.appimage" from other terminal works just fine. Is there some different way to work around it? It makes me wonder what is even the difference here?

*Im just looking for a way to trutly run it "as if" it was ran from a terminal without having to open a terminal and type everything in each time.

So, what's the problem? LL

Add: aside from finding: a trillion search results on the internet,,, oh wait that's babies multiplying?!.

Come-on space race!!!

Add, again: I know, my bad, everyone can pitch with b now...

Sorry if the way i phrased it is confusing, but this is so dumb I don't know how to say it better. The point is Im forced to first open terminal, login, type in cd /home/user/Desktop ; ./qbittirrent.appimage and then have terminal window hanging for qbittorrent to not break every time i click on "add torrent file". Every other way, including putting "xterm ./qbittorrent.appimage" in a shell script and running it ends with qbittorrent breaking every time i click on "add torrent file" button.

I would like to be able to open it through desktop launcher without it breaking every time i click on "add torrent file", even if additional terminal window has to hang around.

Have you tried oping it with -v

-v does nothing unfortunatelly, no additional messages, It doesn't even launch.
It only says this on launch when I launch it by opening terminal and typing the command in:


QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user'
QSystemTrayIcon::setVisible: No Icon set
(but it still works, so i guess this is not where the problem lies)


The most annoying is that when i run it through shell file containing "xterm ./qbittorrent.appimage" it does show some crash message in the terminal that opens. But the terminal window closes instantly along with qbittorrent upon clicking "add torrent file" and it is impossible to read the crash message.

After multiple trials I managed to get 2 screenshots of what was on xterm window of qbittorrent that was run by shell script cotainining "./qbittorrent.appimage" just before it closed after clicking "add new torrent file".

https://i.ibb.co/6v2XDzz/1.png
https://i.ibb.co/LCK8Rpd/2.png

It works if I run shell script containing "xterm ./qbittorrent.appimage" from a terminal window "wha..?"

I don't see this issue running the appimage on -current (KDE). Are you on -current or 14.2?
what desktop are you using? these GTK warnings are a bit strange, qbittorrent is a Qt application, perhaps something broken on your system tray makes qbittorrent misbehave?

Slackware current, mate 1.26 version installed from liveslak ISO. Everything is updated to the most recent in current. Yea, this might have something to do with my current DE.

I have a tr.sh and if I click on a torrent file in the browser it will start this script with the given url. And the script will do the rest (send the request to the torrent server).

You might have a good reason for using appimage, but if not, you might want to try out AlienBob's qbittorrent package (plus the depencency libtorrent-rasterbar) - I've never had any issues with that.

1 members found this post helpful.

This might be why...

From the latest release notes:
---
qBittorrent v4.4.0 was released.
LINUX: An AppImage is now offered. It uses the latest versions of Qt6, libtorrent, boost, openssl. It is created on Ubuntu 20.04 and it should work on any other similarly aged distro. It isn't well tested. Also Ubuntu 20.04 is dropped from the PPAs because it doesn't have the minimum required Qt5 version (5.15.2). The AppImage should cover any users left on that version.
---

Myself I use the docker version and the web gui.

Yeah, thanks I'll consider regular installation. Using appimages because it's convenient to have your set of software across every fresh installation without messing with each one of them.

One script to manage all the slackbuilds ? Or a repo configured with slackpkg+ ?
For each his way...

I always found appimage and all somehow bloated.

1 members found this post helpful.

appimage is not slackware way

build slackware packages and manage installation, upgrading, and removal with slackware's pkgtools.

Of course there's tools built on top of pkgtools to make it even easier, such as sbopkg:

1 members found this post helpful.

The "Slackware Way" is to be the admin of your own box. If that consists of using appimage, docker, pip, or Slackware packages, so be it. I prefer Slackware packages in a lot of cases, but sometimes the ease of prebuilt images can't be beat. I'm running steam through conty, because I don't want to install multilib for just steam.

4 members found this post helpful.