Package Details: filebot 5.1.3-3

Git Clone URL: https://aur.archlinux.org/filebot.git (read-only, click to copy)
Package Base: filebot
Description: The ultimate TV and Movie Renamer
Upstream URL: https://www.filebot.net/
Keywords: mass media rename subtitle
Licenses: Commercial
Conflicts: filebot-git, filebot47
Provides: filebot
Submitter: ndowens
Maintainer: rvasilev
Last Packager: rvasilev
Votes: 138
Popularity: 0.43
First Submitted: 2009-06-21 07:41 (UTC)
Last Updated: 2024-03-30 19:38 (UTC)

Dependencies (6)

Required by (0)

Sources (3)

Pinned Comments

mithrial commented on 2022-03-03 21:16 (UTC)

This package now verifies the downloaded package against rednoahs PGP key:

gpg --recv-keys B0976E51E5C047AD0FD051294E402EBF7C3C6A71

(The key from https://get.filebot.net/filebot/KEYS )

rvasilev commented on 2018-11-11 11:46 (UTC) (edited on 2022-03-03 22:07 (UTC) by rvasilev)

Looking for a co-maintainer.

Please report bugs & fixes https://github.com/arch-noob/filebot

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 25 Next › Last »

max.bra commented on 2016-07-14 07:43 (UTC)

hi j1simon, still home renovation here, sorry. i will definitively fix home preferences & co position ASAP. give me a couple of day. > What is the reason to change desktop file, script init (filebot.sh)? reason is simple. i have inherited this package and i'm trying to keep aligned the old method with the news. and more, using portable version (imho, far better and arch standards compatible than deb/rpm version) original script default APP_DATA to pwd, clearly not compatible with file position of this package. hence the changes to startup sh script. however, i do not think FileBot on arch is working so bad...

j1simon commented on 2016-07-13 22:51 (UTC)

What is the reason to change desktop file, script init (filebot.sh)? The sh script defined here it opens wrong initial folder: https://www.filebot.net/forums/viewtopic.php?f=6&t=3949

max.bra commented on 2016-07-13 21:34 (UTC)

mmmh, netrunner use kde, am i right? can you try a drag and drop with a different plasma theme? better with a default one?

EGraf commented on 2016-07-13 14:03 (UTC) (edited on 2016-07-13 14:05 (UTC) by EGraf)

Hi max.bra, thanks for answering. With locale-gen I get: Generating locales... en_US.UTF-8... done es_ES.UTF-8... done Generation complete. I also tried changing en_US with es_ES in /usr/bin/filebot with no avail. $ filebot -script fn:sysinfo FileBot 4.7 (r3923) JNA Native: 4.0.1 MediaInfo: MediaInfoLib - v0.7.86 Apache Commons VFS: [zip, ftps, rar, ftp, tar, tgz, tbz2, sftp] Chromaprint: fpcalc version 1.3.1 (fpcalc) Extended Attributes: OK Groovy Engine: 2.4.6 JRE: Java(TM) SE Runtime Environment 1.8.0_92 JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM CPU/MEM: 8 Core / 3 GB Max Memory / 26 MB Used Memory OS: Linux (amd64) Package: PORTABLE Data: /home/ernesto/.config/filebot uname: Linux ernesto-pc 4.4.13-1-MANJARO #1 SMP PREEMPT Wed Jun 8 09:21:59 UTC 2016 x86_64 GNU/Linux Done ヾ(@⌒ー⌒@)ノ

max.bra commented on 2016-07-12 19:04 (UTC)

Hi EGraf, sorry for late reply. what about your netrunner locale and which locales are generated? remember, you NEED 'en_US.UTF-8' locate to be generated. this package and official launcher script use that locale by default.

EGraf commented on 2016-07-11 20:41 (UTC)

having problems with the drag-n-drop, if the file name has a square bracket it throws out a "java.net.URISyntaxException: Illegal character in path" error. This doesn't occur on Windows or if I use the "load" button to open the dialog box, only dragging the files on my Netrunner installation. any ideas?

amwalters commented on 2016-05-27 05:18 (UTC) (edited on 2016-05-27 05:50 (UTC) by amwalters)

Hey Teyro, I was getting the same error... I had to switch over to Oracle JRE 8. Looks like the most recent openJDK must be borked somehow.

max.bra commented on 2016-05-22 06:34 (UTC)

You have serious problems with your arm distribution Java VM http://bfy.tw/5t5e

Teyro commented on 2016-05-22 06:21 (UTC)

Huhu, whats wrong? :S [teyro@teyropi3 ~]$ filebot # # A fatal error has been detected by the Java Runtime Environment: # # Internal Error (os_linux_zero.cpp:254), pid=809, tid=0x7674f470 # fatal error: caught unhandled signal 11 # # JRE version: (8.0_92-b14) (build ) # Java VM: OpenJDK Zero VM (25.92-b14 interpreted mode linux-arm ) # Core dump written. Default location: /home/teyro/core or core.809 # # An error report file with more information is saved as: # /home/teyro/hs_err_pid809.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # /usr/bin/filebot: line 14: 809 Aborted (core dumped) java -Dunixfs=false -DuseGVFS=false -DuseExtendedFileAttributes=true -DuseCreationDate=false -Dfile.encoding="UTF-8" -Dsun.jnu.encoding="UTF-8" -Djava.net.useSystemProxies=false -Djna.nosys=true -Dapplication.deployment=portable -Dnet.filebot.Archive.extractor="$EXTRACTOR" -Dnet.filebot.AcoustID.fpcalc="fpcalc" -Dapplication.dir=$HOME/.config/filebot -Djava.io.tmpdir=/tmp/filebot -Duser.home=$HOME/.config/filebot -Dapplication.update=skip -Djna.library.path=/usr/share/java $JAVA_OPTS -jar /usr/share/java/filebot/filebot.jar "$@" [teyro@teyropi3 ~]$

max.bra commented on 2016-05-18 12:01 (UTC)

I do not understand what can be if not a problem of engine response or engine cache... doh anyway, glad you can use filebot again ;-) see you!