← Back to team overview

sikuli-driver team mailing list archive

[Bug 2048941] [NEW] Issue Executing java -jar sikulixide-2.0.5-win.jar

 

Public bug reported:

I've been using sikulixide-2.0.5-win.jar all week without issue and now
when I try to launch the IDE, it brings up a dialog box that says,
"SikuliX-IDE 2.0.5 is starting on Java 17" but the IDE never comes back
up.  I tried deleting the jar and re-downloading it but the issue
remains.  Apparently something changed in my user profile because I had
someone use the exact same jar file on their machine and it works just
fine.  I've checked Task Manager and "ps -ef" with no luck.

This is being run on Windows 64-bit OS.

I start the jar as follows:

java -jar sikulixide-2.0.5-win.jar

Prior to the issue I was trying to delete some log files that my Sikuli
script created.  Apparently, I must have exited my script before closing
a file because when I tried to delete, I got a "resource busy" error.  I
was finally able to fix the issue but then the Sikuli application went
down never to return again :(.

** Affects: sikuli
     Importance: Undecided
         Status: New

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

Title:
  Issue Executing java -jar sikulixide-2.0.5-win.jar

Status in SikuliX:
  New

Bug description:
  I've been using sikulixide-2.0.5-win.jar all week without issue and
  now when I try to launch the IDE, it brings up a dialog box that says,
  "SikuliX-IDE 2.0.5 is starting on Java 17" but the IDE never comes
  back up.  I tried deleting the jar and re-downloading it but the issue
  remains.  Apparently something changed in my user profile because I
  had someone use the exact same jar file on their machine and it works
  just fine.  I've checked Task Manager and "ps -ef" with no luck.

  This is being run on Windows 64-bit OS.

  I start the jar as follows:

  java -jar sikulixide-2.0.5-win.jar

  Prior to the issue I was trying to delete some log files that my
  Sikuli script created.  Apparently, I must have exited my script
  before closing a file because when I tried to delete, I got a
  "resource busy" error.  I was finally able to fix the issue but then
  the Sikuli application went down never to return again :(.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/2048941/+subscriptions