as a short term workaround, the only possibility at the scripting level is to do the following: (only possible if wmctrl still works if renamed to something else) replace the wmctrl executable with a shell script, that does not return any errors.
This would allow, to continue testing, provided you do not use the App class features in the moment I will try to make this internal test a bit more graceful or even optional. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1573466 Title: [request] SikuliX should work with window manager mwm Status in Sikuli: New Bug description: Dear RaiMan, we are thinking to use Sikulix as platform for the HMI testing on large scale applications. We are obliged to use mwm as window manager. We have no other choice. We tried to run our application on different window managers without result. Unfortunately Sikulix does not run with mwm. Attached some .txt with the output received. Sikulix, on the same platform, works fine with any other window manager (GNOME or KDE or ICEWM). Can you help us? Thanks a lot for the support. Alfredo & Andrea P.S.: wmctrl is installed and works fine. In mwm windows manager wmctrl -m returns: Cannot get window manager info properties. (_NET_SUPPORTING_WM_CHECK or _WIN_SUPPORTING_WM_CHECK) To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1573466/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
