Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Key Input Not Supported
See original GitHub issueWhen attempting to use key input, webdriver compains because the environment has no window system:
WebDriverError: unknown error: an X display is required for keycode conversions, consider using Xvfb_
Possible solutions:
- Bundle Xvfb (gross)
- Wait for ChromeDriver team to fix/open issue?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
[SOLVED] Input Not Supported on Monitor
The 'Input Not Supported' error usually occurs to your computer after booting up, and it happens with a black screen on your computer....
Read more >Fix Input Not Supported Monitor error on Windows PC
Input Not Supported Monitor error · 1] Change the Screen Resolution and Monitor Refresh Rate · 2] Update monitor driver and graphics adapter ......
Read more >5 Ways To Fix Input Not Supported On Monitor
Press Windows Key + X and Click on Device Manager. · Click on Display adapters to expand the driver list. · Right-click on...
Read more >What to Do If Acer Monitor Says Input Not Supported?
Usually, this error means the resolution of your computer has been set to one that is not supported on the monitor. The monitor...
Read more >Input Not Supported on Monitor [FIXED]
How to get rid of the Input not supported on monitor problem? · Check your monitor connection · Tweak your resolution settings ·...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Good news, looks like it was recently fixed in ChromeDriver 2.31: https://bugs.chromium.org/p/chromedriver/issues/detail?id=1772#c28
Will try and fix the script in the next week that fetches the old version or so to point to the new release (and test it). Should be a simple update: https://github.com/smithclay/lambdium/blob/master/scripts/fetch-dependencies.sh#L19
This has been addressed. New chromium and chromedriver are now bundled.