You are right, it is indeed some kind of permission issue but I don't know how to resolve it.
The files are on my secondary hard drive which are mounted to /data/.
If I copy my test file to the Desktop it works fine.

Hi, I've got the same issue and after some poking I believe it's due to the way snap handles permissions. snap puts filebot in a jail, this causes problems when you want to access network shares, or in my case files that are owned by another user but have read-write permissions for world.

It won't even let you access files that you own in /tmp, which is really odd. The only place I have found that works is under my home directory. None of my media is here

I suspect this is also why the filebot GUI does not work over X.

Someone asked above if there is a way to install just a debian package instead of using snap. Is this an option? I couldn't find one. I believe this would solve the issue.

I also tried installing filebot in snap "classic" mode which supposedly removes the jail. This doesn't make any difference.

EDIT: I looked a little farther, and also read the post on granting access to /media. My media is not under /media, it's under /share (I tried symbolic links from /media/share to /share - no joy).

If the developers want to continue using snap, please consider building a snap package that can be installed in "classic" mode. Apparently "classic" mode removes the sandbox/jail and allows the snap-deployed application to access the filesystem. Without classic, we're limited to using filebot only on files under our home directory, or under /media after running the "connect removable media" commands.

There is some discussion here explaining that tools that need access to the filesystem, like text editors, should be packaged in "classic" mode. filebot definitely falls into this category IMHO. [feel free to ignore the political discussions around the bad or good of snap]https://www.reddit.com/r/Ubuntu/comment ... ally_hurt/

Illegal Argument: java.nio.file.NoSuchFileException has been fixed, and should give you a better error message now. If the system doesn't allow file access, then the correct behaviour is a failure. That being said, if snap confinement is an issue, then you can just use the deb instead, which then runs with your permissions as usual.