New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
synthetic keys stopped working (Debian jessie/sid and others) #52
Comments
I can confirm this report with Gentoo and vanilla sources. Hopefully this gets fixed before the Debian jessy release |
Debian report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764079 |
Any progress on this? Is this a problem with xdotool source or something specific to Debian's implementation? I've just installed Debian 8.2 (released Sep 2015) and discovered this problem. The last comment on that Debian bug report was in Nov 2014. |
I had this problem with HEAD as well, so it's not debian only. |
Instead of sending keys directly to a specific window, activate the window, then send the keys to the active window. This is work-around for an xdotool bug[0], which broke sending synthetic keys, such as Ctrl+F, to a specific window. The downside of this approach is that the user could break the test if they switched to another window while the test is running. This is not a big deal, because one should run automated tests in an isolated environment (for example, under Xvfb) anyway. This commit should be reverted once the xdotool bug is fixed. [0] jordansissel/xdotool#52
I pulled an older version and it worked as intended.
What happens with older versions:
xev reports:
Newer versions:
xev reports:
The last version that exhibits the correct behaviour seems to be edbbb7a.
The text was updated successfully, but these errors were encountered: