rednoah wrote: ↑14 Jan 2023, 17:41 I see. If you're running FileBot inside a docker container, then "Move to Trash" can't possibly work in the context of the unRAID host platform.

I just wanted to precise that the same behaviour (Move to trash not working) is also seen on a standard/normal Ubuntu 20.04 installation.

FYI, it's also better for Alpine Linux, where JavaFX is not supported yet (no package available).

Thanks for the hint, Zenity is working perfectly! Not having JavaFX as a dependency is a great thing

When using the AWT file chooser (-Dnet.filebot.UserFiles.fileChooser=AWT), a folder can't be selected.

If after clicking "Load"->"Select Folder" a folder is selected from the window, clicking the "Open" button only open that folder. There is no way to tell to open the folder in FileBot.

Issue seen ...

Ok, thanks for clarifications !

I get similar problem with r9102:


Initialize Cache folder: /config/cache
Initialize Logs folder: /config/logs
Initialize TemporaryFiles folder: /config/tmp
Initialize new disk cache: /config/cache/0
FileBot 4.9.5 (r9102) JDK8
JNA Native: 6.1.0
MediaInfo: 21.03
Tools: fpcalc/1.4.3 7z/16.02 unrar/6 ...

:?: You have an extremely powerful x86_64 machine. Why are you stuck with JDK 8 anyway? :lol:
(because the JDK 8 package will be phased out eventually, and really only exists for old hardware for which there aren't any Java 11 builds)


I use FileBot running in a Docker container I'm ...

Thanks! Will this build become and official release or it will ne kept as a beta version ? Also, is there a JDK8 variant for beta versions ?

Matching a file against TheMovieDB in episode mode produce the following exception. Note that this exception is produced in loop.


Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at java.util.Objects.requireNonNull(Objects.java:203)
at java.lang.String.join(String.java:2522 ...

Thanks for the tips. I compared the options passed in the latest filebot.sh and saw that the name and value of the archive extractor option changed.

I guess this post should be updated to reflect the latest changes: viewtopic.php?t=6311

Yes I'm building my own docker image, using the tar package. The filebot.sh used can be seen there: https://github.com/jlesage/docker-filebot/blob/master/rootfs/opt/filebot/filebot

Here is the output of filebot -script fn:sysenv :

# Environment Variables #
PATH: /usr/local/sbin:/usr/local/bin ...

The support for 7zip executable in r6221 seems to be broken.

In r6118 it was working fine:

# /opt/filebot/filebot -script fn:sysinfo
FileBot 4.8.5 (r6118)
JNA Native: 5.2.2
MediaInfo: 18.08.1
p7zip: Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,12 CPUs Intel(R) Xeon(R) CPU E5 ...

Thanks, I have integrated the jar manually in the image.

Nice. Will be part of the next release then. But the next release is probably still 2-3 months off since there's no general pressing issue with the current release.


Would you consider an earlier release considering that the deadlock is easy to hit when using a Docker image? Else I can integrate ...

rednoah wrote: ↑28 Aug 2018, 12:54 FileBot r5846 may fix the issue. Please run a few test and see if it resolves the problem.

CHANGES.tar.xz contains the latest jar:
https://get.filebot.net/filebot/HEAD/

Looks good. I cannot reproduce the issue with the steps I provided in this post.

rednoah wrote: ↑27 Aug 2018, 17:38 There does seem to be a threading / concurrency / deadlock issue. It's very strange that it doesn't seem to be an issue on other platforms, but I might be able to fix this in the FileBot code base,

That's good news

Did installing full GTK / Gnome do anything? That should at least give you the system theme when running FileBot.


Not sure how the theme selection/detection is done, but it seems to be already using gtk theme (at least the one coming from Alpine Linux). I did try the Nimbus look and feel ...

Here is the output of "jstack" : https://pastebin.com/raw/SqLxcvzj
Hope this is what you were looking for.

I tried to play with Swing graphics options, but nothing helped.

Great thanks for confirming this!

What is the best way to be notified of new FileBot versions and/or builds? I saw the topic at viewtopic.php?f=7&t=1609, but it doesn't seem to track every builds (for example, 4.8.2 had multiple builds).

When starting FileBot, the license key is printed to its output. I think it would be preferable to just show "LICENSED" or something like this. The reason is that when people have issues, they often copy-paste the output and post it in a forum.
So I guess that publishing a license key to the public ...

I seem to have a way to easily reproduce this issue with the Docker image (https://hub.docker.com/r/jlesage/filebot):

- Try to rename multiple files that have no match (with the TheTVDB for example).
- You then get a window telling that some files failed to be identified.
- Instead of selecting ...