sikuli-driver team mailing list archive

["J. Mailshredder" <734682@xxxxxxxxxxxxxxxxxx>]

I understand your comment:

"It might help, to upgrade to the newest JRE version (it seems that
beginning with version 24 it might work."

However, as noted in the original report, Sun/Oracle made changes to the
core JRE components post JRE 6 Update 10 that have adversely impacted a
large number of computers (particularly laptops) with certain graphic
chipsets.  So, presently, it is not possible to upgrade to the "newest
version" of JRE at this time.  They are aware of the issue(s) and have
not yet made a determination regarding a "fix".

Prior to the last Sikuli release, everything worked fine with older JRE
versions.  So, for now, the only option is to continue to test Sikuli
using the older releases.

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/734682

Title:
  X-1.0rc2: IDE: Windows: crashes on capture --- newest JRE and specific
  grafics equipement (e.g. Intel based)

Status in Sikuli:
  New

Bug description:
  **************** possible solution
  It might help, to upgrade to the newest JRE version (it seems that beginning with version 24 it might work)

  -----------------

  problem situation -------------------

  Sun modified the internals of JRE 1.6 somewhere around Update 10 to
  enable "Direct Draw" by default. This causes the Sikuli IDE to be
  unusable on many machines with particular graphic chipsets -
  particularly those manufactured by Intel. We have submitted an inquiry
  to to the developers to try and figure out a "work around" as their
  stated workaround:

  <app> -Dsun.java2d.noddraw=true

  does not revert the behavior to the correct functionality that existed
  prior to the change.

  --- J. Mailshredder said on 2011-03-11
  --------------------------------------------------------

  I have used earlier versions of Sikuli successfully...  But I just
  recently installed Sikuli X-1.0rc2 on Windows Vista 32-bit (a fresh,
  first time install) using the Windows .EXE installer and I am seeing
  behavior similar to that mentioned on a couple of "bug reports".  The
  IDE disappears during capture.

  It occurs using both a single and dual-monitor configuration.

  Even though the IDE disappears, the associated process (javaw.exe)
  continues to run.

  Sikuli was launched using the ".bat" process.  ("C:\Program
  Files\Sikuli X\Sikuli-IDE-w.bat")

  I noted some "similar" reports where the following startup process was
  suggested to capture additional data:

  java -Dsikuli.console=false -jar "c:\Program Files\Sikuli X\sikuli-
  ide.jar"

  When I do this...  The following console information is captured:

  [info] locale: en_US
  [debug] init user preferences
  [info] install hotkey: CTRL+SHIFT+2 for onQuickCapture
  [info] install hotkey: ALT+SHIFT+C for onStopRunning

  Then the IDE successfully appears.  If you click on the "Take
  Screenshot" icon the IDE disappears.  The following additional console
  information also appears:

  Exception in thread "capture" java.lang.UnsatisfiedLinkError: C:\Users\ud\AppDat
  a\Local\Temp\tmplib\Win32Util.dll: Can't find dependent libraries
          at java.lang.ClassLoader$NativeLibrary.load(Native Method)
          at java.lang.ClassLoader.loadLibrary0(Unknown Source)
          at java.lang.ClassLoader.loadLibrary(Unknown Source)
          at java.lang.Runtime.load0(Unknown Source)
          at java.lang.System.load(Unknown Source)
          at com.wapmx.nativeutils.jniloader.NativeLoader.loadLibrary(NativeLoader.java:44)
          at org.sikuli.script.Win32Util.<clinit>(Win32Util.java:14)
          at java.lang.Class.forName0(Native Method)
          at java.lang.Class.forName(Unknown Source)
          at org.sikuli.script.Env.getOSUtil(Env.java:84)
          at org.sikuli.script.ScreenHighlighter.init(ScreenHighlighter.java:175)
          at org.sikuli.script.ScreenHighlighter.<init>(ScreenHighlighter.java:288)
          at org.sikuli.script.Screen.initBounds(Screen.java:96)
          at org.sikuli.script.Screen.<init>(Screen.java:89)
          at org.sikuli.script.UnionScreen.<init>(UnionScreen.java:10)
          at org.sikuli.script.CapturePrompt.<init>(CapturePrompt.java:317)
          at org.sikuli.script.CapturePrompt.<init>(CapturePrompt.java:310)
          at org.sikuli.ide.CaptureButton$1.run(CaptureButton.java:186)

  I researched the "error" shown above - and all reference articles I
  could find seemed to indicate this was a "path" problem.  But both
  Sikuli and Java are mentioned correctly in my PATH variable:

  C:\Program Files\Sikuli X\libs;C:\Program Files\Java\jre6\bin

  Can anyone familiar with the new version shed some light on why it's
  not working?  Any help would be greatly appreciated.

  Thanks...

  NOTE: I am currently running an older build of Java JRE (v1.6.0 Build
  1.6.0-b105) for testing as the default behavior for "direct draw" was
  changed after JRE 6 update 10 and the Sikuli IDE does not properly
  display when running the latest version of the Java JRE on Windows
  Vista 32-bit - even with antialiasing disabled.