CentOS: how to setup SikuliX --- a script should be available

Bug #1349255 reported by RaiMan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SikuliX
Won't Fix
Medium
RaiMan

Bug Description

I have read many posts with similar questions and I have tried to use them as a guide but I have been unable to overcome my issue with trying to get Sikuli to work on CentOS 6.x.

From what I can tell this is an issue with Tesseract but I can't figure out how to correct it. I have performed the following thus far...:

     Installed CentOS 6.x
     Installed some prereqs (dev tools, gcc, cmake, etc)
     Installed OpenCV 2.2
     Installed Leptonica
     Installed Tesseract 3.02.02
     Installed Sikuli 1.0.1

When I run ./runIDE -d 3 -c I get the following output:

running SikuliX-IDE: -Xmx512M -Dapple.laf.useScreenMenuBar -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine
-jar ./sikuli-ide.jar -d 3 -c
[debug] Running on Java 7 (1.7.0_45-mockbuild_2013_11_22_18_30-b00)
[debug] --- Sikuli parameters ---
[debug] 1: -d
[debug] 2: 3
[debug] 3: -c
[debug] init user preferences
[debug] locale: en_US
[debug] ResourceLoaderBasic: SikuliX Package Build: 1.0.1 12SEP2013160242
[debug] ResourceLoaderBasic: check: we are running on arch: amd64
[debug] ResourceLoaderBasic: check: using Java at: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.45.x86_64/jre/
[debug] ResourceLoaderBasic: check: Exists libs folder at location of jar? YES: /home/user/Sikuli/
[debug] ResourceLoaderBasic: checkLibsDir: /home/user/Sikuli/libs
[debug] ResourceLoaderBasic: loadLib: JXGrabKey
[debug] ResourceLoaderBasic: loadLib: Found: JXGrabKey
[debug] ResourceLoaderBasic: loadLib: Now loaded: JXGrabKey
[debug] ResourceLoaderBasic: checkLibsDir: Using libs at: /home/user/Sikuli/libs
[debug] Screen: initScreens: basic initialization (1 Screen(s) found)
[debug] *** monitor configuration (primary: 0) ***
[debug] Screen 0: S(0)[0,0 1583x687]
[debug] *** end monitor configuration ***
[debug] [I18N] menuShowThumbs
[debug] ResourceLoaderBasic: loadLib: Is already loaded: JXGrabKey
[debug] Sikuli-IDE startup: 1519
[debug] MenuAction.doLoad
[debug] SikuliX Jython Support Build: 1.0.1 12SEP2013160248
[debug] SikuliEditorKit.read
[debug] ImageLocator: found 1405605172817.png in /home/user/Desktop/test.sikuli/
[debug] FileManager: tempfile create: /tmp/sikuli-4166345826942410403.png
[debug] FileManager: tempfile create: /tmp/sikuli-4490415893266343011.py
[debug] JythonScriptRunner: : executeScriptHeader: adding SikuliX Lib path to sys.path
/home/user/Sikuli/sikuli-ide.jar/Lib
[debug] Jython: sikuli: __init__: entering
[debug] Jython: sikuli: Sikuli: entering
[debug] Jython: sikuli: Sikuli: constants
[debug] Jython: sikuli: Sikuli: import Region
[debug] Jython: sikuli: Sikuli: import Screen
[debug] Jython: sikuli: Sikuli: Env.addHotkey
[debug] Jython: sikuli: Sikuli: import Match
[debug] Jython: sikuli: Sikuli: import Pattern
[debug] Jython: sikuli: Sikuli: import Location
[debug] Jython: sikuli: Sikuli: import ScreenUnion
[debug] Jython: sikuli: Sikuli: import Finder
[debug] ResourceLoaderBasic: loadLib: VisionProxy
[debug] ResourceLoaderBasic: loadLib: Found: VisionProxy
[error] ResourceLoaderBasic: loadLib: Fatal Error 110: loading: libVisionProxy.so
[error] ResourceLoaderBasic: loadLib: Since native library was found, it might be a problem with needed dependent libraries
/home/user/Sikuli/libs/libVisionProxy.so: libtesseract.so.3: cannot open shared object file: No such file or directory
[error] Terminating SikuliX after a fatal error(110)! Sorry, but it makes no sense to continue!
If you do not have any idea about the error cause or solution, run again
with a Debug level of 3. You might paste the output to the Q&A board.
[debug] SikuliXFinal: cleanUp: 0

I then tried running the ./makeVisionProxy and then copied the libVisionProxy.so as the README stated but no change.

Thanks in advance

Revision history for this message
AMS (solak1984) wrote :

Attached is the script I use for setting up a completely new CentOS 6.5 system after a fresh install.

Note: When installing the operating system, I select "Software Development" as the server function. I keep a CD with the script and the installation files for when the download locations are no longer available. In that case comment out the wget commands in the script and make sure the installation files needed are in the same directory as the script (/home/user/Downloads).

I would also double-check the /etc/profile additions performed by the script prior to performing the Sikuli installation if you want to be absolutely sure no issues are encountered.

Revision history for this message
RaiMan (raimund-hocke) wrote :

many thanks for your contribution.

questions:
- in the first and second yum block some things are repeated. reason?
- what happens if a package is already installed (upgrade e.g.)?

- what is the reason for the additional yum
yum install -y libtiff-devel.i686 libjpeg-devel.i686 libpng-devel.i686 giflib-devel.i686

Does CentOS 6.5 support 32-Bit and 64-Bit with one distribution?
I always thought with Linux: a running system is either 32-Bit or 64-Bit (Something like on Windows mixing both in the same setup is not possible)

Changed in sikuli:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.2.0
Revision history for this message
AMS (solak1984) wrote :

Thanks for reviewing it so quickly.

The repeated yum calls can be removed. It was really my mistake of having too many testing scripts on hand while putting together the final version. I just created a new CentOS 6.5 VM will test the updated version of the script.

Revision history for this message
RaiMan (raimund-hocke) wrote :

Thanks.

what about my other questions?

Additional:
Is it true, that the same approach could work on Fedora and RHEL?

Revision history for this message
AMS (solak1984) wrote :

- in the first and second yum block some things are repeated. reason?
    This was not intentional and will be corrected
- what happens if a package is already installed (upgrade e.g.)?
    Nothing will occur, it will simply skip stating the application is already there
- what is the reason for the additional yums
    Another unintentional addition which will be removed
- Does CentOS 6.5 support 32-Bit and 64-Bit with one distribution?
    No, There is only one version installed at a time. I removed the i686 yum calls and will update with the results.
- Is it true, that the same approach could work on Fedora and RHEL?
    The overall approach should be the same

Revision history for this message
RaiMan (raimund-hocke) wrote :

Great, thanks.

Revision history for this message
AMS (solak1984) wrote :

Attached is the updated script. I removed the attachment from the first post to avoid confusion.

Revision history for this message
RaiMan (raimund-hocke) wrote :

Thanks for your contribution.

I will install a CentOS the next days in VirtualBox and test it.
Should I use 6.5 or 7 ?

Revision history for this message
AMS (solak1984) wrote :

I havent yet tested on 7. I would try 6.5 first and confirm your results are the same as mine.

Revision history for this message
RaiMan (raimund-hocke) wrote :

ok, thanks

RaiMan (raimund-hocke)
Changed in sikuli:
status: In Progress → Won't Fix
milestone: 2.0.0 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.