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.
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.