Grant access to removable-media

[pitz]

Probably missing something trivial, but I've been at it for a while and can't resolve.

I want to process a folder with many files (some inside subfolders) using the amc script, but writing the folder name as input does nothing: "No files selected for processing". Writing as input a specific file inside that folder works as expected.

Code: Select all

pitz@pitz-and-pitz:/media/pitz$ filebot -script fn:amc --output "/media/pitz/HDD" --action test -non-strict "/media/pitz/HDD/Series/0-unsorted" --log-file amc.log
Locking /home/pitz/snap/filebot/9/data/logs/amc.log
Run script [fn:amc] at [Wed Jun 21 17:55:55 IDT 2017]
Argument[0]: /media/pitz/HDD/Series/0-unsorted
No files selected for processing
Done ヾ(＠⌒ー⌒＠)ノ

Thanks in advance!

Mandatory sysinfo:

Code: Select all

FileBot 4.7.9 (r4986)
JNA Native: 5.1.0
MediaInfo: 0.7.82
7-Zip-JBinding: 9.20
Chromaprint: 1.2.0
Extended Attributes: OK
Unicode Filesystem: OK
GVFS: PlatformGVFS [/run/user/1000/gvfs]
Script Bundle: 2017-05-15 (r500)
Groovy: 2.4.10
JRE: OpenJDK Runtime Environment 1.8.0_121
JVM: 64-bit OpenJDK 64-Bit Server VM
CPU/MEM: 4 Core / 1 GB Max Memory / 27 MB Used Memory
OS: Linux (amd64)
Package: SNAP
uname: Linux pitz-and-pitz 4.10.0-24-generic #28-Ubuntu SMP Wed Jun 14 08:14:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Done ヾ(＠⌒ー⌒＠)ノ

[rednoah]

Since you're using a snap package, you need to be aware of snap sandboxing, which limits sandboxed apps to well-known file locations. You can use --devmode when installing the snap to disable this kind of security feature.


EDIT:

You probably need to give the filebot snap access to your removable-media folder:

Code: Select all

sudo snap connect filebot:removable-media

@see https://github.com/snapcore/snapd/wiki/ ... onnections