| Summary: | Custom key bindings completely disables keyboard input | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Alister Sanders <aj.sanders3004> |
| Component: | video | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED FIXED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | critical | ||
| Priority: | P2 | CC: | philipp.wiesemann |
| Version: | 2.0.3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Attachments: | Full error log | ||
This problem has been resolved with the new 2.0.4 release |
Created attachment 2349 [details] Full error log When running an SDL2-based application whilst having custom keyboard bindings through xmodmap, this causes all of the keys on the keyboard to become unrecognized by SDL. Basically, if a program using SDL2 is run through a terminal, it spurts out one of these messages for each key on the keyboard: code = 1, sym = 0xFF1b, (Escape), scancode = 41 (Escape) And makes keyboard input for that program impossible. Attached is the full error log