Is X11 required when just using the command line?

Running FileBot from the console, Groovy / FileBot scripting, shell scripts, etc
Post Reply
MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Is X11 required when just using the command line?

Post by MACscr » 03 Feb 2013, 06:09

Is X11 required when using Filebot through the CLI? Im currently trying it from an ssh session and i get the following warnings:

Code: Select all

[email protected]:~/autoprocesstv/delugeScripts$ filebot -script fn:utorrent-postprocess -non-strict --def ut_kind=multi --def 'ut_dir=/media/Storage/torrents/incomplete/Family.Guy.S11E11.HDTV.XviD-ph2
> '
Feb 02, 2013 11:45:32 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Parameter: ut_kind = multi
Parameter: ut_dir = /media/Storage/torrents/incomplete/Family.Guy.S11E11.HDTV.XviD-ph2
Read archive [Family.Guy.S11E11.HDTV.XviD-ph2.part01.rar] to [/media/Storage/torrents/incomplete/Family.Guy.S11E11.HDTV.XviD-ph2/Family.Guy.S11E11.HDTV.XviD-ph2.part01]
Extracting files [/media/Storage/torrents/incomplete/Family.Guy.S11E11.HDTV.XviD-ph2/Family.Guy.S11E11.HDTV.XviD-ph2.part01/Family.Guy.S11E11.HDTV.XviD-ph2.avi]
Input: /media/Storage/torrents/incomplete/Family.Guy.S11E11.HDTV.XviD-ph2/Family.Guy.S11E11.HDTV.XviD-ph2.part01/Family.Guy.S11E11.HDTV.XviD-ph2.avi

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Group: [tvs:Family Guy] => [Family.Guy.S11E11.HDTV.XviD-ph2.avi]
Rename episodes using [TheTVDB]
Auto-detected query: [Family Guy]

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Fetching episode data for [Family Guy]

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Fetching episode data for [Family Guns]

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
[MOVE] Rename [/media/Storage/torrents/incomplete/Family.Guy.S11E11.HDTV.XviD-ph2/Family.Guy.S11E11.HDTV.XviD-ph2.part01/Family.Guy.S11E11.HDTV.XviD-ph2.avi] to [TV Shows/Family Guy/Season 11/Family Guy - S11E11 - The Giggity Wife.avi]

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Processed 1 files

** (process:22546): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Done ヾ(@⌒ー⌒@)ノ
[email protected]:~/autoprocesstv/delugeScripts$ filebot -version
FileBot 3.3 (r1412) / OpenJDK Runtime Environment 1.7.0_09 (headless)
It also results in no output. Am i missing something? This is on my Ubuntu 12.04 LTS system.

User avatar
rednoah
The Source
Posts: 16803
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Is X11 required when just using the command line?

Post by rednoah » 03 Feb 2013, 06:28

Well, it did do it's job and the output is between the many lines of dbus warnings:

Code: Select all

[MOVE] Rename [/media/Storage/torrents/incomplete/Family.Guy.S11E11.HDTV.XviD-ph2/Family.Guy.S11E11.HDTV.XviD-ph2.part01/Family.Guy.S11E11.HDTV.XviD-ph2.avi] to [TV Shows/Family Guy/Season 11/Family Guy - S11E11 - The Giggity Wife.avi]
I have no idea why OpenJDK would try to launch dbus though.

You could try forcing Java headless mode in the startup script:

Code: Select all

-Djava.awt.headless=true
:idea: Please read the FAQ and How to Request Help.

MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Re: Is X11 required when just using the command line?

Post by MACscr » 03 Feb 2013, 08:46

Apologies for my ignorance, but which startup file?

User avatar
rednoah
The Source
Posts: 16803
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Is X11 required when just using the command line?

Post by rednoah » 03 Feb 2013, 08:53

The executable file called 'filebot' containting the command to start filebot containing:

Code: Select all

#!/bin/bash
java -Xmx256m -Dunixfs=false -DuseGVFS=true -DuseExtendedFileAttributes=true -Djava.net.useSystemProxies=true -Dsun.net.client.defaultConnectTimeout=10000 -Dsun.net.client.defaultReadTimeout=60000 -Dapplication.deployment=deb -Dapplication.dir=$HOME/.filebot -Djava.io.tmpdir=$HOME/.filebot/temp -Djna.library.path=/usr/share/filebot -Djava.library.path=/usr/share/filebot -jar /usr/share/filebot/FileBot.jar "[email protected]"
:idea: Please read the FAQ and How to Request Help.

MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Re: Is X11 required when just using the command line?

Post by MACscr » 04 Feb 2013, 07:15

didnt seem to make a difference. =(

User avatar
rednoah
The Source
Posts: 16803
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Is X11 required when just using the command line?

Post by rednoah » 04 Feb 2013, 07:37

:idea: Please read the FAQ and How to Request Help.

MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Re: Is X11 required when just using the command line?

Post by MACscr » 04 Feb 2013, 07:43

I dont see an r1444 in that list. Am I blind?

Also, you were right that it it was working despide those warnings, but now when I have my fully completed command, it doesnt appear to finish. It says it does, but I cant find that anything has been done. Is there a debug option?

Code: Select all

[email protected]:/media/Storage/torrents/complete$ filebot -script fn:utorrent-postprocess -non-strict --def ut_kind=multi --def 'ut_dir=/media/Storage/torrents/completed/Django.Unchained.2012.DVDSCR.XVID.NYDIC' --output /media/Storage/Videos --action move --conflict override --def subtitles=true --def plex=localhost --def 'movieFormat=Movies/{n} ({y})/{n} ({y})'

** (process:28731): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:28731): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:28731): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n

** (process:28731): WARNING **: Command line `dbus-launch --autolaunch=5c686fcd4b7fc19b5fd84dfc00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Parameter: ut_kind = multi
Parameter: ut_dir = /media/Storage/torrents/completed/Django.Unchained.2012.DVDSCR.XVID.NYDIC
Parameter: subtitles = true
Parameter: plex = localhost
Parameter: movieFormat = Movies/{n} ({y})/{n} ({y})
Done ヾ(@⌒ー⌒@)ノ

User avatar
rednoah
The Source
Posts: 16803
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Is X11 required when just using the command line?

Post by rednoah » 04 Feb 2013, 08:04

Sry, upload crashed. It's up now.

The utorrent-script has plenty of debug logging. But it looks like that folder might be empty, or at least there's no video files. So it's not doing anything.
:idea: Please read the FAQ and How to Request Help.

MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Re: Is X11 required when just using the command line?

Post by MACscr » 04 Feb 2013, 08:07

hmm, doesnt the utorrent script do extracting though? The folder is full of rar files and an nfo

MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Re: Is X11 required when just using the command line?

Post by MACscr » 04 Feb 2013, 08:31

Nvm, i had a typo. So while things do work, the new jar doesnt seem to make a difference with the X11 warnings. I replaced my /usr/share/filebot/FileBot.jar file with the new one. I left the change you mentioned in my /usr/bin/filebot startup file as well.

User avatar
rednoah
The Source
Posts: 16803
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Is X11 required when just using the command line?

Post by rednoah » 04 Feb 2013, 08:48

I'm still not convinced that there's any files in that folder you pass in. :P

Works for me:

Code: Select all

E:\testdata>filebot -script fn:utorrent-postprocess utorrent-postprocess-test/archive --action test --output E:/output -non-strict

Code: Select all

Argument: E:\testdata\utorrent-postprocess-test\archive
Read archive [Avatar.7z] to [E:\testdata\utorrent-postprocess-test\archive\Avatar]
Extracting files [E:\testdata\utorrent-postprocess-test\archive\Avatar\Avatar.mp4]
Input: E:\testdata\utorrent-postprocess-test\archive\Avatar\Avatar.mp4
Avatar.mp4 [series: null, movie: Avatar (2009)]
Group: [tvs:null, mov:Avatar (2009), anime:null] => [Avatar.mp4]
Rename movies using [TheMovieDB]
Looking up movie by filehash via [TheMovieDB]
TheMovieDB: Hash lookup not supported
Auto-detect movie from context: [E:\testdata\utorrent-postprocess-test\archive\Avatar\Avatar.mp4]
[TEST] Rename [E:\testdata\utorrent-postprocess-test\archive\Avatar\Avatar.mp4] to [E:\output\Movies\Avatar (2009)\Avatar (2009).mp4]
Processed 1 files
Done ?(?????)?
:idea: Please read the FAQ and How to Request Help.

MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Re: Is X11 required when just using the command line?

Post by MACscr » 04 Feb 2013, 08:49

I already admitted to the typo so thats why the command was not completing as the folder was empty (aka, it didnt exist because the path was wrong). My point is that your update didnt get rid of the x11 warnings.

User avatar
rednoah
The Source
Posts: 16803
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Is X11 required when just using the command line?

Post by rednoah » 04 Feb 2013, 08:50

As for the warnings, nothing I can do about it unless I know where they're coming from. It's probably in the Java or Groovy runtime.
:idea: Please read the FAQ and How to Request Help.

User avatar
rednoah
The Source
Posts: 16803
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Is X11 required when just using the command line?

Post by rednoah » 04 Feb 2013, 09:03

Try setting all these:

Code: Select all

-DuseGVFS=false -DuseExtendedFileAttributes=false -Djava.net.useSystemProxies=false -Dapplication.analytics=false
:idea: Please read the FAQ and How to Request Help.

MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Re: Is X11 required when just using the command line?

Post by MACscr » 04 Feb 2013, 09:05

Nice work. That fixed it! Thanks for your great app!

MACscr
Posts: 10
Joined: 03 Feb 2013, 06:04

Re: Is X11 required when just using the command line?

Post by MACscr » 01 May 2013, 23:34

You mentioned that the utorrent script already does plenty of logging. What is the path to the logs or even just the file name so I can search for it? Im on a headless ubuntu system.

User avatar
rednoah
The Source
Posts: 16803
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Is X11 required when just using the command line?

Post by rednoah » 02 May 2013, 02:07

Console output. And whatever you specify as --log file.
:idea: Please read the FAQ and How to Request Help.

Post Reply