FileBot

Posted: **17 Jun 2024, 03:07**

(zenity:488): GVFS-RemoteVolumeMonitor-WARNING **: 02:59:19.406: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
Gtk-Message: 02:59:19.608: GtkDialog mapped without a transient parent. This is discouraged.
1 file linked.
Failed to write xattr key: net.filebot.metadata: /mnt/media/downloads/new/Boardwalk Empire - S05E01 - Golden Days for Boys and Girls.mkv: Error writing extended attribute 'net.filebot.metadata': Operation not supported
Failed to write xattr key: net.filebot.filename: /mnt/media/downloads/new/Boardwalk Empire - S05E01 - Golden Days for Boys and Girls.mkv: Error writing extended attribute 'net.filebot.filename': Operation not supported

Filebot docker is being run as a user that has full permissions to the media mount. If I choose option rename or hardlink I get the same errors. The operation completes though, the file does actually get renamed/hardlinked, but these errors appear in the CLI console.

Posted: **17 Jun 2024, 05:40**

If the target file system does not support xattr then Failed to write xattr key warning messages are expected. Please read xattr metadata for details.

You may configure filebot to store xattr metadata to .xattr folders and plain/text files instead of native filesystem extended attributes:

rednoah wrote: ↑24 Oct 2012, 11:16 Configure FileBot to store xattr metadata in plain text files instead of filesystem xattr streams:
Shell: Select all
filebot -script fn:properties --def net.filebot.xattr.store=.xattr

Alternatively, you can also disable xattr metadata altogether, just to make the warning messages go away, but at that point you could also just ignore those warning messages.

FileBot

getting "Failed to write xattr key" errors from filebot docker (clean install)

getting "Failed to write xattr key" errors from filebot docker (clean install)

Re: getting "Failed to write xattr key" errors from filebot docker (clean install)