sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #41901
[Bug 1506359] Re: [1.1.0] Linux: not working wmctrl should not terminate SikuliX, but only block App class usage --- fixed 1.1.1-2015-10-17
Related problem:
http://stackoverflow.com/questions/34443779/wmctrl-not-executable-while-running-sikulix-script-in-headless-mode
I'm experiencing this with SikuliX 1.1.0 and CentOS 7.X, with Xvfb
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1506359
Title:
[1.1.0] Linux: not working wmctrl should not terminate SikuliX, but
only block App class usage --- fixed 1.1.1-2015-10-17
Status in Sikuli:
Fix Released
Bug description:
Trying to run Sikuli 1.1.0 on CentOS7
Managed to get all required RPMs installed an running the following on
a remote server forwarding the X session via SSH to a local Windows-
based X server (XLaunch)
Managed to run the setup, after that I am getting as follows:
[sikuli@localhost src]$ ./runsikulix
running SikuliX: -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine
-jar ./sikulix.jar
[info] runcmd: lsb_release -i -r -s
[error] RunTimeINIT: fatal error: java.io.IOException: Cannot run program "lsb_release": error=2, No such file or directory
[info] HotkeyManager: add Capture Hotkey: CTRL+SHIFT 2 (50, 3)
[info] HotkeyManager: add Abort Hotkey: ALT+SHIFT C (67, 9)
[error] RunTimeIDE: *** terminating: command 'wmctrl' is not executable
please check the Availability!
[sikuli@localhost src]$ which wmctrl
/usr/bin/wmctrl
[sikuli@localhost src]$ wmctrl -V
1.07
[sikuli@localhost src]$
Cant really figure out this one - could this be a case of wmctrl
requiring some kind of desktop environment or windows management
system running? Im running raw X session - nothing on top of it and
could run Setup just fine.
Thanks,
Marcel
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1506359/+subscriptions
References