sikuli-driver team mailing list archive

[Tannalein <tannalein@xxxxxxxxx>]

Hi,

I'm having the same problem on Ubuntu guest machine running TigerVNc
server. It would seem that Sikuli only sees the state of the screen as
it is at the moment of connection. If I set Sikuli to connect to the
guest machine, take a screenshot, set wait to 30 seconds, manually move
things around the screen, and after those thirty seconds Sikuli takes
another screenshot, I get the exact same image. The clock doesn't move.
If you check the screenshots Christoph posted, you can see that the file
was created at 11:11, but the Windows clock on the screenshot says
11:09. The screenshot was two minutes old at the time it was saved.

The issue seems to be connected to TigerVNC, because if I connect with
Vino VNC, which is the default VNC server on Ubuntu, I don't get this
issue. I do, however, get a garbled screenshot, which was the reason I
switched to TigerVNC.

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

Title:
  [1.1.4] VNC: synchronization of screen content for wait and capture
  not working properly

Status in Sikuli:
  In Progress

Bug description:
  Hi!

  I am currently developing some software tests using virtual Windows 7
  and 10 guests in VirtualBox. My VNC-Server on the guests is TigerVNC.

  What I am trying:

  client = vncStart(ip="192.168.56.100", port=5900, password="vnc"  ) 
  wait( 1 )

  client.keyDown( Key.WIN )
  client.type( "r" )
  client.keyUp()

  client.wait("Run.png",60)

  Run.png is a screenshot of the "run"-panel in Windows 7 or 10.
  This wait fails  on both Windows 7 and 10.
  The reason seems to be a failing synchronisation of the screen contents to the client-object.
  As a proof I made a capture of the client after 120s and attached the files for Windows 7 and 10.
  The code:
  client.keyDown( Key.WIN )
  client.type( "r" )
  client.keyUp()

  wait( 120 )
  client.capture().saveInBundle("Win10.png")
  Remark: on the virtual box window itself, I see the open run-panel, only the capture is empty.

  When I'm doing the wait and search-commands in my tests undotted on
  the virtual desktop window , everything works fine. I only avoid this
  with the goal starting the tests from a jenkins server testing virtual
  machines later.

  Best regards,
  Christoph

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