FileBot

Salix Linux is based on Slackware.

Can't get Filebot to work correctly in Salix Linux. Not even the Flatpak. Snap isn't available to me as Salix/Slackware doesn't use systemd. The Slackpkg doesn't work correctly.

Filebot loads, but as soon as I try to select a file I get a spinning logo and Filebot locks up totally. The only recourse is to kill it. I've tried from the command line and I'm informed some fx file is missing. I suspected this may be a Java issue, so I loaded up every Java jdk file I could find in the repos but no effect whatsoever.

If I can't sort this out then I'll have to move on to another distribution.

I must be confused as I thought flatpaks were universal and worked on any Linux distribution. I've also reported my issue to Flathub/Flatpak whatever they call themselves.

I'm stuck.

tippunmon1953 wrote: ↑17 Jan 2026, 14:38 Salix Linux is based on Slackware.

Which Desktop are you using? Gnome? KDE? Something else? How did you install the FileBot package?

tippunmon1953 wrote: ↑17 Jan 2026, 14:38 as soon as I try to select a file I get a spinning logo and Filebot locks up totally.

So when you click on the Load button, the FileDialog doesn't show? You could run filebot from console to see error messages. You can send kill -3 to the java process to dump all stack traces. That way you can see exactly where things are stuck. You can configure different FileDialog implementations via the Advanced Settings › User Interface Options. Zenity works best if you have the zenity package installed.

If it is indeed a FileDialog issue, then you could try to bypass the issue by using drag-n-drop to load files instead of the FileDialog

tippunmon1953 wrote: ↑17 Jan 2026, 14:38 I must be confused as I thought flatpaks were universal and worked on any Linux distribution.

Communication between Desktop components is complicated and error-prone. A flatpak bundles all libraries and POSIX runtime libraries as to avoid dependency issues. That makes sure that the FileBot process runs at all, but the various Desktop components at play not interacting correctly at runtime is something that AFAIK flatpak doesn't solve / maybe makes worse.