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.008338
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 .. 10 11 12 13 14 15 16 17 18 19 20 .. 26 Next › Last »

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!

ptr commented on 2016-05-18 11:39 (UTC)

> which engine was crashing? used engine: TheTVDB/TheMovieDB (others not tested) > do you use any kind of proxy, ad blocker, web filter or similar? various ad/tracking/script/privacy filter in firefox but not what can blocked filebot..

max.bra commented on 2016-05-18 11:27 (UTC)

finally something good! > (but i don't now why.. (two config dirs? O_o)) pre 4.7 shell file starter leave .filebot on user home. now is in a more appropriate position. which engine was crashing? do you use any kind of proxy, ad blocker, web filter or similar?

ptr commented on 2016-05-18 10:51 (UTC)

$ mv -i ~/.filebot ~/.config/filebot same error message.. i have do following: # pacman -Rcs filebot $ rm -r .config/filebot $ yaourt filebot and a first test worked now.. :) (Version: 4.7) (but i don't now why.. (two config dirs? O_o)) Thanks for your help.. :) -- > is filebot open and except/crash during renaming or is not open at all? filebot except on "match". After move config dir it crashed completly.

max.bra commented on 2016-05-18 10:15 (UTC)

@ptr is filebot open and except/crash during renaming or is not open at all?

max.bra commented on 2016-05-18 10:11 (UTC)

can you move "old" config dir and files ~/.filebot to current ~/.config/filebot and try again?

ptr commented on 2016-05-18 09:07 (UTC)

sry.. same error message https://gist.github.com/anonymous/ba9e5b15b3a6914f8aeb133ef808f006

max.bra commented on 2016-05-18 08:53 (UTC)

> is not working.. ... is it still exception?