FileBot

I have Filebot installed on Kubuntu 26.04. I was using it to rename/relocate TV shows and movies for Jellyfin. The logfile shows successful renaming of TV shows and Movies since May 25th including creating folders. Suddenly it stopped working after June 16th. I've tried numerous times to rename files but I keep getting this error. I've checked file and folder permissions. It's as if Ubuntu changed the permissions for Filebot.

The media files are currently stored in the Unfiled Videos folder as a catchup prior to being organized. This folder is located on a different HDD than the OS if that makes any difference.
If I try to navigate to that path, the "media" folder does not exist for the user:
Even removing the "sticky bit" for the Unfiled Videos folder did not make a difference. I get the same error.

I'm somewhat of a newb with linux. I've used Ubuntu off and on for years but I typically find instructions and guidance online. Please make suggestions as if I were 5.

How did you install FileBot? (NOTE: depending on how you install an application, it may or may not running in a sandboxed environment with limited file system access)


How are you running FileBot? Are you running FileBot for a long long time? How did you configure the output folder? It sounds a bit like the underlying file paths have changed while FileBot was running.


Does this file path make sense? It says /run/media/user but you also write ls /run/media/ross so there does seem to be confusion about what the correct file paths would be in the first place?
What is the input file path of the file at hand? What is the expected output file path for the file at hand? (NOTE: if you're working with external drives or network shares on Linux, you'll want to be aware of how they're auto-mounted into the file system)


AFAIK, if you attach an external drive or connect a network drive, then that will be auto-mounted somewhere. Where? Does /run/media/ross being empty mean that your external drive is currently not mounted / not attached? (NOTE: permission errors often indicate the fundamental impossibility of a requested file system operation, not necessarily something that is fundamentally possible and merely disallowed by permissions)


Note that FileBot only works with file paths and is generally not aware of internal drives / external drives / network drives / etc since the OS file system abstraction layer takes care of making everything look the same standard file system to applications. So the first step is to always check if the file paths you seen in the FileBot error messages (i.e. file paths that FileBot is working with) make sense in your current environment.

Thank you. A friend who works with linux came over. There was apparently a path that somehow broke or got deleted. That was the issue.
I missed changing the username to "user". Sorry for that confusion.

You can mark this as solved.