[Sikuli-driver] [Bug 793723] Re: Linux System Always Uses Screen(0)
I can confirm this bug under Opensuse Linux 13.1. I have a two-monitors setup. My application iterates all screens, looks for a certain image and then clicks on it. This works fine if that image is on screen 0. If it is on screen 1, Sikuli moves the pointer to the corresponding position on screen 0 (which in my case is above screen 1) and clicks there: [log] CLICK on L(90,1217)@S(1)[0,1050 1920x1080] -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/793723 Title: Linux System Always Uses Screen(0) Status in Sikuli: In Progress Bug description: I am using Sikuli version 1.0rc3 compiled from source on a Redhat EL4 system. I have a 3 monitor setup running X11R7.1.1 and it appears that Sikuli maps all operations to screen 0 i.e. DISPLAY :0.0. The getNumberScreens() method returns 3 as expected, and instantiating screen objects for Screen(0), Screen(1), and Screen(2) appear to work. Trying to use the screen objects to invoke click(), find(), etc. always result in an operation on screen(0) only. If I print the screen objects all 3 return the following: Screen(0)[0,0 1920x1200] E:Y, T:3.0 So, does this version of Sikuli support a multi-monitor Linux setup and if yes, what could I be doing wrong? Thanks... To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/793723/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 793723] Re: Linux System Always Uses Screen(0)
I am working with 1.1.0, so yes, I can confirm that. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/793723 Title: Linux System Always Uses Screen(0) Status in Sikuli: In Progress Bug description: I am using Sikuli version 1.0rc3 compiled from source on a Redhat EL4 system. I have a 3 monitor setup running X11R7.1.1 and it appears that Sikuli maps all operations to screen 0 i.e. DISPLAY :0.0. The getNumberScreens() method returns 3 as expected, and instantiating screen objects for Screen(0), Screen(1), and Screen(2) appear to work. Trying to use the screen objects to invoke click(), find(), etc. always result in an operation on screen(0) only. If I print the screen objects all 3 return the following: Screen(0)[0,0 1920x1200] E:Y, T:3.0 So, does this version of Sikuli support a multi-monitor Linux setup and if yes, what could I be doing wrong? Thanks... To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/793723/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 793723] Re: [1.1.0-Beta1] Linux System Always Uses Screen(0)
You have e-mail. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/793723 Title: [1.1.0-Beta1] Linux System Always Uses Screen(0) Status in Sikuli: In Progress Bug description: I am using Sikuli version 1.0rc3 compiled from source on a Redhat EL4 system. I have a 3 monitor setup running X11R7.1.1 and it appears that Sikuli maps all operations to screen 0 i.e. DISPLAY :0.0. The getNumberScreens() method returns 3 as expected, and instantiating screen objects for Screen(0), Screen(1), and Screen(2) appear to work. Trying to use the screen objects to invoke click(), find(), etc. always result in an operation on screen(0) only. If I print the screen objects all 3 return the following: Screen(0)[0,0 1920x1200] E:Y, T:3.0 So, does this version of Sikuli support a multi-monitor Linux setup and if yes, what could I be doing wrong? Thanks... To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/793723/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #250119]: How can I turn on debugging in a JUnit test?
Question #250119 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/250119 Rainer Klute gave more information on the question: What I am trying to do is to integrate Sikuli JUnit tests into my project's Maven build. If I explictly add sikulix.jar to my classpath, the JUnit tests find libVisionProxy.so in the libs folder which is neighboring sikulix.jar. So I am able to run my JUnit tests in Eclipse, but this is of course no option for Maven. It should be possible to configure somehow where libVisionProxy.so resides. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #250119]: How can I turn on debugging in a JUnit test?
Question #250119 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/250119 Status: Answered = Solved Rainer Klute confirmed that the question is solved: Thanks RaiMan, that solved my question. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #250119]: How can I turn on debugging in a JUnit test?
New question #250119 on Sikuli: https://answers.launchpad.net/sikuli/+question/250119 Running a JUnit test case I get the following error message: [error] ResourceLoader: loadLib: Fatal Error 110: loading: libVisionProxy.so [error] ResourceLoader: loadLib: Since native library was found, it might be a problem with needed dependent libraries Expecting an absolute path of the library: libVisionProxy.so [error] RunSetup: Problem with SikuliX libs folder - see error log [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 QA board. How can I set the debug level to 3 in order to dive deeper into the problem? How is the libVisionProxy.so looked up anyway? I couldn't find that in the docs. What's that absolute path in Expecting an absolute path of the library: libVisionProxy.so? Regarding see error log, I don't have any error log besides what I pasted above. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #249653]: Running a Sikuli script throws a java.lang.NoClassDefFoundError
Question #249653 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/249653 Status: Answered = Solved Rainer Klute confirmed that the question is solved: I just had the time to repeat the installation executing sikulixsetup-1.1.jar in an otherwise empty directory. Then I copied my self-compiled libVisionProxy.so to the libs folder, ran java -jar sikulix.jar, created my first simple script, and – it worked! Thanks for your help! (Will now try to write some JUnit tests ...) -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #249653]: Running a Sikuli script throws a java.lang.NoClassDefFoundError
Question #249653 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/249653 Rainer Klute confirmed that the question is solved: Thanks RaiMan, that solved my question. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #249653]: Running a Sikuli script throws a java.lang.NoClassDefFoundError
Question #249653 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/249653 Rainer Klute posted a new comment: How would this bring org.sikuli.natives.VisionProxyJNI into the classpath? (I have a self-compile libVisionProxy.so in my libs directory already.) -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #249653]: Running a Sikuli script throws a java.lang.NoClassDefFoundError
Question #249653 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/249653 Rainer Klute posted a new comment: I did execute sikulixsetup-1.1.jar. However, I skipped the download step, because this was my second try to generate sikuli.jar and I had the downloaded files already. I could repeat everything WITH downloading them, if it helps. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #249530]: Cannot install Sikuli because libopencv is too recent
Question #249530 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/249530 Status: Answered = Solved Rainer Klute confirmed that the question is solved: Building libVisionProxy.so from source was the way to got – it works! Thanks! (I'll got an error when trying to run a very simple test script, though. But that will be another question ...) -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #249653]: Running a Sikuli script throws a java.lang.NoClassDefFoundError
New question #249653 on Sikuli: https://answers.launchpad.net/sikuli/+question/249653 I am trying my very first steps with Sikuli X 1.1 on Linux (Opensuse 13.1, 64 bit). In a first test I used the IDE to create a script click(image). I saved the script and then tried to execute it. However, the following error message appeared: [error] script [ test ] stopped with error in line 1 [error] java.lang.NoClassDefFoundError ( java.lang.NoClassDefFoundError: org/sikuli/natives/VisionProxyJNI ) The missing class IS in two of the downloaded jars, but it IS NOT in sikulix.jar. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #249530]: Cannot install Sikuli because libopencv is too recent
New question #249530 on Sikuli: https://answers.launchpad.net/sikuli/+question/249530 My Sikuli installation under Opensuse Linux 13.1 aborts with an error message telling that libopencv_core.so.2.3 cannot be found. Well, that's very plausible, because I don't have OpenCV 2.3 installed, but rather 2.4. However, shouldn't a more recent version work even better than not at all? For completeness, here's the error log: [debug (28.05.14 16:36:05)] ResourceLoader: export: Found 8 Files in Lib/sikuli [error (28.05.14 16:36:05)] ResourceLoader: loadLib: Fatal Error 110: loading: libVisionProxy.so [error (28.05.14 16:36:05)] ResourceLoader: loadLib: Since native library was found, it might be a problem with needed dependent libraries /data/data1/klute/Archiv/Sikuli/xxx/libs/libVisionProxy.so: libopencv_core.so.2.3: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden [error (28.05.14 16:36:05)] RunSetup: Problem with SikuliX libs folder - see error log [error (28.05.14 17:32:21)] Terminating SikuliX after a fatal error(110)! Sorry, but it makes no sense to continue! -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #249530]: Cannot install Sikuli because libopencv is too recent
Question #249530 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/249530 Rainer Klute posted a new comment: Yes, thanks, it should do it – will try. However, I consider this an ugly workaround and not a solution. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
