sikuli-driver team mailing list archive

[RaiMan <sikulix@xxxxxxxxxxx>]

what exact version of Windows?

** Changed in: sikuli
       Status: New => In Progress

** Changed in: sikuli
   Importance: Undecided => Medium

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

** Changed in: sikuli
    Milestone: None => 1.1.4

** Summary changed:

- [error] RobotDesktop: checkMousePosition: new information
+ [1.1.4] [error] RobotDesktop: checkMousePosition: new information

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

Title:
  [1.1.4] [error] RobotDesktop: checkMousePosition: new information

Status in Sikuli:
  In Progress

Bug description:
  Hi
  Maybe I can support with the bugfinding of the
  [error] RobotDesktop: checkMousePosition: should be L(960,12)@S(0)[0,0 1920x1080] but after move is L(923,71)@S(0)[0,0 1920x1080] Possible cause in case you did not touch the mouse while script was running: Mouse actions are blocked generally or by the frontmost application. You might try to run the SikuliX stuff as admin

  issue.

  I run the latest version of java and Sikulix.

  Sikulix 2018-10-11_14:41 (Build 109)

  C:\temp\SikuliX>java -version
  java version "1.8.0_181"
  Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
  Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)

  All went fine the last couple of weeks, without running the jar as
  admin. Suddenly yesterday in the middle of night the program stopped
  working, and clicks were not registered anymore. with the error
  message above. Actually the error message appeared even before, while
  it was still working fine.

  I was not able to get it back to work, by reinstalling java, or the
  newest Sikulix version. only running as admin fixed the issue. (so it
  is working now - only in administrator mode).

  When suddenly in the middle of night the Sikulix program stopped working, I did not do any OS updates or any other changes (actually I was not even at home). However, on the evening before I started playing around with running external programs from the script.
  Just 2-3 hours before it stopped working I used app.focus to start taskkill and open tail.  (which actually is strange, because it should just focus on an existing window - maybe another bug).
  I also started to import subprocess.

  import subprocess

  And in my script I am using taskkill a lot - I am mentioning this, as at the same time the clicks did not work anymore, also the taskkill command did not work anymore.
  these are the commands used:
  App.focus(r"C:\Program Files (x86)\TeamViewer\TeamViewer.exe")
  subprocess.call('taskkill.exe /f /im TeamViewer.exe')

  App.focus worked fine all the time, subprocess stopped at the same
  time the click stopped working.

  I can reproduce here and happy to help.

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